From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 2/2] ARM: da850: add the nand dev_id to the clock lookup table
Date: Mon, 23 Jan 2017 21:29:15 +0530 [thread overview]
Message-ID: <ca65a02c-a067-9a4a-af7d-98bace48c5fd@ti.com> (raw)
In-Reply-To: <CAMpxmJUcPQJw3YKEtmnqMnW1OqEH1mz3hosYJc2arK65Qwkz+Q@mail.gmail.com>
On Monday 23 January 2017 09:02 PM, Bartosz Golaszewski wrote:
> 2017-01-23 16:17 GMT+01:00 Sekhar Nori <nsekhar@ti.com>:
>> On Friday 20 January 2017 07:16 PM, Sekhar Nori wrote:
>>> On Friday 13 January 2017 03:30 PM, Bartosz Golaszewski wrote:
>>>> The aemif driver can now access struct of_dev_auxdata (using platform
>>>> data).
>>>>
>>>> Add the device id to the clock lookup table for the nand clock and
>>>> create a separate lookup table for aemif subnodes.
>>>>
>>>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>
>>> Applied to v4.11/soc
>>
>> I forgot that this has a build dependency with 1/2. Instead of creating
>> a dependency with Greg's tree, I think I will send it for v4.12. This is
>> a clean-up and does not add a new feature from a user's perspective so I
>> hope thats okay.
>>
>> Thanks,
>> Sekhar
>
> Hi Sekhar,
>
> Greg picked up both patches - 1/2 is already in char-misc-next[1].
Alright. I did not notice any merge conflicts between this and what I
plan to queue so I guess we are okay.
Thanks
Sekhar
prev parent reply other threads:[~2017-01-23 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 10:00 [PATCH RESEND 0/2] ARM: davinci: improve the nand clock lookup Bartosz Golaszewski
2017-01-13 10:00 ` [PATCH RESEND 1/2] memory: aemif: allow passing device lookup table as platform data Bartosz Golaszewski
2017-01-13 16:36 ` Santosh Shilimkar
2017-01-13 10:00 ` [PATCH RESEND 2/2] ARM: da850: add the nand dev_id to the clock lookup table Bartosz Golaszewski
2017-01-20 13:46 ` Sekhar Nori
2017-01-23 15:17 ` Sekhar Nori
2017-01-23 15:32 ` Bartosz Golaszewski
2017-01-23 15:59 ` 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=ca65a02c-a067-9a4a-af7d-98bace48c5fd@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).