public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 6/6] s3c24xx driver
Date: Wed, 12 Jun 2013 16:51:58 -0700	[thread overview]
Message-ID: <20130612235158.GC9067@quad.lixom.net> (raw)
In-Reply-To: <51B791F6.4000004@samsung.com>

On Wed, Jun 12, 2013 at 06:09:10AM +0900, Kukjin Kim wrote:
> The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
> 
>   Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
> 
> are available in the git repository at:
> 

> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/s3c24xx-driver-1
> 
> for you to fetch changes up to ae7b6dccf6711e8d5815688f1572ab55bf5b3069:
> 
>   Merge branch 'v3.11-next/driver-cpufreq' into
> v3.11-next/s3c24xx-driver (2013-06-12 05:24:22 +0900)
> 
> ----------------------------------------------------------------
> 
> update driver for s3c24xx
> - move cpufreq driver into drivers/
> - add pinctrl-s3c24xx driver
> - cleanup OF in gpio driver
> 
> ----------------------------------------------------------------
> Heiko Stuebner (1):
>       pinctrl: Add pinctrl-s3c24xx driver
> 
> Kukjin Kim (3):
>       Merge branch 'v3.11-next/driver-gpio' into v3.11-next/s3c24xx-driver
>       Merge branch 'v3.11-next/driver-pinctrl' into
> v3.11-next/s3c24xx-driver
>       Merge branch 'v3.11-next/driver-cpufreq' into
> v3.11-next/s3c24xx-driver

Hi,

No need to do a merge commit per patch, just do them on a single branch in the
future, please.

Pulled.


-Olof

  reply	other threads:[~2013-06-12 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 21:09 [GIT PULL 6/6] s3c24xx driver Kukjin Kim
2013-06-12 23:51 ` Olof Johansson [this message]
2013-06-13  0:26   ` Kukjin Kim

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=20130612235158.GC9067@quad.lixom.net \
    --to=olof@lixom.net \
    --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