[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdaxTJ96hpJqs=xWVD4gSLdgc=m9uq+rbJKrJL+jgC645g@mail.gmail.com>
Date: Wed, 30 Apr 2025 10:47:32 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Sylwester Nawrocki <s.nawrocki@...sung.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the pinctrl-samsung tree
On Wed, Apr 30, 2025 at 10:29 AM Krzysztof Kozlowski <krzk@...nel.org> wrote:
> 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.
Thanks Krzysztof, my bad I didn't think about splitting the series across
submaintainers, I should have. I hope this doesn't collide with anything
in your tree.
Yours,
Linus Walleij
Powered by blists - more mailing lists