All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 1/1] at24: Drop of_match_ptr() and ACPI_PTR() protections
Date: Tue, 25 Feb 2025 12:48:40 +0200	[thread overview]
Message-ID: <Z72gCD7B0_jj-f2s@smile.fi.intel.com> (raw)
In-Reply-To: <745ff032-1e71-4569-ac9f-07c44cbcb344@app.fastmail.com>

On Tue, Feb 25, 2025 at 11:42:48AM +0100, Arnd Bergmann wrote:
> On Tue, Feb 25, 2025, at 11:37, Andy Shevchenko wrote:
> > On Tue, Feb 25, 2025 at 11:29:05AM +0100, Arnd Bergmann wrote:
> >> On Tue, Feb 25, 2025, at 11:08, Andy Shevchenko wrote:
> >
> >> Subject: [PATCH] [SUBMITTED 20240403] spi: remove incorrect of_match_ptr
> >>  annotations
> >
> > Was it applied (and the rest you provided here)?
> 
> It was part of a longer series. Some were applied, but the ones
> I provided here are those that for some reason did not make it.
> They should apply cleanly to today's linux-next.

I can review them and give a tag if you issue a new version.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-02-25 10:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 10:08 [PATCH v1 1/1] at24: Drop of_match_ptr() and ACPI_PTR() protections Andy Shevchenko
2025-02-25 10:29 ` Arnd Bergmann
2025-02-25 10:37   ` Andy Shevchenko
2025-02-25 10:42     ` Arnd Bergmann
2025-02-25 10:48       ` Andy Shevchenko [this message]
2025-02-25 18:09         ` Arnd Bergmann
2025-02-25 17:21   ` Krzysztof Kozlowski
2025-02-26 14:18     ` Andy Shevchenko
2025-02-27  8:18       ` Arnd Bergmann
2025-03-03 11:07 ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z72gCD7B0_jj-f2s@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.