From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Jérôme Pouiller" <Jerome.Pouiller@silabs.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Tony Lindgren" <tony@atomide.com>,
"Bean Huo" <beanhuo@micron.com>,
"Gražvydas Ignotas" <notasas@gmail.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
letux-kernel@openphoenux.org, kernel@pyra-handheld.com
Subject: Re: [RFC v4 5/6] mmc: core: transplant ti,wl1251 quirks from to be retired omap_hsmmc
Date: Wed, 10 Nov 2021 18:09:26 +0100 [thread overview]
Message-ID: <B7FC3305-7C27-4D17-9BBD-856CF6C542C8@goldelico.com> (raw)
In-Reply-To: <CAPDyKFqsBkWBajYvS2DXsHzO01-hgQp7YuzTs61N7vmLkZLgKg@mail.gmail.com>
> Am 10.11.2021 um 18:03 schrieb Ulf Hansson <ulf.hansson@linaro.org>:
>
> On Wed, 10 Nov 2021 at 17:36, H. Nikolaus Schaller <hns@goldelico.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
next prev parent reply other threads:[~2021-11-10 17:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 9:05 [RFC v4 0/6] mmc: core: extend mmc_fixup_device and transplant ti,wl1251 quirks from to be retired omap_hsmmc H. Nikolaus Schaller
2021-11-05 9:05 ` [RFC v4 1/6] mmc: core: rewrite mmc_fixup_device() H. Nikolaus Schaller
2021-11-05 9:05 ` [RFC v4 2/6] mmc: core: allow to match the device tree to apply quirks H. Nikolaus Schaller
2021-11-05 14:27 ` Jérôme Pouiller
2021-11-06 14:31 ` H. Nikolaus Schaller
2021-11-08 15:00 ` Ulf Hansson
2021-11-08 15:34 ` Jérôme Pouiller
2021-11-08 16:01 ` H. Nikolaus Schaller
2021-11-05 9:05 ` [RFC v4 3/6] mmc: core: provide macro and table " H. Nikolaus Schaller
2021-11-05 9:05 ` [RFC v4 4/6] mmc: core: add new calls to mmc_fixup_device(sdio_card_init_methods) H. Nikolaus Schaller
2021-11-08 15:08 ` Ulf Hansson
2021-11-08 16:07 ` H. Nikolaus Schaller
2021-11-08 15:39 ` Jérôme Pouiller
2021-11-08 16:04 ` H. Nikolaus Schaller
2021-11-05 9:05 ` [RFC v4 5/6] mmc: core: transplant ti,wl1251 quirks from to be retired omap_hsmmc H. Nikolaus Schaller
2021-11-08 15:33 ` Ulf Hansson
2021-11-08 16:08 ` H. Nikolaus Schaller
2021-11-09 10:58 ` H. Nikolaus Schaller
2021-11-09 20:01 ` Ulf Hansson
2021-11-10 16:36 ` H. Nikolaus Schaller
2021-11-10 17:03 ` Ulf Hansson
2021-11-10 17:09 ` H. Nikolaus Schaller [this message]
2021-11-05 9:05 ` [RFC v4 6/6] mmc: host: omap_hsmmc: revert special init for wl1251 H. Nikolaus Schaller
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=B7FC3305-7C27-4D17-9BBD-856CF6C542C8@goldelico.com \
--to=hns@goldelico.com \
--cc=Jerome.Pouiller@silabs.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=shawn.lin@rock-chips.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).