From: Ulf Hansson <ulf.hansson@linaro.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ulf Magnusson <ulfalizer@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms+renesas@verge.net.au>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
devicetree@vger.kernel.org,
Linux-sh list <linux-sh@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Lee Jones <lee.jones@linaro.org>, Rich Felker <dalias@libc.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 00/16] mmc: tmio: another batch of TMIO MMC fixes and cleanups
Date: Wed, 14 Feb 2018 10:46:39 +0100 [thread overview]
Message-ID: <CAPDyKFrCc-rFs_u_sSd=YN5SKFnE-vmjJabb+Sycynv2Q43ngQ@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQaEJFH7Y+XsGEWDbrDkXTt35Yqd5DBmk0hpd6bggy+hQ@mail.gmail.com>
On 14 February 2018 at 10:43, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> Hi Ulf,
>
>
> 2018-02-14 18:36 GMT+09:00 Ulf Hansson <ulf.hansson@linaro.org>:
>> On 7 February 2018 at 20:11, Wolfram Sang <wsa@the-dreams.de> wrote:
>>>
>>>> I picked patch5 and patch6, as those seemed trivial. Unless there is a
>>>> rc9, let's aim for 4.17 for the rest.
>>>
>>> I can't find the branch where you picked these patches? I wanted to use
>>> it to apply the rest of the patches. They don't seem to fit on v4.15
>>> or current linus/master. Can you share this branch?
>>
>> You need to check again. :-)
>>
>> Patches up and to patch6 is already in Linus' tree v.16rc1, those I
>> carried for quite a while on my next branch before sending them in the
>> PR to Linus.
>>
>>>
>>> I will do reviewing now "visually". But please wait until I tested them
>>> before applying.
>>
>> I am eager to apply those patches you already have reviewed (to
>> patch14), as those mostly seemed rather trivial and should be nice
>> cleanups.
>>
>> Do you mind me going ahead, then you can continue and review/test the rest?
>>
>
>
> If you move forward, please fix-up the commit log of the patch 11.
> (https://patchwork.kernel.org/patch/10170007/)
>
>
> Documentation/devicetree/bindings/mmc/tmio_mmc.txt
>
> ->
>
> Documentation/devicetree/bindings/mmc/mmc.txt
Thanks for the reminder. Yes I can amend the patch, no worries.
Kind regards
Uffe
next prev parent reply other threads:[~2018-02-14 9:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 16:28 [PATCH v3 00/16] mmc: tmio: another batch of TMIO MMC fixes and cleanups Masahiro Yamada
[not found] ` <1516206496-16612-1-git-send-email-yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
2018-01-17 16:28 ` [PATCH v3 11/16] mmc: tmio: deprecate "toshiba,mmc-wrprotect-disable" DT property Masahiro Yamada
2018-01-18 1:58 ` Masahiro Yamada
[not found] ` <CAK7LNAQUJw-fjuJO68Kvskn8BRYW3rZj4YMtbo-Oxfv7c=6Ggg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-29 17:18 ` Rob Herring
2018-02-07 19:32 ` Wolfram Sang
2018-03-18 2:46 ` Masahiro Yamada
2018-01-18 8:13 ` [PATCH v3 00/16] mmc: tmio: another batch of TMIO MMC fixes and cleanups Ulf Hansson
2018-02-07 19:11 ` Wolfram Sang
2018-02-14 9:36 ` Ulf Hansson
2018-02-14 9:43 ` Masahiro Yamada
2018-02-14 9:46 ` Ulf Hansson [this message]
[not found] ` <CAPDyKFoxp7p0atQTV=PoQ7Bwt0fOs2aEq1KJHPtrq+zA3eFYgw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-14 10:23 ` Wolfram Sang
2018-02-14 10:39 ` Ulf Hansson
2018-03-04 22:42 ` Wolfram Sang
2018-03-05 8:45 ` Ulf Hansson
2018-03-05 9:22 ` Wolfram Sang
2018-03-05 9:34 ` Masahiro Yamada
2018-03-05 9:39 ` Wolfram Sang
2018-03-05 12:06 ` Ulf Hansson
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='CAPDyKFrCc-rFs_u_sSd=YN5SKFnE-vmjJabb+Sycynv2Q43ngQ@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=dalias@libc.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=ulfalizer@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
--cc=yamada.masahiro@socionext.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
--cc=ysato@users.sourceforge.jp \
/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).