From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Nishanth Menon <nm@ti.com>, Kevin Hilman <khilman@linaro.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-omap <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-next <linux-next@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
Date: Thu, 11 Dec 2014 09:29:45 +0000 [thread overview]
Message-ID: <20141211092945.GE11502@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <54881589.20105@samsung.com>
On Wed, Dec 10, 2014 at 10:42:33AM +0100, Marek Szyprowski wrote:
> I assume that now it won't be possible to get l2c patches back to -next,
> so I will resend them (again...) with the omap related fix.
What, you mean you don't know the fundamental rules of kernel development?
No one should ever dump any new code into linux-next during a merge
window which is not a fix for a regression or a bug fix, period.
Linus has in the past taken a snapshot of linux-next at the beginning
of a merge window, and then threatened to refuse to merge anything that
wasn't in his local snapshot, or which doesn't qualify as the above.
So no, it won't be possible, because I play by the community rules when
it comes to what gets merged and at what time in the cycle.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-12-11 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 16:10 regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like) Nishanth Menon
2014-12-05 16:13 ` Nishanth Menon
2014-12-05 16:23 ` Russell King - ARM Linux
2014-12-08 11:54 ` Tomasz Figa
2014-12-08 12:22 ` Russell King - ARM Linux
2014-12-08 13:54 ` Nishanth Menon
2014-12-08 15:11 ` Russell King - ARM Linux
2014-12-09 16:57 ` Nishanth Menon
2014-12-10 9:42 ` Marek Szyprowski
2014-12-11 9:29 ` Russell King - ARM Linux [this message]
2014-12-11 10:42 ` Marek Szyprowski
2014-12-22 17:04 ` Russell King - ARM Linux
2014-12-22 17:08 ` Tony Lindgren
2014-12-22 17:12 ` Nishanth Menon
2014-12-22 17:28 ` Russell King - ARM Linux
2014-12-23 11:00 ` Marek Szyprowski
2014-12-23 11:10 ` Russell King - ARM Linux
2014-12-23 16:05 ` Nishanth Menon
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=20141211092945.GE11502@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nm@ti.com \
--cc=tomasz.figa@gmail.com \
--cc=tony@atomide.com \
/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).