From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/13] nvmem: patches (set 1) for 6.15
Date: Mon, 31 Mar 2025 06:04:35 +0200 [thread overview]
Message-ID: <2025033114-slept-train-df46@gregkh> (raw)
In-Reply-To: <a85e75dc-8ea2-42d1-9b70-124196439fde@linaro.org>
On Sun, Mar 30, 2025 at 10:03:39PM +0100, Srinivas Kandagatla wrote:
> Hi Greg,
>
> On 30/03/2025 19:30, Greg KH wrote:
> > On Tue, Mar 25, 2025 at 11:31:38AM +0000, Srinivas Kandagatla wrote:
> > > Hi Greg,
> > >
> > > Just want to ping you incase these patches fell through the cracks.
> > >
> > > Normally you pick nvmem series much earlier.
> > >
> > > Pl, let me know if there is anything that I can do to help.
> >
> > Crap, I missed these, so sorry about that. Are these also in linux-next
> > from your development tree? If so, I can suck them in next week and get
> > them to Linus for -rc1.
> Yes, these are in linux-next.
>
> pulling it for next rc1 would really help,
Ok, cool, after Linus takes this pull request I'll sync up with this and
send it to him as well.
thanks!
greg k-h
next prev parent reply other threads:[~2025-03-31 4:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 14:56 [PATCH v2 00/13] nvmem: patches (set 1) for 6.15 srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 01/13] nvmem: rockchip-otp: Move read-offset into variant-data srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 02/13] dt-bindings: nvmem: rockchip,otp: add missing limits for clock-names srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 03/13] dt-bindings: nvmem: rockchip,otp: Add compatible for RK3576 srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 04/13] nvmem: rockchip-otp: add rk3576 variant data srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 05/13] dt-bindings: nvmem: qfprom: Add X1E80100 compatible srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 06/13] dt-bindings: nvmem: Add compatible for MS8937 srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 07/13] dt-bindings: nvmem: fixed-cell: increase bits start value to 31 srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 08/13] nvmem: core: fix bit offsets of more than one byte srinivas.kandagatla
2025-03-09 14:56 ` [PATCH v2 09/13] nvmem: core: verify cell's raw_len srinivas.kandagatla
2025-03-09 14:57 ` [PATCH v2 10/13] nvmem: core: update raw_len if the bit reading is required srinivas.kandagatla
2025-03-09 14:57 ` [PATCH v2 11/13] nvmem: qfprom: switch to 4-byte aligned reads srinivas.kandagatla
2025-03-09 14:57 ` [PATCH v2 12/13] dt-bindings: nvmem: Add compatible for IPQ5018 srinivas.kandagatla
2025-03-09 14:57 ` [PATCH v2 13/13] dt-bindings: nvmem: Add compatible for MSM8960 srinivas.kandagatla
2025-03-25 11:31 ` [PATCH v2 00/13] nvmem: patches (set 1) for 6.15 Srinivas Kandagatla
2025-03-30 18:30 ` Greg KH
2025-03-30 21:03 ` Srinivas Kandagatla
2025-03-31 4:04 ` Greg KH [this message]
2025-04-01 19:18 ` Greg KH
2025-04-02 8:19 ` Srinivas Kandagatla
2025-04-02 11:31 ` Greg KH
2025-04-03 9:18 ` Srinivas Kandagatla
2025-04-03 9:25 ` Dmitry Baryshkov
2025-04-03 9:27 ` Srinivas Kandagatla
2025-04-03 9:31 ` Dmitry Baryshkov
2025-04-03 9:35 ` Srinivas Kandagatla
2025-04-03 9:38 ` Dmitry Baryshkov
2025-04-03 13:52 ` Greg KH
2025-04-03 13:58 ` Srinivas Kandagatla
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=2025033114-slept-train-df46@gregkh \
--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 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.