All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>
Subject: Re: [GIT PULL 0/10] Samsung stuff for v3.10
Date: Tue, 9 Apr 2013 23:20:06 +0200	[thread overview]
Message-ID: <201304092320.06222.arnd@arndb.de> (raw)
In-Reply-To: <516309C4.3000008@samsung.com>

On Monday 08 April 2013, Kukjin Kim wrote:
> 
> Hi Arnd, Olof
> 
> This is 2nd pull-request for Samsung stuff for v3.10.
> 
> If any problems, please kindly let me know.

I managed to pull them all in, aside from the 6/10, since you asked us
to defer that one. There were a lot more small mistakes, and I think
I've managed to fix them all up, but please check if the for-next
branch now actually works.

A few more requests for the future:

* Please send branches earlier. You already sent a number of them
very early, but then we saw very little until now. I'd rather
get a number of follow-on pull requests than getting everything
at once, which has lead to stuff getting rejected in the past
when things break, as you remember. I've been waiting for
ages now to rebase my multiplatform series on the things you
have in your tree, I hope we can still make it in time.

* Half a sentence of tag description is not really enough for
a long series. Please explain in the tag what the purpose of
the series is, as you do for a patch.

* Mention interdependencies between branches explicitly. It
causes us a lot of extra work having to find out what patches
are actually new in a series when you have based them on earlier
patches.

* Look at the patches that are already merged and test them.
I've had to fix up build errors now that have been present
in linux-next for multiple weeks.

	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 0/10] Samsung stuff for v3.10
Date: Tue, 9 Apr 2013 23:20:06 +0200	[thread overview]
Message-ID: <201304092320.06222.arnd@arndb.de> (raw)
In-Reply-To: <516309C4.3000008@samsung.com>

On Monday 08 April 2013, Kukjin Kim wrote:
> 
> Hi Arnd, Olof
> 
> This is 2nd pull-request for Samsung stuff for v3.10.
> 
> If any problems, please kindly let me know.

I managed to pull them all in, aside from the 6/10, since you asked us
to defer that one. There were a lot more small mistakes, and I think
I've managed to fix them all up, but please check if the for-next
branch now actually works.

A few more requests for the future:

* Please send branches earlier. You already sent a number of them
very early, but then we saw very little until now. I'd rather
get a number of follow-on pull requests than getting everything
at once, which has lead to stuff getting rejected in the past
when things break, as you remember. I've been waiting for
ages now to rebase my multiplatform series on the things you
have in your tree, I hope we can still make it in time.

* Half a sentence of tag description is not really enough for
a long series. Please explain in the tag what the purpose of
the series is, as you do for a patch.

* Mention interdependencies between branches explicitly. It
causes us a lot of extra work having to find out what patches
are actually new in a series when you have based them on earlier
patches.

* Look at the patches that are already merged and test them.
I've had to fix up build errors now that have been present
in linux-next for multiple weeks.

	Arnd

  reply	other threads:[~2013-04-09 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 18:17 [GIT PULL 0/10] Samsung stuff for v3.10 Kukjin Kim
2013-04-08 18:17 ` Kukjin Kim
2013-04-09 21:20 ` Arnd Bergmann [this message]
2013-04-09 21:20   ` Arnd Bergmann
2013-04-10  8:59   ` Kukjin Kim
2013-04-10  8:59     ` 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=201304092320.06222.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    /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.