On 02/11/2023 19:00:27+0200, Andy Shevchenko wrote: > On Thu, Nov 2, 2023 at 6:50 PM Alexandre Belloni > <alexandre.belloni@xxxxxxxxxxx> wrote: > > On 02/11/2023 18:46:05+0200, Andy Shevchenko wrote: > > > On Thu, Nov 2, 2023 at 6:17 PM Esteban Blanc <eblanc@xxxxxxxxxxxx> wrote: > > > > On Thu Nov 2, 2023 at 5:00 PM CET, Andy Shevchenko wrote: > > > > > On Thu, Nov 2, 2023 at 3:26 PM Esteban Blanc <eblanc@xxxxxxxxxxxx> wrote: > > > > > > > > > > > Notes: > > > > > > This patch was picked from a series since there is no dependency between > > > > > > the two patches. > > > > > > > > > > Not sure if RTC maintainer uses the b4 tool, but as I said in previous > > > > > email for pinctrl change, there is no need to resend. b4 has an > > > > > ability to select patches from the series to be applied. > > > > > > > > Oh that's good to know, I was not aware of that. > > > > I resent it because there was some minor nits that I fixed on both > > > > patches. > > > > > > Ah, that was not reflected in the changelog... > > > > For the record, I'm using b4 but it was not clear which path the patches > > would take. > > You mean in the initial series? You take it by direct message-id with > -P _. Or did I misunderstand the problem? No I mean it was not clear whether I should take the patch or it would get through MFD. -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
