public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Pull Request] Various ARM platform code fixes
Date: Mon, 02 Jun 2014 21:02:57 +0200	[thread overview]
Message-ID: <4750577.NRz8KZsHUG@wuerfel> (raw)
In-Reply-To: <CAOesGMhsxKCVXJPX-JF96nvwstDp3crZKZzb3GVKX=dzZMMD0A@mail.gmail.com>

On Monday 02 June 2014 09:42:48 Olof Johansson wrote:
> On Mon, Jun 2, 2014 at 2:23 AM, Sachin Kamat <sachin.kamat@linaro.org> wrote:
> > Hi Arnd,
> >
> > As suggested by you I am sending a pull request for the below 8 patches.
> > These are based on for-next branch of arm-soc tree [1].
> >
> > [1] git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> 
> Please, don't send random pull requests to us. Some of these patches
> are for platforms that have quite active maintainers and you're
> messing up everyone's workflow by randomly sending them to us.
> 
> I have no idea what you talked to Arnd about, and you give no
> reference to it in your pull request.

FYI, these are all trivial cleanups that no subarch maintainer has
picked up since they were posted, and I offered to take them
from a pull request
 
> Besides, the merge window is open, we're not taking anything new until
> after -rc1.

Agreed, I didn't expect the merge window to open already, and since there
is no urgency here, let's apply this into next/cleanups after the merge
window.

	Arnd

  reply	other threads:[~2014-06-02 19:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  9:23 [Pull Request] Various ARM platform code fixes Sachin Kamat
2014-06-02 16:42 ` Olof Johansson
2014-06-02 19:02   ` Arnd Bergmann [this message]
2014-06-24  9:44     ` Sachin Kamat
2014-06-24 11:12       ` Arnd Bergmann
2014-06-24 11:49         ` Sachin Kamat

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=4750577.NRz8KZsHUG@wuerfel \
    --to=arnd@arndb.de \
    --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