linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: samsung merge window over
Date: Tue, 25 May 2010 08:34:54 +0100	[thread overview]
Message-ID: <20100525073454.GF7248@trinity.fluff.org> (raw)
In-Reply-To: <20100525073124.GA11051@n2100.arm.linux.org.uk>

On Tue, May 25, 2010 at 08:31:24AM +0100, Russell King - ARM Linux wrote:
> On Tue, May 25, 2010 at 02:52:29PM +0900, Kukjin Kim wrote:
> > Ben Dooks wrote:
> > > 
> > > Thankyou to all who contributed to this round of updates, I am officially
> > > calling the end of any new development work for this merge window.
> > > 
> > > Special thanks to all at Samsung for their help.
> > > 
> > > I will now be preparing a defconfig, documentation and any other bugfixes
> > > tree to send to Linus as soon as possible.
> > > 
> > > As a note, this is the shortlog of the patches merged via my tree:
> > 
> > Thanks for your review and merging.
> > 
> > And ok, we will continue our development and submit patches for the next
> > merge window. Also, if we find any issues, we will submit patches for those
> > also.
> 
> The impression I have is that Samsung folk waited for the merge window
> before sending their patches to the mailing list - there have been
> about 320 messages attributable to 'samsung' or 's3' subjects since the
> merge window opened.
> 
> This is excessive, and isn't really practical - it swamps the mailing
> list and makes it very easy to miss more relevant stuff during the
> merge window.

Yes, agreed. I have made the point to them again that this is too late
in the development cycle. Unforunately due to the 'fun' with uk airspace
my visit here was dealyed by nearly three weeks, which has left us with
too little time.
 
> So, please send the majority of patches *before* the merge window and
> try to avoid sending anything but fixes during the merge window itself.
> The merge window is for code which has _already_ been merged and has
> been in linux-next to be merged into Linus' tree.  It's not for new
> code to be reviewed.

Next merge window, which will probably be the last I will handle for the
S5P range, will have an earlier cut-off point. It was a big rush to get
this lot reviewed and merged.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-05-25  7:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25  4:42 samsung merge window over Ben Dooks
2010-05-25  5:52 ` Kukjin Kim
2010-05-25  7:31   ` Russell King - ARM Linux
2010-05-25  7:34     ` Ben Dooks [this message]
2010-05-25  8:00       ` WARNING about next merge window (Re: samsung merge window over) Russell King - ARM Linux

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=20100525073454.GF7248@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --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;
as well as URLs for NNTP newsgroup(s).