linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL REQ] Big Endian initial patch series
Date: Sat, 19 Oct 2013 20:51:35 +0100	[thread overview]
Message-ID: <5262E2C7.7000106@codethink.co.uk> (raw)
In-Reply-To: <20131019170954.GC25076@mudshark.cambridge.arm.com>

On 19/10/13 18:09, Will Deacon wrote:
> Hi Ben,
>
> A few nits here...
>
> Firstly, I'd suggest using [GIT PULL] instead of [PULL REQ] in the subject.
> Many people filter on the first, so you might get missed with the latter.
>
> On Fri, Oct 18, 2013 at 09:54:05PM +0100, Ben Dooks wrote:
>> This series has been well tested and it would be great to get this
>> merged now. So here is the pull request:
>>
>> The following changes since commit 8b5ede69d24db939f52b47effff2f6fe1e83e08b:
>>
>>    powerpc/irq: Don't switch to irq stack from softirq stack (2013-10-07 14:19:39 -0700)
>
> Secondly, I'd suggest basing against a specific tag in mainline if possible,
> rather than a random commit. I think -rc3 matches rmk's current
> devel-stable branch.
>
>> are available in the git repository at:
>>
>>    ssh://git at git.baserock.org/delta/linux baserock/bjdooks/312-rc4/be/core-v2
>
> This is an ssh URL, so it can't be pulled without some form of
> authentication! Use git:// instead for pull requests.
>
> It's also good form to put your pull requests on separate branches from what
> you have been using for development, to make it clear that it is stable.
> Another method is to use a signed tag (although this seems more common with
> arm-soc than others).
>
> Do you think you could send another pull request please?

Ok, sorted.


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  reply	other threads:[~2013-10-19 19:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 20:54 [PULL REQ] Big Endian initial patch series Ben Dooks
2013-10-19 17:09 ` Will Deacon
2013-10-19 19:51   ` Ben Dooks [this message]
2013-10-28  0:47     ` Russell King - ARM Linux
2013-10-28  8:44       ` Will Deacon
2013-10-28  8:53         ` Russell King - ARM Linux
2013-10-28  9:12           ` Sricharan R
2013-10-29  5:09             ` Victor Kamensky
2013-10-29  5:24               ` Sricharan R
2013-10-28 15:59           ` Ben Dooks
2013-10-30  4:05             ` Victor Kamensky
2013-10-30 17:43               ` Russell King - ARM Linux
2013-10-30 18:01             ` Russell King - ARM Linux
2013-10-30 18:23               ` Victor Kamensky

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=5262E2C7.7000106@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --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).