devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Tony Lindgren" <tony@atomide.com>, "Pavel Machek" <pavel@ucw.cz>,
	"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: Wed, 27 Jan 2016 11:18:28 +0000	[thread overview]
Message-ID: <20160127111828.GK5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160127100237.GH25796@pali>

On Wed, Jan 27, 2016 at 11:02:37AM +0100, Pali Rohár wrote:
> In my opinion this patch is not support for new hardware. It just add
> missing DT definition for one specific board for HW which was added to
> linux kernel in v4.2-rc1 version. For me it looks like that needed DT
> definition was forgotten...

Opinions differ, but ultimately it's up to whoever is responsible for
accepting the patch, and in the case of ARM SoC based patches, the
arm-soc maintainers.

The arm-soc maintainers close their trees for development changes a
few weeks before hand (a patch of mine which was acked etc by 7th
December never made the 4.5 merge window either, and the alleged
reason I've been told is because arm-soc was already closed by then).

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

  reply	other threads:[~2016-01-27 11:18 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
     [not found] ` <1451086812-3729-1-git-send-email-pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
     [not found]     ` <20160121092909.GH5783-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2016-01-21 10:18       ` Pavel Machek
2016-01-21 16:38         ` Tony Lindgren
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 [this message]
     [not found]                 ` <20160127111828.GK5783-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
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=20160127111828.GK5783@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 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).