[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160121163857.GH19432@atomide.com>
Date: Thu, 21 Jan 2016 08:38:57 -0800
From: Tony Lindgren <tony@...mide.com>
To: Pavel Machek <pavel@....cz>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Pali Rohár <pali.rohar@...il.com>,
Benoît Cousson <bcousson@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>, linux-omap@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: n900: Include adp1653 device
* Pavel Machek <pavel@....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.
Regards,
Tony
Powered by blists - more mailing lists