public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	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>,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Cc: notasas@gmail.com, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org,
	kernel@pyra-handheld.com,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [RFC v2 0/2]
Date: Tue, 02 Nov 2021 12:14:01 +0100	[thread overview]
Message-ID: <65944054.TfMWBj6dXo@pc-42> (raw)
In-Reply-To: <cover.1635759337.git.hns@goldelico.com>

Hello Nikolaus,

On Monday 1 November 2021 10:39:10 CET H. Nikolaus Schaller wrote:
> 
> RFC V2 2021-11-01 10:24:26:
> * reworked to not misuse mmc_select_card() but add a call to
>   mmc_fixup_device() right after where host->ops->init_card
>   was called before to apply the wl1251 specific quirks.
>   Device tree matching is done by a new table passed to mmc_fixup_device().
>   suggested by: ulf.hansson@linaro.org
>   based on patches by: jerome.pouiller@silabs.com

To make review easier, I think you can include these patches
in this series (BTW, I have no time to care of them until end
of next week. So, it will probably go faster if you take over
these patches).

(I also suggest to add a title to your series to make your work
easier to track.)


-- 
Jérôme Pouiller



  parent reply	other threads:[~2021-11-02 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  9:39 [RFC v2 0/2] H. Nikolaus Schaller
2021-11-01  9:39 ` [RFC v2 1/2] mmc: core: transplant ti,wl1251 quirks from to be retired omap_hsmmc H. Nikolaus Schaller
2021-11-01  9:39 ` [RFC v2 2/2] mmc: host: omap_hsmmc: revert special init for wl1251 H. Nikolaus Schaller
2021-11-02 11:14 ` Jérôme Pouiller [this message]
2021-11-02 13:13   ` [RFC v2 0/2] mmc_fixup_device 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=65944054.TfMWBj6dXo@pc-42 \
    --to=jerome.pouiller@silabs.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=hns@goldelico.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