From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Raag Jadav <raag.jadav@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
mika.westerberg@linux.intel.com, dmitry.torokhov@gmail.com,
broonie@kernel.org, pierre-louis.bossart@linux.dev,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Introduce devm_kmemdup_array() helper
Date: Thu, 12 Dec 2024 18:25:16 +0200 [thread overview]
Message-ID: <Z1sObNubEnsFwzOD@smile.fi.intel.com> (raw)
In-Reply-To: <2024121242-saturday-aqua-9ac6@gregkh>
On Thu, Dec 12, 2024 at 03:39:57PM +0100, Greg KH wrote:
> On Thu, Dec 12, 2024 at 04:32:48PM +0200, Andy Shevchenko wrote:
> > On Sat, Dec 07, 2024 at 04:46:18PM +0200, Raag Jadav wrote:
> > > On Fri, Nov 29, 2024 at 04:20:14PM +0200, Andy Shevchenko wrote:
> > > > On Fri, Nov 29, 2024 at 11:17:02AM +0100, Linus Walleij wrote:
> > > > > On Tue, Nov 26, 2024 at 6:22 PM Raag Jadav <raag.jadav@intel.com> wrote:
> > > > >
> > > > > > This series introduces a more robust and cleaner devm_kmemdup_array()
> > > > > > helper and uses it across drivers.
> > > > >
> > > > > For the series:
> > > > > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> > > > >
> > > > > It seems like Andy will push it to me which is excellent.
> > > >
> > > > Yep, that's the plan after we get all necessary ACKs.
> > >
> > > Greg, anything I can do to move this forward?
> >
> > Greg, is it possible to give your Ack or comment or guidance of the preferences
> > with the first patch?
>
> $ mdfrm -c ~/mail/todo/
> 2293 messages in /home/gregkh/mail/todo/
Oh my...
> Please be patient.
Sure!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-12-12 16:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 17:22 [PATCH v2 0/6] Introduce devm_kmemdup_array() helper Raag Jadav
2024-11-26 17:22 ` [PATCH v2 1/6] devres: Introduce devm_kmemdup_array() Raag Jadav
2024-11-27 1:36 ` Dmitry Torokhov
2024-11-26 17:22 ` [PATCH v2 2/6] pinctrl: intel: copy communities using devm_kmemdup_array() Raag Jadav
2024-11-26 22:37 ` Andy Shevchenko
2024-11-26 17:22 ` [PATCH v2 3/6] pinctrl: tangier: use devm_kmemdup_array() Raag Jadav
2024-11-26 22:38 ` Andy Shevchenko
2024-11-26 17:22 ` [PATCH v2 4/6] pinctrl: pxa2xx: " Raag Jadav
2024-11-26 17:22 ` [PATCH v2 5/6] input: sparse-keymap: " Raag Jadav
2024-11-27 1:36 ` Dmitry Torokhov
2024-11-26 17:22 ` [PATCH v2 6/6] ASoC: Intel: avs: " Raag Jadav
2024-11-27 8:30 ` Amadeusz Sławiński
2024-11-26 22:40 ` [PATCH v2 0/6] Introduce devm_kmemdup_array() helper Andy Shevchenko
2024-11-27 1:37 ` Dmitry Torokhov
2024-11-29 10:17 ` Linus Walleij
2024-11-29 14:20 ` Andy Shevchenko
2024-12-07 14:46 ` Raag Jadav
2024-12-12 14:32 ` Andy Shevchenko
2024-12-12 14:39 ` Greg KH
2024-12-12 16:25 ` Andy Shevchenko [this message]
2025-01-16 14:50 ` Andy Shevchenko
2025-01-17 15:00 ` Raag Jadav
2025-01-20 17:07 ` Andy Shevchenko
2025-01-20 17:11 ` Andy Shevchenko
2025-01-21 6:05 ` Raag Jadav
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=Z1sObNubEnsFwzOD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=raag.jadav@intel.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.