From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the mhi tree
Date: Fri, 21 Feb 2025 11:16:20 +0530 [thread overview]
Message-ID: <20250221054620.orulewump6jgzstz@thinkpad> (raw)
In-Reply-To: <20250221161344.09a6cf09@canb.auug.org.au>
On Fri, Feb 21, 2025 at 04:13:44PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the char-misc.current tree as a different
> commit (but the same patch):
>
> 0f96e4d32983 ("bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock")
>
> This is commit
>
> a321d163de3d ("bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock")
>
> in the char-misc.current tree.
>
Dropped the commit from mhi-next now!
- Mani
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2025-02-21 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 5:13 linux-next: duplicate patch in the mhi tree Stephen Rothwell
2025-02-21 5:46 ` Manivannan Sadhasivam [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=20250221054620.orulewump6jgzstz@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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