From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Kosina <jkosina@suse.cz>,
Ivan Orlov <ivan.orlov0322@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the driver-core tree
Date: Tue, 15 Aug 2023 21:34:00 +1000 [thread overview]
Message-ID: <20230815213400.49afbd8f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
Hi all,
The following commits are also in the hid tree as different commits
(but the same patches):
32944855bac7 ("HID: hidraw: make hidraw_class structure const")
afdf5dd33a91 ("HID: roccat: make all 'class' structures const")
These are commits
21168bdba6ea ("HID: hidraw: make hidraw_class structure const")
fadfcf360161 ("HID: roccat: make all 'class' structures const")
in the hid tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-08-15 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 11:34 Stephen Rothwell [this message]
2023-08-22 11:51 ` linux-next: duplicate patches in the driver-core tree Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-10-16 4:12 Stephen Rothwell
2024-10-16 5:49 ` Greg KH
2023-12-11 4:24 Stephen Rothwell
2023-12-11 7:16 ` Greg KH
2023-02-02 1:12 Stephen Rothwell
2023-02-02 6:53 ` Sudeep Holla
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=20230815213400.49afbd8f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benjamin.tissoires@redhat.com \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.orlov0322@gmail.com \
--cc=jikos@kernel.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 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).