From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Michael S. Tsirkin" <mst@redhat.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 vhost tree
Date: Thu, 18 Jul 2024 07:16:25 +0200 [thread overview]
Message-ID: <2024071818-resemble-errand-a58b@gregkh> (raw)
In-Reply-To: <20240718150141.49349347@canb.auug.org.au>
On Thu, Jul 18, 2024 at 03:01:41PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the char-misc tree as a different commit
> (but the same patch):
>
> 69eced9eb49a ("virtio: add missing MODULE_DESCRIPTION() macro")
>
> This is commit
>
> 89067019d7db ("virtio: add missing MODULE_DESCRIPTION() macro")
>
> in the char-misc tree.
Thanks, should be fine.
greg k-h
next prev parent reply other threads:[~2024-07-18 5:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 5:01 linux-next: duplicate patch in the vhost tree Stephen Rothwell
2024-07-18 5:16 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2024-10-24 4:15 Stephen Rothwell
2024-09-11 7:47 Stephen Rothwell
2024-09-11 10:41 ` Michael S. Tsirkin
2024-05-14 6:18 Stephen Rothwell
2024-02-23 3:25 Stephen Rothwell
2024-01-05 4:06 Stephen Rothwell
2023-06-05 2:24 Stephen Rothwell
2023-04-11 5:19 Stephen Rothwell
2023-04-11 22:18 ` Jonathan Corbet
2023-04-12 2:51 ` Michael S. Tsirkin
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=2024071818-resemble-errand-a58b@gregkh \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mst@redhat.com \
--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 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.