linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: spear-soc DT support for 3.5
Date: Wed, 11 Apr 2012 10:43:53 +0200	[thread overview]
Message-ID: <CACRpkdYgSFYgr-CVmG0JenMM+EOydjJxpR8zaFuGPiMKtKRM9Q@mail.gmail.com> (raw)
In-Reply-To: <4F853FC0.4080802@st.com>

On Wed, Apr 11, 2012 at 10:24 AM, Viresh Kumar <viresh.kumar@st.com> wrote:

> On 4/11/2012 1:47 PM, Linus Walleij wrote:
>> Hm, then we should maybe consider mergeing all that pinctrl stuff
>> through ARM SoC later as well. I can probably provide the
>> necessary ACKs.
>
> That would be much better. Just to know who should update these Acks
> in commits. If it isn't a pull request, Arnd will do it. But if it is,
> then probably i am required to update this?

Yeah you can send this pull request and then Arnd or Olof will put it
on some topic branch like "topic-spear" and then you base your
further work on top of that and then send a new pull request to be
merged into that same branch, with the pinctrl stuff. And include the
ACK:s directly in the patches (git rebase -i is your friend...)

Yours,
Linus Walleij

  reply	other threads:[~2012-04-11  8:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02  5:42 [GIT PULL] ARM: spear-soc DT support for 3.5 Viresh Kumar
     [not found] ` <CAOh2x=n8GO-vzFgDEdeyUVdGiOE_-BxgpC5+LbKRMtvgnoSxHQ@mail.gmail.com>
2012-04-10  8:42   ` Linus Walleij
2012-04-10  9:18     ` Viresh Kumar
2012-04-11  8:17       ` Linus Walleij
2012-04-11  8:24         ` Viresh Kumar
2012-04-11  8:43           ` Linus Walleij [this message]
2012-04-11  8:47             ` Viresh Kumar
2012-04-11  8:54               ` Linus Walleij
2012-04-11  9:04                 ` Shiraz Hashim
2012-04-11  8:16 ` Linus Walleij
2012-04-11  8:23   ` Viresh Kumar
2012-04-11 17:30 ` Arnd Bergmann
2012-04-12  6:49   ` Viresh Kumar

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=CACRpkdYgSFYgr-CVmG0JenMM+EOydjJxpR8zaFuGPiMKtKRM9Q@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --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).