linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ivo.g.dimitrov.75@gmail.com (Ivaylo Dimitrov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Pass n900 MMC slot names in pdata for legacy user space
Date: Thu, 28 Apr 2016 23:33:38 +0300	[thread overview]
Message-ID: <572273A2.4050104@gmail.com> (raw)
In-Reply-To: <1461714383-9956-1-git-send-email-tony@atomide.com>

Hi,

On 27.04.2016 02:46, Tony Lindgren wrote:
> Hi all,
>
> N900 needs the MMC slot names to work. Let's pass them in pdata
> for now to remove the last remaining blocker for removing omap3
> legacy booting support for v4.8.
>
> Then when we have a generic DT binding for the slot names, we
> can use that assuming it will work for the n900 legacy user space.
>
> Regards,
>
> Tony
>
>
> Tony Lindgren (2):
>    ARM: OMAP2+: n900 needs MMC slot names for legacy user space
>    mmc: omap_hsmmc: Check if MMC slot name is passed in pdata
>
>   arch/arm/mach-omap2/pdata-quirks.c | 7 +++++++
>   drivers/mmc/host/omap_hsmmc.c      | 6 +++++-
>   2 files changed, 12 insertions(+), 1 deletion(-)
>

For both patches, you may add:

Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>

Thanks,
Ivo

      parent reply	other threads:[~2016-04-28 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 23:46 [PATCH 0/2] Pass n900 MMC slot names in pdata for legacy user space Tony Lindgren
2016-04-26 23:46 ` [PATCH 1/2] ARM: OMAP2+: n900 needs MMC slot names " Tony Lindgren
2016-04-27  8:48   ` Ulf Hansson
2016-04-27 14:17     ` Tony Lindgren
2016-05-02  7:05   ` Pavel Machek
2016-04-26 23:46 ` [PATCH 2/2] mmc: omap_hsmmc: Check if MMC slot name is passed in pdata Tony Lindgren
2016-04-27  8:52   ` Ulf Hansson
2016-04-27 14:17     ` Tony Lindgren
2016-04-28 20:33 ` Ivaylo Dimitrov [this message]

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=572273A2.4050104@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).