All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: David Lechner <david@lechnology.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Kevin Hilman <khilman@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v3 00/13] ARM: davinci: remove duplicate aemif support
Date: Wed, 4 Jul 2018 12:05:29 +0530	[thread overview]
Message-ID: <e1222b3c-dfa4-4cb0-eebf-8e2550e9d674@ti.com> (raw)
In-Reply-To: <59fdc532-bb72-ffae-cfb6-a7f156c14771@lechnology.com>

Hi David,

On Monday 02 July 2018 09:02 PM, David Lechner wrote:
> On 07/02/2018 07:28 AM, Sekhar Nori wrote:
>> Hi David, Stephen,
>>
>> On Thursday 28 June 2018 03:27 PM, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>
>>> This series moves all aemif/nand users to using the ti-aemif platform
>>> driver located in drivers/memory instead of the older API located in
>>> mach-davinci.
>>>
>>> First five patches add necessary changes to the clock driver. Next
>>> seven convert the board files to using the ti-aemif driver. Last patch
>>> removes now dead code.
>>
>> How do you want to handle this series? I can apply the series and
>> provide you an immutable branch on v4.18-rc1 with the clock patches
>> applied if that can work.
> 
> Sounds good to me. But I'm new to this maintainer thing, so maybe
> there is something to consider that I haven't thought of?

I don't think there is more to it. Ultimately there should not be two
commits for the same patch. Either you can apply and share the commit to
use or I can do that as well. I am equally fine either way.

Regards,
Sekhar

WARNING: multiple messages have this Message-ID (diff)
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 00/13] ARM: davinci: remove duplicate aemif support
Date: Wed, 4 Jul 2018 12:05:29 +0530	[thread overview]
Message-ID: <e1222b3c-dfa4-4cb0-eebf-8e2550e9d674@ti.com> (raw)
In-Reply-To: <59fdc532-bb72-ffae-cfb6-a7f156c14771@lechnology.com>

Hi David,

On Monday 02 July 2018 09:02 PM, David Lechner wrote:
> On 07/02/2018 07:28 AM, Sekhar Nori wrote:
>> Hi David, Stephen,
>>
>> On Thursday 28 June 2018 03:27 PM, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>
>>> This series moves all aemif/nand users to using the ti-aemif platform
>>> driver located in drivers/memory instead of the older API located in
>>> mach-davinci.
>>>
>>> First five patches add necessary changes to the clock driver. Next
>>> seven convert the board files to using the ti-aemif driver. Last patch
>>> removes now dead code.
>>
>> How do you want to handle this series? I can apply the series and
>> provide you an immutable branch on v4.18-rc1 with the clock patches
>> applied if that can work.
> 
> Sounds good to me. But I'm new to this maintainer thing, so maybe
> there is something to consider that I haven't thought of?

I don't think there is more to it. Ultimately there should not be two
commits for the same patch. Either you can apply and share the commit to
use or I can do that as well. I am equally fine either way.

Regards,
Sekhar

  reply	other threads:[~2018-07-04  6:36 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28  9:57 [PATCH v3 00/13] ARM: davinci: remove duplicate aemif support Bartosz Golaszewski
2018-06-28  9:57 ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 01/13] clk: davinci: psc-da850: remove the 'davinci_nand.0" lookup Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-07-06 17:40   ` David Lechner
2018-07-06 17:40     ` David Lechner
2018-06-28  9:57 ` [PATCH v3 02/13] clk: davinci: psc-dm365: use two lookup entries for the aemif clock Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-07-06 17:40   ` David Lechner
2018-07-06 17:40     ` David Lechner
2018-06-28  9:57 ` [PATCH v3 03/13] clk: davinci: psc-dm644x: " Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-07-06 17:40   ` David Lechner
2018-07-06 17:40     ` David Lechner
2018-06-28  9:57 ` [PATCH v3 04/13] clk: davinci: psc-dm646x: " Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-07-06 17:41   ` David Lechner
2018-07-06 17:41     ` David Lechner
2018-06-28  9:57 ` [PATCH v3 05/13] clk: davinci: psc-da830: add a lookup entry for " Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-07-06 17:41   ` David Lechner
2018-07-06 17:41     ` David Lechner
2018-06-28  9:57 ` [PATCH v3 06/13] ARM: davinci: omapl138-hawk: add aemif & nand support Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 07/13] ARM: davinci: da850-evm: use aemif platform driver in legacy mode Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 08/13] ARM: davinci: dm365-evm: use the ti-aemif soc driver Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 09/13] ARM: davinci: dm644x-evm: use aemif platform driver Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 10/13] ARM: davinci: da830-evm: " Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 11/13] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 12/13] ARM: davinci: mityomapl138: " Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-06-28  9:57 ` [PATCH v3 13/13] ARM: davinci: unduplicate aemif support Bartosz Golaszewski
2018-06-28  9:57   ` Bartosz Golaszewski
2018-07-02 12:28 ` [PATCH v3 00/13] ARM: davinci: remove duplicate " Sekhar Nori
2018-07-02 12:28   ` Sekhar Nori
2018-07-02 15:32   ` David Lechner
2018-07-02 15:32     ` David Lechner
2018-07-04  6:35     ` Sekhar Nori [this message]
2018-07-04  6:35       ` Sekhar Nori
2018-07-06 17:39       ` David Lechner
2018-07-06 17:39         ` David Lechner
2018-07-10 10:19         ` Sekhar Nori
2018-07-10 10:19           ` Sekhar Nori
2018-08-06 16:35           ` David Lechner
2018-08-06 16:35             ` David Lechner
2018-08-07  6:02             ` Sekhar Nori
2018-08-07  6:02               ` Sekhar Nori

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=e1222b3c-dfa4-4cb0-eebf-8e2550e9d674@ti.com \
    --to=nsekhar@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=david@lechnology.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.