linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: n900: Include adp1653 device
Date: Thu, 21 Jan 2016 08:38:57 -0800	[thread overview]
Message-ID: <20160121163857.GH19432@atomide.com> (raw)
In-Reply-To: <20160121101828.GA7411@amd>

* 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.

Regards,

Tony

  reply	other threads:[~2016-01-21 16:38 UTC|newest]

Thread overview: 13+ 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-26 18:35 ` Pavel Machek
2016-01-09 22:38 ` Pali Rohár
2016-01-21  9:12 ` Pali Rohár
2016-01-21  9:29   ` Russell King - ARM Linux
2016-01-21  9:50     ` Pali Rohár
2016-01-21 10:03       ` Russell King - ARM Linux
2016-01-21 10:18     ` Pavel Machek
2016-01-21 16:38       ` Tony Lindgren [this message]
2016-01-21 16:54         ` Russell King - ARM Linux
2016-01-27 10:02           ` Pali Rohár
2016-01-27 11:18             ` Russell King - ARM Linux
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=20160121163857.GH19432@atomide.com \
    --to=tony@atomide.com \
    --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).