From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: 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 gpio-intel tree
Date: Thu, 17 Apr 2025 15:44:47 +1000 [thread overview]
Message-ID: <20250417154447.642f2ec4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
Hi all,
The following commits are also in the gpio-brgl tree as different commits
(but the same patches):
8f4543e980ff ("gpio: ich: use new line value setter callbacks")
b7a49fd57be3 ("gpio: graniterapids: use new line value setter callbacks")
These are commits
69e230a0a288 ("gpio: ich: use new line value setter callbacks")
04eaa41eb8eb ("gpio: graniterapids: use new line value setter callbacks")
in the gpio-bgrl tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-04-17 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 5:44 Stephen Rothwell [this message]
2025-04-17 15:56 ` linux-next: duplicate patches in the gpio-intel tree Andy Shevchenko
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=20250417154447.642f2ec4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--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