linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Greg Ungerer <gregungerer@westnet.com.au>,
	Angelo Dureghello <angelo.dureghello@timesys.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	linux-m68k@vger.kernel.org
Subject: Re: [PATCH v3 1/3] m68k: mcf5441x: add support for esdhc mmc controller
Date: Wed, 13 May 2020 13:59:10 +0200	[thread overview]
Message-ID: <CAPDyKFqdGGfCurSRG8poO2aCbOmRb9so7-zarKEb1yUnBP=GXA@mail.gmail.com> (raw)
In-Reply-To: <bde7080c-298d-c28b-5986-dbabc95985bf@westnet.com.au>

On Tue, 12 May 2020 at 17:09, Greg Ungerer <gregungerer@westnet.com.au> wrote:
>
> Hi Ulf,
>
> On 7/5/20 7:13 pm, Ulf Hansson wrote:
> > + Geert
> >
> > On Sat, 2 May 2020 at 01:54, Angelo Dureghello
> > <angelo.dureghello@timesys.com> wrote:
> >>
> >> Add support for sdhci-edshc mmc controller.
> >>
> >> Signed-off-by: Angelo Dureghello <angelo.dureghello@timesys.com>
> >> ---
> >> Changes for v3:
> >> - removed volatile cast from clk.c
> >> ---
> >>   arch/m68k/coldfire/clk.c                    | 15 ++++++++++
> >>   arch/m68k/coldfire/device.c                 | 33 +++++++++++++++++++--
> >>   arch/m68k/coldfire/m5441x.c                 | 12 +++++++-
> >>   arch/m68k/include/asm/m5441xsim.h           | 19 ++++++++++++
> >>   arch/m68k/include/asm/mcfclk.h              |  2 ++
> >>   include/linux/platform_data/mmc-esdhc-mcf.h | 17 +++++++++++
> >>   6 files changed, 95 insertions(+), 3 deletions(-)
> >>   create mode 100644 include/linux/platform_data/mmc-esdhc-mcf.h
> >
> > Not sure what's the best way to deal with this patch. I looped in
> > Geert to get some input.
> >
> > If it looks okay and the risk is minimal for conflicts, I can carry it
> > via my tree, but then I need an ack from Geert.
>
> I can carry just this patch in the m68knommu git tree it you prefer.
> Should be no conflicts that way. But really if you want to carry it
> with all the others I don't have a problem with that either.

It looks like the new platform data header file is being used by the
mmc patch in 3/3, so it's probably easiest if I take them all via my
mmc tree.

Anyway, I will wait for a v4 from Angelo to address the comments.

[...]

Kind regards
Uffe

  reply	other threads:[~2020-05-13 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 23:59 [PATCH v3 1/3] m68k: mcf5441x: add support for esdhc mmc controller Angelo Dureghello
2020-05-01 23:59 ` [PATCH v3 2/3] mmc: sdhci: add quirks for be to le byte swapping Angelo Dureghello
2020-05-01 23:59 ` [PATCH v3 3/3] mmc: host: add Coldfire esdhc support Angelo Dureghello
2020-05-07  9:13 ` [PATCH v3 1/3] m68k: mcf5441x: add support for esdhc mmc controller Ulf Hansson
2020-05-07  9:23   ` Geert Uytterhoeven
2020-05-12 15:09   ` Greg Ungerer
2020-05-13 11:59     ` Ulf Hansson [this message]
2020-05-13 12:24       ` Greg Ungerer
2020-05-12 15:06 ` Greg Ungerer
2020-05-12 18:05   ` Angelo Dureghello

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='CAPDyKFqdGGfCurSRG8poO2aCbOmRb9so7-zarKEb1yUnBP=GXA@mail.gmail.com' \
    --to=ulf.hansson@linaro.org \
    --cc=adrian.hunter@intel.com \
    --cc=angelo.dureghello@timesys.com \
    --cc=geert@linux-m68k.org \
    --cc=gregungerer@westnet.com.au \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.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).