From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: Keystone reset driver 3.16
Date: Tue, 27 May 2014 10:07:01 -0400 [thread overview]
Message-ID: <53849C05.8090004@ti.com> (raw)
In-Reply-To: <1401175584.4090.22.camel@paszta.hi.pengutronix.de>
Olof,
On Tuesday 27 May 2014 03:26 AM, Philipp Zabel wrote:
> Hi Olof, Santosh,
>
> Am Montag, den 26.05.2014, 14:26 -0700 schrieb Olof Johansson:
>> On Fri, May 23, 2014 at 05:29:57PM -0400, Santosh Shilimkar wrote:
>>> Hi Arm-soc folks,
>>>
>>> Please pull below keystone reset driver for 3.16 . To avoid merge conflict
>>> with earlier keystone-soc pull request[1], I have based the subject pull
>>> request on top of it. It merges cleanly with arm-soc 'next/soc2' head. Please
>>> apply it against 'next/soc2'. Thanks
>>
>> Hi,
>>
>> I notice this driver doesn't have an ack from Philipp Zabel (cc:d here). That
>> would be appropriate.
>
We asked about ack, split series options from reset folks but didn't hear back.
Since the series has been on the list for almost 3 merge windows now, I asked
Arnd how to go about it and he suggested to send it via arm-soc. Should have
clarified it in pull request.
> I don't think this driver needs my ack, see below, ...
>
>> (Philipp, should there be a MAINTAINERS entry for you so
>> that get_maintainer works as expected here?)
>
> ... but that is a good idea to keep me in the loop. I will send a patch.
>
>> I'd also prefer to see the driver and the other changes split up since we tend
>> to merge them through different branches. I think it's OK to just split in
>> those two for this merge.
>>
Agree. I have split the series and created another two tags as below. If you
are ok, please pull them accordingly. If you want me to repost the pull requests
in separate emails, I can do that as well. Do let me know.
1] Reset driver. Contains only driver and binding documentation.
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
tags/keystone-reset-driver
2]Keystone mach updates which needs to applied on top of earlier soc
pull request. i.e on top of arm-soc 'next/soc2'. I have left 1 dts
patch in the same instead of creating another pull request for dts
change.
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
tags/keystone-soc-2
Regards,
Snatosh
next prev parent reply other threads:[~2014-05-27 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 21:29 [GIT PULL] ARM: Keystone reset driver 3.16 Santosh Shilimkar
2014-05-26 21:26 ` Olof Johansson
2014-05-27 7:26 ` Philipp Zabel
2014-05-27 14:07 ` Santosh Shilimkar [this message]
2014-05-27 14:16 ` Arnd Bergmann
2014-05-27 16:35 ` Olof Johansson
2014-05-27 18:12 ` Olof Johansson
2014-05-27 18:14 ` Santosh Shilimkar
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=53849C05.8090004@ti.com \
--to=santosh.shilimkar@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