From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: LPC32xx: Core updates
Date: Fri, 20 Jul 2012 22:19:40 +0000 [thread overview]
Message-ID: <201207202219.40319.arnd@arndb.de> (raw)
In-Reply-To: <50094A0E.4070006@antcom.de>
On Friday 20 July 2012, Roland Stigge wrote:
> Hi Arnd and Olof,
>
> this LPC32xx core update (branch lpc32xx/core2) builds upon the
> previously provided lpc32xx/core-fixes. Basically including PWM support
> (for the PWM driver from Alexandre already in the pwm tree), and
> CPU ID.
Pulled both branches into the sames ones as earlier respective ones.
Note that you don't actually have to start a new branch when you
add patches for the same topic, you can just add stuff on top,
whichever works best for you.
It would be nice if you can start sending tags rather than branches,
because that lets you put the changeset text right into the tag
so I don't have to copy it into the merge text manually.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Roland Stigge <stigge@antcom.de>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alexandre Pereira da Silva <aletes.xgr@gmail.com>
Subject: Re: [GIT PULL] ARM: LPC32xx: Core updates
Date: Fri, 20 Jul 2012 22:19:40 +0000 [thread overview]
Message-ID: <201207202219.40319.arnd@arndb.de> (raw)
In-Reply-To: <50094A0E.4070006@antcom.de>
On Friday 20 July 2012, Roland Stigge wrote:
> Hi Arnd and Olof,
>
> this LPC32xx core update (branch lpc32xx/core2) builds upon the
> previously provided lpc32xx/core-fixes. Basically including PWM support
> (for the PWM driver from Alexandre already in the pwm tree), and
> CPU ID.
Pulled both branches into the sames ones as earlier respective ones.
Note that you don't actually have to start a new branch when you
add patches for the same topic, you can just add stuff on top,
whichever works best for you.
It would be nice if you can start sending tags rather than branches,
because that lets you put the changeset text right into the tag
so I don't have to copy it into the merge text manually.
Arnd
next prev parent reply other threads:[~2012-07-20 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 12:07 [GIT PULL] ARM: LPC32xx: Core updates Roland Stigge
2012-07-20 12:07 ` Roland Stigge
2012-07-20 22:19 ` Arnd Bergmann [this message]
2012-07-20 22:19 ` Arnd Bergmann
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=201207202219.40319.arnd@arndb.de \
--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 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.