All of lore.kernel.org
 help / color / mirror / Atom feed
From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ep93xx cleanups for 3.5
Date: Fri, 11 May 2012 16:20:41 +1000	[thread overview]
Message-ID: <4FACAFB9.7000506@gmail.com> (raw)
In-Reply-To: <CAOesGMiPiYF8d2x5hHBChvTkaGJPGVKZR=wyumhbk1BV=t4eiA@mail.gmail.com>

On 11/05/12 16:18, Olof Johansson wrote:

> Hi,
> 
> On Thu, May 10, 2012 at 5:55 PM, Ryan Mallon <rmallon@gmail.com> wrote:
>> The following changes since commit 0034102808e0dbbf3a2394b82b1bb40b5778de9e:
>>
>>  Linux 3.4-rc2 (2012-04-07 18:30:41 -0700)
>>
>> are available in the git repository at:
>>
>>  git://github.com/RyanMallon/linux-ep93xx.git tags/ep93xx-cleanup-for-3.5
>>
>> for you to fetch changes up to a1eacd79a602707f97201edbac9a03edaaea1847:
>>
>>  arm: ep93xx: use gpio_led_register_device (2012-04-12 09:38:15 +1000)
>>
>> ----------------------------------------------------------------
>> H Hartley Sweeten (2):
>>      arm: ep93xx: use DEFINE_RES_* macros
>>      arm: ep93xx: use gpio_led_register_device
>>
>> Ryan Mallon (1):
>>      Fix build breakage in ep93xx-core
> 
> Pulled, thanks.
> 
> One^WTwo nits: please use the format 'ARM: ep93xx: <...>' on these
> kind of commits in the future. Also, since you have the commit that
> introduces the error right before, you can squash it in with the
> bugfix (and document it in the signed-off-by sequence if you prefer --
> see SubmittingPatches for examples).


Thanks,

The reason I didn't squash the patches together was that I had already
pushed the original broken commit out. I'm still a bit unclear on how to
fix things on a public stable branch once it has been pushed.

I'll make sure that all patches have the correct subject headers in future.

~Ryan

  reply	other threads:[~2012-05-11  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11  0:55 [GIT PULL] ep93xx cleanups for 3.5 Ryan Mallon
2012-05-11  6:18 ` Olof Johansson
2012-05-11  6:20   ` Ryan Mallon [this message]
2012-05-11  6:23     ` Olof Johansson

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=4FACAFB9.7000506@gmail.com \
    --to=rmallon@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.