From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yang Ruibin <11162571@vivo.com>, Mark Brown <broonie@kernel.org>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v2] drivers: spi: Insert the missing pci_dev_put()before return
Date: Fri, 30 Aug 2024 22:12:03 +0300 [thread overview]
Message-ID: <ZtIZg4Jy31GON1zw@smile.fi.intel.com> (raw)
In-Reply-To: <CAMuHMdWNjo69_W6f+R9QJJOf8uF0htg2XazeS-yjugJv3UM+kg@mail.gmail.com>
On Fri, Aug 30, 2024 at 10:55:06AM +0200, Geert Uytterhoeven wrote:
> On Thu, Aug 29, 2024 at 5:35 AM Yang Ruibin <11162571@vivo.com> wrote:
> > Increase the reference count by calling pci_get_slot(), and remember to
> > decrement the reference count by calling pci_dev_put().
> >
> > Signed-off-by: Yang Ruibin <11162571@vivo.com>
>
> Thanks for your patch, which is now commit 8a0ec8c2d736961f ("spi:
> Insert the missing pci_dev_put()before return") in spi/for-next.
Which should be reverted.
Who is going to send one?
I also have one revert for double applied spi-ppc44x commit.
But Mark haven't replied if I need to send a v2 of that as it has Subject and
first line of the commit message generated by `git revert` without editing.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-08-30 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 3:35 [PATCH v2] drivers: spi: Insert the missing pci_dev_put()before return Yang Ruibin
2024-08-29 17:38 ` Mark Brown
2024-08-30 8:55 ` Geert Uytterhoeven
2024-08-30 17:10 ` Krzysztof Kozlowski
2024-08-30 17:49 ` Jakub Kicinski
2024-09-02 7:15 ` Yuesong Li
2024-09-03 6:29 ` Greg Kroah-Hartman
2024-08-30 19:12 ` Andy Shevchenko [this message]
2024-08-30 19:56 ` Mark Brown
2024-09-02 10:21 ` Andy Shevchenko
2024-08-30 19:57 ` Mark Brown
2024-08-30 22:23 ` Nathan Chancellor
2024-09-02 11:48 ` Mark Brown
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=ZtIZg4Jy31GON1zw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=11162571@vivo.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=geert@linux-m68k.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=robert.jarzmik@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).