All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org,
	'Russell King' <rmk+kernel@arm.linux.org.uk>,
	'Ben Dooks' <ben-linux@fluff.org>
Subject: Re: [GIT PULL] Samsung cleanup-2 for v3.2
Date: Fri, 7 Oct 2011 20:05:49 +0200	[thread overview]
Message-ID: <201110072005.49967.arnd@arndb.de> (raw)
In-Reply-To: <019a01cc8298$823f7b20$86be7160$%kim@samsung.com>

On Tuesday 04 October 2011, Kukjin Kim wrote:
> This is second cleanup for Samsung stuff for v3.2 and includes cleanup
> header files in plat-s3c24xx and plat-s5p to merge into one plat-samsung
> directory.
> 
> Please pull from:
>   git://github.com/kgene/linux-samsung.git next-samsung-cleanup-2
> 
> And this is based on previous Samsung cleanup branch, next-samsung-cleanup
> which has been merged in arm-soc because of dependency.
> 
> If any problems, please let me know.
> 

Looks good to me. I think this should go into 3.2 very late during the merge
window since it moves around a lot of files that might be touched by other
patches, and I don't want to break a lot of that stuff, so I'm putting
it into a separate next/cleanup2 branch, ok?

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung cleanup-2 for v3.2
Date: Fri, 7 Oct 2011 20:05:49 +0200	[thread overview]
Message-ID: <201110072005.49967.arnd@arndb.de> (raw)
In-Reply-To: <019a01cc8298$823f7b20$86be7160$%kim@samsung.com>

On Tuesday 04 October 2011, Kukjin Kim wrote:
> This is second cleanup for Samsung stuff for v3.2 and includes cleanup
> header files in plat-s3c24xx and plat-s5p to merge into one plat-samsung
> directory.
> 
> Please pull from:
>   git://github.com/kgene/linux-samsung.git next-samsung-cleanup-2
> 
> And this is based on previous Samsung cleanup branch, next-samsung-cleanup
> which has been merged in arm-soc because of dependency.
> 
> If any problems, please let me know.
> 

Looks good to me. I think this should go into 3.2 very late during the merge
window since it moves around a lot of files that might be touched by other
patches, and I don't want to break a lot of that stuff, so I'm putting
it into a separate next/cleanup2 branch, ok?

	Arnd

  reply	other threads:[~2011-10-07 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 13:21 [GIT PULL] Samsung cleanup-2 for v3.2 Kukjin Kim
2011-10-04 13:21 ` Kukjin Kim
2011-10-07 18:05 ` Arnd Bergmann [this message]
2011-10-07 18:05   ` Arnd Bergmann
2011-10-10  4:27   ` Kukjin Kim
2011-10-10  4:27     ` 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=201110072005.49967.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=ben-linux@fluff.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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.