From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH] eeprom: at24: Use pm_runtime_resume_and_get to simplify the code
Date: Fri, 5 Jan 2024 10:37:45 +0100 [thread overview]
Message-ID: <2024010512-dancing-multiply-26d1@gregkh> (raw)
In-Reply-To: <CAMRc=MetjCb-42uPBEU53RFD1_CcwJ9d22eGHbX1HESOdp1nig@mail.gmail.com>
On Fri, Jan 05, 2024 at 10:35:18AM +0100, Bartosz Golaszewski wrote:
> On Fri, Jan 5, 2024 at 10:32 AM Heiner Kallweit <hkallweit1@gmail.com> wrote:
> >
> > On 05.01.2024 10:22, Bartosz Golaszewski wrote:
> > > On Wed, Dec 20, 2023 at 4:11 PM Heiner Kallweit <hkallweit1@gmail.com> wrote:
> > >>
> > >> Use helper pm_runtime_resume_and_get() to simplify the code.
> > >>
> > >> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> > >> ---
> > >
> > > This looks good, but I had already sent out my PR to Wolfram when you
> > > sent it, so I'll queue it for v6.9.
> > >
> > I just received an automated note from Greg that he applied this patch
> > via the char-misc tree. The same applies to "eeprom: at24: Probe for
> > DDR3 thermal sensor in the SPD case"
> >
> > > Bart
> > Heiner
> >
>
> Huh? Greg, I typically pick up patches for at24 and send them through
> the I2C tree (as per the MAINTAINERS file).
Sorry about that, I caught this in my sweep of patches sent to me. As
you wanted it applied anyway, all should be good, git can handle the
merge just fine.
thanks,
greg k-h
prev parent reply other threads:[~2024-01-05 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 15:11 [PATCH] eeprom: at24: Use pm_runtime_resume_and_get to simplify the code Heiner Kallweit
2024-01-05 9:22 ` Bartosz Golaszewski
2024-01-05 9:32 ` Heiner Kallweit
2024-01-05 9:35 ` Bartosz Golaszewski
2024-01-05 9:37 ` Greg Kroah-Hartman [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=2024010512-dancing-multiply-26d1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=hkallweit1@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@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 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.