[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <B7FC3305-7C27-4D17-9BBD-856CF6C542C8@goldelico.com>
Date: Wed, 10 Nov 2021 18:09:26 +0100
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Jérôme Pouiller <Jerome.Pouiller@...abs.com>,
Avri Altman <avri.altman@....com>,
Shawn Lin <shawn.lin@...k-chips.com>,
Linus Walleij <linus.walleij@...aro.org>,
Tony Lindgren <tony@...mide.com>,
Bean Huo <beanhuo@...ron.com>,
Gražvydas Ignotas <notasas@...il.com>,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
letux-kernel@...nphoenux.org, kernel@...a-handheld.com
Subject: Re: [RFC v4 5/6] mmc: core: transplant ti,wl1251 quirks from to be
retired omap_hsmmc
> Am 10.11.2021 um 18:03 schrieb Ulf Hansson <ulf.hansson@...aro.org>:
>
> On Wed, 10 Nov 2021 at 17:36, H. Nikolaus Schaller <hns@...delico.com> wrote:
>>
>>
>> Indeed we can. That is great.
>>
>> Now the question is how to handle the dependency on your patch.
>> Somehow we must ensure that it is merged before my $subject patch.
>> Even if someone decides to backport this to stable.
>
> Yes, I can pick up my patch first. As it's not really fixing a
> problem, but rather preparing for your series to work better, I don't
> think we need to care about stable backports, at least for now.
>
> If you re-submit before rc1, then just include my patch early in your series.
Ok, I'll submit a v2 asap (isn't much work since I have your patch already in my test branch).
BR and thanks,
Nikolaus
Powered by blists - more mailing lists