From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel for v3.3
Date: Mon, 9 Jan 2012 09:58:39 +0000 [thread overview]
Message-ID: <20120109095839.GH21765@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120108204953.GA20043@sirena.org.uk>
On Sun, Jan 08, 2012 at 08:49:53PM +0000, Mark Brown wrote:
> On Fri, Jan 06, 2012 at 01:58:29PM -0800, Olof Johansson wrote:
>
> > > Please pull Samsung devel for v3.3 from:
> > > ?git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > > next-samsung-devel-samsung
>
> > Thanks. I've pulled this into late/devel, based on earlier email from
> > Arnd we might end up sending this in towards the end of the merge
> > window, but there's also a chance it will wait for 3.4.
>
> That'd be extremely disappointing, especially given that there's some
> bug fixes in there for updates going in this merge window without which
> mainline is going to have problems on s3c64xx (mostly the GPIO stuff).
Here we go again with sucky work practices.
This sucky behaviour has been around for a long time, I've long since
given up complaining about it as it's exactly like talking to a bloody
brick wall. People just continue mixing development and fixes together.
They then wonder why their fixes don't make it into mainline in a timely
fashion.
Maybe delaying the whole lot will make people change their behaviour:
it's a behaviour that needs to change at the submitters end. There's
nothing which Olof or Arnd can reasonably do to expedite the fixes.
So, please direct your complaints to the submitter for not having a
work practice which ensures that fixes receive a higher submission
priority.
Note: Linus _has_ taken a copy of linux-next (read the 3.2 release email),
and _is_ checking whether development stuff was in linux-next prior to
the merge window opening. It would be very unwise to send new development
which wasn't already there.
next prev parent reply other threads:[~2012-01-09 9:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 23:33 [GIT PULL] Samsung devel for v3.3 Kukjin Kim
2012-01-06 21:58 ` Olof Johansson
2012-01-07 10:09 ` Kukjin Kim
2012-01-08 20:49 ` Mark Brown
2012-01-09 1:21 ` Olof Johansson
2012-01-09 1:40 ` Kukjin Kim
2012-01-09 2:03 ` Olof Johansson
2012-01-09 15:56 ` Arnd Bergmann
2012-01-09 16:11 ` Mark Brown
2012-01-10 9:06 ` Russell King - ARM Linux
2012-01-10 18:31 ` Mark Brown
2012-01-10 18:44 ` Nicolas Pitre
2012-01-10 18:46 ` Mark Brown
2012-01-10 19:00 ` Nicolas Pitre
2012-01-10 20:13 ` Arnd Bergmann
2012-01-10 22:37 ` Mark Brown
2012-01-11 0:11 ` Olof Johansson
2012-01-11 6:39 ` Kukjin Kim
2012-01-11 16:19 ` Arnd Bergmann
2012-01-11 16:50 ` Olof Johansson
2012-01-11 17:29 ` Mark Brown
2012-01-11 6:20 ` Kukjin Kim
2012-01-09 8:26 ` Mark Brown
2012-01-17 6:40 ` Olof Johansson
2012-01-17 7:23 ` Kukjin Kim
2012-01-17 7:24 ` Olof Johansson
2012-01-17 10:53 ` Mark Brown
2012-01-09 9:58 ` Russell King - ARM Linux [this message]
2012-01-09 23:24 ` Mark Brown
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=20120109095839.GH21765@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).