From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 vhost tree
Date: Tue, 11 Apr 2023 22:51:16 -0400 [thread overview]
Message-ID: <20230411224945-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <871qkqawqr.fsf@meer.lwn.net>
On Tue, Apr 11, 2023 at 04:18:36PM -0600, Jonathan Corbet wrote:
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>
> > Hi all,
> >
> > The following commit is also in the jc_docs tree as a different commit
> > (but the same patch):
> >
> > 3a9421482150 ("dma-api-howto: typo fix")
> >
> > This is commit
> >
> > 2ca956cf8834 ("dma-api-howto: typo fix")
> >
> > in the jc_docs tree.
>
> Michael, I'm a bit confused by this one...you sent it to me, but
> evidently didn't want me to take it? I can certainly drop it...
>
> Thanks,
>
> jon
Sorry, it's just a holiday here. dropped now.
--
MST
next prev parent reply other threads:[~2023-04-12 2:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 5:19 linux-next: duplicate patch in the vhost tree Stephen Rothwell
2023-04-11 22:18 ` Jonathan Corbet
2023-04-12 2:51 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 2:24 Stephen Rothwell
2024-01-05 4:06 Stephen Rothwell
2024-02-23 3:25 Stephen Rothwell
2024-05-14 6:18 Stephen Rothwell
2024-07-18 5:01 Stephen Rothwell
2024-07-18 5:16 ` Greg KH
2024-09-11 7:47 Stephen Rothwell
2024-09-11 10:41 ` Michael S. Tsirkin
2024-10-24 4:15 Stephen Rothwell
2025-08-27 2:46 Stephen Rothwell
2025-08-27 10:23 ` Michael S. Tsirkin
2025-08-27 17:26 ` Namhyung Kim
2025-08-27 22:04 ` Michael S. Tsirkin
2025-08-27 23:50 ` Namhyung Kim
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=20230411224945-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=corbet@lwn.net \
--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;
as well as URLs for NNTP newsgroup(s).