From: Greg KH <gregkh@linuxfoundation.org>
To: srinivas.kandagatla@linaro.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] nvmem: fixes for v6.8
Date: Thu, 7 Mar 2024 20:22:18 +0000 [thread overview]
Message-ID: <2024030702-eggshell-impending-f817@gregkh> (raw)
In-Reply-To: <20240224114023.85535-1-srinivas.kandagatla@linaro.org>
On Sat, Feb 24, 2024 at 11:40:22AM +0000, srinivas.kandagatla@linaro.org wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>
> Here are one fix in nvmem for 6.8, Could you queue
> these for next possible rc.
Sorry, I got to these too late for 6.8, I've queued them up for -rc1
greg k-h
prev parent reply other threads:[~2024-03-07 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 11:40 [PATCH 0/1] nvmem: fixes for v6.8 srinivas.kandagatla
2024-02-24 11:40 ` [PATCH 1/1] nvmem: meson-efuse: fix function pointer type mismatch srinivas.kandagatla
2024-03-07 20:22 ` Greg KH [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=2024030702-eggshell-impending-f817@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.