mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Santosh Shilimkar <ssantosh@kernel.org>
Cc: Kevin Hilman <khilman@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v2 0/2] memory: aemif: add support for machine code
Date: Tue, 24 Apr 2018 14:21:00 +0530	[thread overview]
Message-ID: <4d72accf-7d63-c725-0b67-253ed6818ae0@ti.com> (raw)
In-Reply-To: <0f2903da-b670-dc85-e61b-64cac90a6c34@oracle.com>

On Friday 20 April 2018 10:54 PM, santosh.shilimkar@oracle.com wrote:
> On 4/19/18 8:12 AM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> This is a follow-up to the series that contained both changes to the
>> aemif driver and platform code. It contains only the driver changes.
>>
>> As the first step in removing duplicate support for aemif from the
>> kernel we need to add support for board files to the aemif memory
>> driver.
>>
>> First patch just uses a static string for the ti-aemif driver name.
>>
>> The second adds support for board files to the aemif driver.
>>
>> This series includes changes requested by Sekhar in his code review:
>> - made aemif the parent of each sub-device before registering it
>> - documented the new members in aemif_platform_data
>>
>> v1 -> v2:
>> - actually iterate over abus entries instead of always accessing the
>>    first one
>>
>> Bartosz Golaszewski (2):
>>    memory: aemif: don't rely on kbuild for driver's name
>>    memory: aemif: add support for board files
>>
> Applied. Should show up in next soon.
> 
> Sekhar, You can use below branch.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git  'for_4.18/soc-drivers'

Thanks Santosh!

Regards,
Sekhar

      reply	other threads:[~2018-04-24  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 15:12 Bartosz Golaszewski
2018-04-19 15:12 ` [PATCH v2 1/2] memory: aemif: don't rely on kbuild for driver's name Bartosz Golaszewski
2018-04-19 15:12 ` [PATCH v2 2/2] memory: aemif: add support for board files Bartosz Golaszewski
2018-04-20 17:24 ` [PATCH v2 0/2] memory: aemif: add support for machine code santosh.shilimkar
2018-04-24  8:51   ` 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=4d72accf-7d63-c725-0b67-253ed6818ae0@ti.com \
    --to=nsekhar@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=santosh.shilimkar@oracle.com \
    --cc=ssantosh@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

all inboxes | Powered by JetHome®