From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] spi: Unify and simplify fwnode related checks
Date: Wed, 11 Dec 2024 13:33:33 +0200 [thread overview]
Message-ID: <Z1l4jTtm-BterK5D@smile.fi.intel.com> (raw)
In-Reply-To: <Z1lwnqGZsO_x8h0k@smile.fi.intel.com>
On Wed, Dec 11, 2024 at 12:59:42PM +0200, Andy Shevchenko wrote:
> On Wed, Dec 11, 2024 at 09:42:33AM +0530, Mukesh Kumar Savaliya wrote:
> > On 12/8/2024 9:33 PM, Andy Shevchenko wrote:
> > > couple of cleanups on top of recently added change.
> > please add what exactly cleanups done ? Recently added change is not that
> > something someone would check as part of this patch.
> > Description would be helpful.
>
> But each patch has its description. Or I didn't get the request, sorry.
FWIW, the change induced this mini-series is this one: d24cfee7f63d ("spi: Fix
acpi deferred irq probe").
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-12-11 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 16:03 [PATCH v1 0/2] spi: Unify and simplify fwnode related checks Andy Shevchenko
2024-12-08 16:03 ` [PATCH v1 1/2] spi: Unify firmware node type checks Andy Shevchenko
2024-12-08 16:03 ` [PATCH v1 2/2] spi: Deduplicate deferred probe checks in spi_probe() Andy Shevchenko
2024-12-10 18:05 ` [PATCH v1 0/2] spi: Unify and simplify fwnode related checks Mark Brown
2024-12-11 4:12 ` Mukesh Kumar Savaliya
2024-12-11 10:59 ` Andy Shevchenko
2024-12-11 11:33 ` Andy Shevchenko [this message]
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=Z1l4jTtm-BterK5D@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
/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.