devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "ivan.khoronzhuk" <ivan.khoronzhuk@ti.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	linux@arm.linux.org.uk, mark.rutland@arm.com,
	devicetree@vger.kernel.org, grygorii.strashko@ti.com,
	pawel.moll@arm.com, swarren@wwwdotorg.org,
	ijc+devicetree@hellion.org.uk, galak@kernel.crashing.org,
	rob.herring@calxeda.com, linux-kernel@vger.kernel.org,
	linux-mtd@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	Rob Landley <rob@landley.net>
Subject: Re: [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif
Date: Fri, 10 Jan 2014 12:45:00 +0530	[thread overview]
Message-ID: <52CF9DF4.8000607@ti.com> (raw)
In-Reply-To: <20140109163305.GC28655@norris-Latitude-E6410>

On Thursday 09 January 2014 10:03 PM, Brian Norris wrote:
> On Thu, Jan 09, 2014 at 04:09:00PM +0530, Sekhar Nori wrote:
>> On Thursday 26 December 2013 05:36 PM, ivan.khoronzhuk wrote:
>>> On 12/18/2013 02:13 PM, Sekhar Nori wrote:
>>>> On Wednesday 18 December 2013 05:21 PM, ivan.khoronzhuk wrote:
>>>>> Hi, Sekhar
>>>>>
>>>>> This patch is based on "Reuse davinci-nand driver for Keystone arch"
>>>>> series.
>>>>> The series has passed review at https://lkml.org/lkml/2013/12/17/241
>>>>> and can be found at http://git.infradead.org/l2-mtd.git
>>>>>
>>>>> This patch can be still applied on top of the series without conflicts.
>>>>>
>>>>> Can you please pick up the $subject patch if you are OK with it?
>>>>
>>>> I have no problems with the patch and can pick it too, but need ack from
>>>> MTD maintainer (David) as it touches drivers/mtd/ too.
>>>>
>>>> David,
>>>>
>>>> If you do not have the patch, we can resend it.
>>>>
>>>> Thanks,
>>>> Sekhar
>>>>
>>>
>>> Hi Brian,
>>>
>>> Do you agree if this patch will go through Davinci tree?
>>>
>>> This is the last one we need to reuse Davinci Nand driver for Keystone.
>>
>> Since we never got an ack from MTD folks, I am going and go ahead and
>> try pushing this through ARM-SoC regardless. I will CC the MTD
>> maintainers on the pull request so any objections could even be posted
>> there.
> 
> Sorry, I've been a little busy / out for vacation. The MTD parts look OK
> to me. Feel free to take it in your tree.
> 
> Acked-by: Brian Norris <computersforpeace@gmail.com>

Actually the NAND portion conflicts with some of the changes from Ivan
you took recently. I think it will be better if you take this patch too
with my ack. For me to take it through ARM-SoC, I need an immutable
branch from you - with commits same as what you will eventually be
sending to Linus, based on which I can send a pull request.

In any case, there is a v4 needed to fix a build and checkpatch error I
just noticed. I will send it out soon.

Thanks,
Sekhar

      parent reply	other threads:[~2014-01-10  7:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 18:11 [PATCH v3] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif Ivan Khoronzhuk
2013-12-06 21:04 ` Sekhar Nori
2013-12-09  8:58   ` ivan.khoronzhuk
     [not found] ` <1386267092-18615-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2013-12-18 11:51   ` ivan.khoronzhuk
     [not found]     ` <52B18C44.2000305-l0cyMroinI0@public.gmane.org>
2013-12-18 12:13       ` Sekhar Nori
2013-12-26 12:06         ` ivan.khoronzhuk
2014-01-09 10:39           ` Sekhar Nori
2014-01-09 16:33             ` Brian Norris
2014-01-10  4:19               ` Sekhar Nori
2014-01-10  7:15               ` Sekhar Nori [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=52CF9DF4.8000607@ti.com \
    --to=nsekhar@ti.com \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@kernel.crashing.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ivan.khoronzhuk@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=santosh.shilimkar@ti.com \
    --cc=swarren@wwwdotorg.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).