From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: n900: Include adp1653 device
Date: Thu, 21 Jan 2016 16:54:08 +0000 [thread overview]
Message-ID: <20160121165408.GJ5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160121163857.GH19432@atomide.com>
On Thu, Jan 21, 2016 at 08:38:57AM -0800, Tony Lindgren wrote:
> * Pavel Machek <pavel@ucw.cz> [160121 02:19]:
> > On Thu 2016-01-21 09:29:10, Russell King - ARM Linux wrote:
> > > The merge window is open, which is when development code that was merged
> > > in good time prior to the merge window is sent upstream to Linus. Linux
> > > maintainers may choose not to merge new code into their tree to avoid
> > > disrupting the utility of linux-next until the merge window has
> > > closed.
> >
> > Support for new hardware is normally allowed after -rc1.
>
> Yeah most maintainers avoid looking at new code until -rc1. Or until
> regresssions are out of the way. So patience please. Fixes are
> welcome any time though.
Indeed. However, unlike Pavel's comment, many maintainers choose not
to merge code for new hardware until the merge window - it's very rare
that support for new hardware is merged during the -rc phase.
If it were otherwise, I would've been able to get the Hummingboard 2
DTS patches in, or the etnaviv team would've been able to get the
Etnaviv GPU DRM driver in during the 4.4-rc cycle, or the Dove PMU
driver, or... etc.
Practically, new code waits for merge windows, because no one wants
to de-stabilise the progression of the -rc series with new code, and
Linus wants to see -rc merges fairly quiet and be mostly bug fixes
so he can feel good about a final release around -rc6 to -rc7 time.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: n900: Include adp1653 device
Date: Thu, 21 Jan 2016 16:54:08 +0000 [thread overview]
Message-ID: <20160121165408.GJ5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160121163857.GH19432@atomide.com>
On Thu, Jan 21, 2016 at 08:38:57AM -0800, Tony Lindgren wrote:
> * Pavel Machek <pavel@ucw.cz> [160121 02:19]:
> > On Thu 2016-01-21 09:29:10, Russell King - ARM Linux wrote:
> > > The merge window is open, which is when development code that was merged
> > > in good time prior to the merge window is sent upstream to Linus. Linux
> > > maintainers may choose not to merge new code into their tree to avoid
> > > disrupting the utility of linux-next until the merge window has
> > > closed.
> >
> > Support for new hardware is normally allowed after -rc1.
>
> Yeah most maintainers avoid looking at new code until -rc1. Or until
> regresssions are out of the way. So patience please. Fixes are
> welcome any time though.
Indeed. However, unlike Pavel's comment, many maintainers choose not
to merge code for new hardware until the merge window - it's very rare
that support for new hardware is merged during the -rc phase.
If it were otherwise, I would've been able to get the Hummingboard 2
DTS patches in, or the etnaviv team would've been able to get the
Etnaviv GPU DRM driver in during the 4.4-rc cycle, or the Dove PMU
driver, or... etc.
Practically, new code waits for merge windows, because no one wants
to de-stabilise the progression of the -rc series with new code, and
Linus wants to see -rc merges fairly quiet and be mostly bug fixes
so he can feel good about a final release around -rc6 to -rc7 time.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-01-21 16:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 23:40 [PATCH] ARM: dts: n900: Include adp1653 device Pali Rohár
2015-12-25 23:40 ` Pali Rohár
2015-12-25 23:40 ` Pali Rohár
2015-12-26 18:35 ` Pavel Machek
2015-12-26 18:35 ` Pavel Machek
2016-01-09 22:38 ` Pali Rohár
2016-01-09 22:38 ` Pali Rohár
2016-01-09 22:38 ` Pali Rohár
2016-01-21 9:12 ` Pali Rohár
2016-01-21 9:12 ` Pali Rohár
2016-01-21 9:12 ` Pali Rohár
2016-01-21 9:29 ` Russell King - ARM Linux
2016-01-21 9:29 ` Russell King - ARM Linux
2016-01-21 9:29 ` Russell King - ARM Linux
2016-01-21 9:50 ` Pali Rohár
2016-01-21 9:50 ` Pali Rohár
2016-01-21 10:03 ` Russell King - ARM Linux
2016-01-21 10:03 ` Russell King - ARM Linux
2016-01-21 10:18 ` Pavel Machek
2016-01-21 10:18 ` Pavel Machek
2016-01-21 10:18 ` Pavel Machek
2016-01-21 16:38 ` Tony Lindgren
2016-01-21 16:38 ` Tony Lindgren
2016-01-21 16:38 ` Tony Lindgren
2016-01-21 16:54 ` Russell King - ARM Linux [this message]
2016-01-21 16:54 ` Russell King - ARM Linux
2016-01-27 10:02 ` Pali Rohár
2016-01-27 10:02 ` Pali Rohár
2016-01-27 11:18 ` Russell King - ARM Linux
2016-01-27 11:18 ` Russell King - ARM Linux
2016-01-27 16:24 ` Tony Lindgren
2016-01-27 16:24 ` Tony Lindgren
2016-01-27 16:24 ` Tony Lindgren
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=20160121165408.GJ5783@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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 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.