From: Lee Jones <lee@kernel.org>
To: linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Andy Shevchenko <andy@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v1 0/4] mfd: intel_soc_pmic_bxtwc: A few cleanups
Date: Thu, 31 Oct 2024 14:59:05 +0000 [thread overview]
Message-ID: <173038674598.1763751.11067388290170331649.b4-ty@kernel.org> (raw)
In-Reply-To: <20241016105201.757024-1-andriy.shevchenko@linux.intel.com>
On Wed, 16 Oct 2024 13:49:50 +0300, Andy Shevchenko wrote:
> While working on the fixes series against the driver I have noticed some
> places that can be improved using better APIs or approaches. Hence this
> mini-series. The plus statistics is due to the patch 2 that brought
> missed inclusions to the code (instead of using a proxy header).
>
> Have been tested on Intel Joule device.
>
> [...]
Applied, thanks!
[1/4] mfd: intel_soc_pmic_bxtwc: Switch to use ATTRIBUTE_GROUPS()
commit: 1f9e418aafc6ee52aad25b85f1e799f031f8de67
[2/4] mfd: intel_soc_pmic_bxtwc: Don't use "proxy" headers
commit: d2e77347ce9a4d70165f4e97d6a4133e48e678cc
[3/4] mfd: intel_soc_pmic_bxtwc: Use temporary variable for struct device
commit: 3d6b7374f0d8b5f8945185e901a6f5e7ae887a16
[4/4] mfd: intel_soc_pmic_bxtwc: Deduplicate error messages
commit: 4a8b3d48dad2ddbbb150602606c65bef3c2b3f8e
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-10-31 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 10:49 Andy Shevchenko
2024-10-16 10:49 ` [PATCH v1 1/4] mfd: intel_soc_pmic_bxtwc: Switch to use ATTRIBUTE_GROUPS() Andy Shevchenko
2024-10-16 10:49 ` [PATCH v1 2/4] mfd: intel_soc_pmic_bxtwc: Don't use "proxy" headers Andy Shevchenko
2024-10-16 10:49 ` [PATCH v1 3/4] mfd: intel_soc_pmic_bxtwc: Use temporary variable for struct device Andy Shevchenko
2024-10-16 10:49 ` [PATCH v1 4/4] mfd: intel_soc_pmic_bxtwc: Deduplicate error messages Andy Shevchenko
2024-10-31 14:59 ` 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=173038674598.1763751.11067388290170331649.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®