Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung S5P for 2.6.38 merge window
Date: Mon, 17 Jan 2011 09:54:03 +0900	[thread overview]
Message-ID: <038201cbb5e1$0bd664a0$23832de0$%kim@samsung.com> (raw)
In-Reply-To: <20110115132955.GA15996@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> 
> On Thu, Jan 13, 2011 at 02:30:01PM +0900, Kukjin Kim wrote:
> > Hi Russell,
> >
> > Please pull Samsung S5P updates from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > for-rmk
> >
> > These things are for 2.6.38.
> 
Hi,

> This looks very large.  I really considered not merging this due to:
> 
> 1. possibly conflicts with Lennert's irq_data conversion patches.
> 
Yeah, you're right, but its changes have been merged in my for-next and
already merged in linux-next also long ago.

> 2. It's not right to push large quantities of code into mainline towards
>    the end of the merge window.  You should have everything prepared
>    that you want to send before the merge window opens.
> 
I'm afraid that it's late and large stuff 'pull request'. But I asked about
that...maybe you missed it. Anyway it's my mistake...sorry for it.

> In future, please have your tree ready for merging *before* the merge
> window opens and aim to get the bulk in preferably before, at the latest
> during the first week.

Ok...I will always remember it.

Thanks a lot.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

      parent reply	other threads:[~2011-01-17  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13  5:30 [GIT PULL] Samsung S5P for 2.6.38 merge window Kukjin Kim
2011-01-15 13:29 ` Russell King - ARM Linux
2011-01-15 13:44   ` Russell King - ARM Linux
2011-01-17  0:54   ` Kukjin Kim [this message]

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='038201cbb5e1$0bd664a0$23832de0$%kim@samsung.com' \
    --to=kgene.kim@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox