From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] nvmem: patches (set 2) for 5.18
Date: Fri, 25 Feb 2022 12:31:21 +0100 [thread overview]
Message-ID: <Yhi+CSZYUwvVPN3J@kroah.com> (raw)
In-Reply-To: <e8f4af89-97f1-88d6-05ae-32246f1de57e@linaro.org>
On Fri, Feb 25, 2022 at 11:17:47AM +0000, Srinivas Kandagatla wrote:
>
>
> On 25/02/2022 10:52, Srinivas Kandagatla wrote:
> > Hi Greg,
> >
> > On 23/02/2022 22:34, Srinivas Kandagatla wrote:
> > > Hi Greg,
> > >
> > > Here is final set of nvmem patches for 5.18 which includes
> > >
> > > - Add new Sunplus nvmem provider and bindings.
> > > - fix in qfprom to increase blow timeout.
> > >
> > > Can you please queue them up for 5.18.
> > >
> > > thanks for you help,
> > > srini
> > >
> > > Knox Chiou (1):
> > > nvmem: qfprom: Increase fuse blow timeout to prevent write fail
> > >
> > > Vincent Shih (2):
> > > nvmem: Add driver for OCOTP in Sunplus SP7021
> > > dt-bindings: nvmem: Add bindings doc for Sunplus OCOTP driver
> >
> > Sorry for inconvenience, but can you please ignore this set if you have
> > not already applied them.
> >
> Opps, It looks like these were just applied.
>
> I can send other patches along with fix to yaml as next set, if that works
> for you?
Yes please.
next prev parent reply other threads:[~2022-02-25 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 22:34 [PATCH 0/3] nvmem: patches (set 2) for 5.18 Srinivas Kandagatla
2022-02-23 22:35 ` [PATCH 1/3] nvmem: qfprom: Increase fuse blow timeout to prevent write fail Srinivas Kandagatla
2022-02-23 22:35 ` [PATCH 2/3] nvmem: Add driver for OCOTP in Sunplus SP7021 Srinivas Kandagatla
2022-02-23 22:35 ` [PATCH 3/3] dt-bindings: nvmem: Add bindings doc for Sunplus OCOTP driver Srinivas Kandagatla
2022-02-25 10:52 ` [PATCH 0/3] nvmem: patches (set 2) for 5.18 Srinivas Kandagatla
2022-02-25 11:17 ` Srinivas Kandagatla
2022-02-25 11:31 ` Greg KH [this message]
2022-02-25 11:18 ` Greg KH
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=Yhi+CSZYUwvVPN3J@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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