From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: 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 pinctrl-samsung tree
Date: Wed, 30 Apr 2025 10:29:12 +0200 [thread overview]
Message-ID: <4386227a-3dc9-42c4-9cc1-827dad1556be@kernel.org> (raw)
In-Reply-To: <20250430175001.4d12e01f@canb.auug.org.au>
On 30/04/2025 09:50, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the pinctrl tree as a different commit
> (but the same patch):
>
> 0a5b9be31f78 ("pinctrl: samsung: use new GPIO line value setter callbacks")
>
> This is commit
>
> 9e4c444755b1 ("pinctrl: samsung: use new GPIO line value setter callbacks")
>
Thanks, I will drop mine.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-30 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 7:50 linux-next: duplicate patch in the pinctrl-samsung tree Stephen Rothwell
2025-04-30 8:29 ` Krzysztof Kozlowski [this message]
2025-04-30 8:47 ` Linus Walleij
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=4386227a-3dc9-42c4-9cc1-827dad1556be@kernel.org \
--to=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=s.nawrocki@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox