From: Raag Jadav <raag.jadav@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mark Brown <broonie@kernel.org>,
lgirdwood@gmail.com, bleung@chromium.org, groeck@chromium.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Convert regulator drivers to use devm_kmemdup_array()
Date: Thu, 6 Mar 2025 13:32:19 +0200 [thread overview]
Message-ID: <Z8mHw_W1xT9Mcilt@black.fi.intel.com> (raw)
In-Reply-To: <Z8mBQEKAJfZd6a7G@smile.fi.intel.com>
On Thu, Mar 06, 2025 at 01:04:32PM +0200, Andy Shevchenko wrote:
> On Thu, Mar 06, 2025 at 12:14:59PM +0200, Raag Jadav wrote:
> > On Thu, Mar 06, 2025 at 11:19:31AM +0200, Andy Shevchenko wrote:
> > > On Thu, Mar 06, 2025 at 04:15:55AM +0200, Raag Jadav wrote:
> > > > On Fri, Feb 28, 2025 at 09:22:47PM +0000, Mark Brown wrote:
> > > > > On Fri, 28 Feb 2025 12:50:55 +0530, Raag Jadav wrote:
> > > > > > This series converts regulator drivers to use the newly introduced[1]
> > > > > > devm_kmemdup_array() helper. This depends on changes available on
> > > > > > immutable tag[2].
> > > > > >
> > > > > > [1] https://lore.kernel.org/r/20250212062513.2254767-1-raag.jadav@intel.com
> > > > > > [2] https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com
> > > > > >
> > > > > > [...]
> > > > >
> > > > > Applied to
> > > > >
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> > > >
> > > > Thank you.
> > > >
> > > > Unless there's a nuance intended in the merge series title that I'm unable
> > > > to understand, it probably seems incomplete.
> > >
> > > I believe it's an issue somewhere in the scripts. The long Subject line is
> > > split in the mailbox and that's probably is not supported by the machinery.
> > >
> > > You are not the only one who reports this issue.
> >
> > While I'm not well educated on the machinery, I'm also seeing devm_kmemdup_array()
> > introduction commit reordered in -next and thinking perhaps it can cause issues
> > with bisect, especially after final merge into Linus' tree?
>
> I;m not sure what you exactly pointing out here. Mark seems applied only
> necessary part of the immutable tag, which have the same effect. The Git merges
> only once the stuff as long as it has the same hash.
$ git describe
next-20250306
$ git log --oneline --grep raag
...
1f4c7f3b3afa Merge patch series "Split devres APIs to device/devres.h and introduce devm_kmemdup_array()"
a103b833ac38 devres: Introduce devm_kmemdup_array()
b8c38ccb2ca5 input: ipaq-micro-keys: use devm_kmemdup_array()
cdcc09a495a4 input: sparse-keymap: use devm_kmemdup_array()
a0d78eec8839 iio: adc: xilinx-xadc-core: use devm_kmemdup_array()
86068aca7548 pinctrl: pxa2xx: use devm_kmemdup_array()
91bfcc7a2fdb pinctrl: tangier: use devm_kmemdup_array()
d795fb90d6c6 pinctrl: cherryview: use devm_kmemdup_array()
f192c8447f4e pinctrl: baytrail: copy communities using devm_kmemdup_array()
753764aa8eb5 pinctrl: intel: copy communities using devm_kmemdup_array()
a21cad931276 driver core: Split devres APIs to device/devres.h
18311a766c58 err.h: move IOMEM_ERR_PTR() to err.h
I'm expecting commit a103b833ac38 to be before its users, or perhaps I'm
doing something wrong here?
Raag
next prev parent reply other threads:[~2025-03-06 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 7:20 [PATCH v2 0/2] Convert regulator drivers to use devm_kmemdup_array() Raag Jadav
2025-02-28 7:20 ` [PATCH v2 1/2] regulator: devres: " Raag Jadav
2025-02-28 7:20 ` [PATCH v2 2/2] regulator: cros-ec: " Raag Jadav
2025-02-28 21:22 ` [PATCH v2 0/2] Convert regulator drivers to " Mark Brown
2025-03-06 2:15 ` Raag Jadav
2025-03-06 9:19 ` Andy Shevchenko
2025-03-06 10:14 ` Raag Jadav
2025-03-06 11:04 ` Andy Shevchenko
2025-03-06 11:32 ` Raag Jadav [this message]
2025-03-06 12:37 ` Andy Shevchenko
2025-03-06 12:50 ` Andy Shevchenko
2025-03-06 13:22 ` Mark Brown
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=Z8mHw_W1xT9Mcilt@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bleung@chromium.org \
--cc=broonie@kernel.org \
--cc=groeck@chromium.org \
--cc=lgirdwood@gmail.com \
--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