public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: Keystone reset driver 3.16
Date: Mon, 26 May 2014 14:26:05 -0700	[thread overview]
Message-ID: <20140526212605.GQ27093@quad.lixom.net> (raw)
In-Reply-To: <1400880597-7516-1-git-send-email-santosh.shilimkar@ti.com>

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. (Philipp, should there be a MAINTAINERS entry for you so
that get_maintainer works as expected here?)

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.

I could do it for you (i.e. merge the first patch into next/drivers and the
rest into next/soc2 with the driver patch included on the bottom), but that
still wouldn't cover the ack from Philipp. If he replies to this email and says
he's ok with it going in I can still do it that way though. Philipp?



-Olof

  reply	other threads:[~2014-05-26 21:26 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 [this message]
2014-05-27  7:26   ` Philipp Zabel
2014-05-27 14:07     ` Santosh Shilimkar
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=20140526212605.GQ27093@quad.lixom.net \
    --to=olof@lixom.net \
    --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