From: Lee Jones <lee@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: broonie@kernel.org, andy.shevchenko@gmail.com,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: (subset) [PATCH v4 1/6] spi: cs42l43: Tidy up header includes
Date: Thu, 8 Feb 2024 17:46:16 +0000 [thread overview]
Message-ID: <20240208174616.GY689448@google.com> (raw)
In-Reply-To: <ZcUSIoAXmYsm0Lui@ediswmail9.ad.cirrus.com>
On Thu, 08 Feb 2024, Charles Keepax wrote:
> On Thu, Feb 08, 2024 at 02:13:06PM +0000, Lee Jones wrote:
> > On Mon, 29 Jan 2024 15:25:52 +0000, Charles Keepax wrote:
> > > Including some missing headers.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [1/6] spi: cs42l43: Tidy up header includes
> > commit: 0863c47b4147b948a23f03031ac880096512a878
>
> Thanks all, sorry about the confusion I really should have kept
> including the blurb I did on the first version of the patch that
> pointed this out explicitly.
No problem. I would have probably missed it anyway!
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-02-08 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 15:25 [PATCH v4 1/6] spi: cs42l43: Tidy up header includes Charles Keepax
2024-01-29 15:25 ` [PATCH v4 2/6] mfd: " Charles Keepax
2024-01-29 15:25 ` [PATCH v4 3/6] mfd: cs42l43: Use __u8 type rather than u8 for firmware interface Charles Keepax
2024-01-29 15:25 ` [PATCH v4 4/6] mfd: cs42l43: Add time postfixes on defines Charles Keepax
2024-01-29 15:25 ` [PATCH v4 5/6] mfd: cs42l43: Add some missing dev_err_probe()s Charles Keepax
2024-01-29 15:25 ` [PATCH v4 6/6] mfd: cs42l43: Handle error from devm_pm_runtime_enable() Charles Keepax
2024-02-08 9:04 ` [PATCH v4 1/6] spi: cs42l43: Tidy up header includes Lee Jones
2024-02-08 10:16 ` (subset) " Lee Jones
2024-02-08 13:35 ` Charles Keepax
2024-02-08 13:57 ` Lee Jones
2024-02-08 13:59 ` Mark Brown
2024-02-08 14:13 ` Lee Jones
2024-02-08 17:40 ` Charles Keepax
2024-02-08 17:46 ` Lee Jones [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=20240208174616.GY689448@google.com \
--to=lee@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.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.