From: Tejun Heo <tj@kernel.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Kishon Vijay Abraham I <kishon@ti.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>,
Gregory Fong <gregory.0xf0@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
bcm-kernel-feedback-list@broadcom.com,
Kevin Cernekee <cernekee@gmail.com>
Subject: Re: [PATCH v3 0/5] AHCI and SATA PHY support for Broadcom STB SoCs
Date: Thu, 21 May 2015 18:23:50 -0400 [thread overview]
Message-ID: <20150521222350.GN4914@htj.duckdns.org> (raw)
In-Reply-To: <20150521221306.GF11598@ld-irv-0074>
Hello,
On Thu, May 21, 2015 at 03:13:06PM -0700, Brian Norris wrote:
> Most subsystems take device tree binding patches for their constituent
> drivers. And I see you've been merging others:
>
> e35b98849f25 ata: sata_rcar: Add r8a7793 device support
> 8340bfeb03 ahci: st: Update the ahci_st DT documentation
> af64dce4cb3a ahci: st: Provide DT bindings for ST's SATA implementation
> a1a205df6ee2 ahci: add support for Hisilicon sata
>
> All have your sign-off / commit stamp.
Yeap, I've been routing some of them.
> > Is this
> > an exception?
>
> Not that I know of. Where would you like it to go instead?
But the rules have never been clear to me. If the subsystem
maintainer is okay with it, I'm happy to take the patches. I'm just
kinda curious why this doesn't go through devicetree tree while some
other devicetree patches go through there. Can somebody explain the
overall policy to me? I'm not looking for some absolute rules and
exceptions are fine but I do wanna have a general direction.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-05-21 22:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 23:28 [PATCH v3 0/5] AHCI and SATA PHY support for Broadcom STB SoCs Brian Norris
2015-05-12 23:28 ` [PATCH v3 1/5] Documentation: devicetree: add Broadcom SATA binding Brian Norris
2015-05-25 0:11 ` Tejun Heo
2015-05-12 23:28 ` [PATCH v3 2/5] Documentation: devicetree: add Broadcom SATA PHY binding Brian Norris
2015-05-12 23:28 ` [PATCH v3 3/5] ata: add Broadcom AHCI SATA3 driver for STB chips Brian Norris
2015-05-21 22:03 ` Tejun Heo
[not found] ` <1431473303-18873-4-git-send-email-computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-21 22:16 ` Fabio Estevam
2015-05-21 22:20 ` Tejun Heo
2015-05-21 22:26 ` Brian Norris
2015-05-21 22:28 ` Tejun Heo
2015-05-12 23:28 ` [PATCH v3 4/5] phy: add Broadcom SATA3 PHY driver for Broadcom STB SoCs Brian Norris
2015-05-13 11:07 ` Kishon Vijay Abraham I
2015-05-13 18:49 ` Brian Norris
2015-05-14 5:52 ` Kishon Vijay Abraham I
2015-05-14 17:39 ` Brian Norris
2015-05-14 17:42 ` Florian Fainelli
2015-05-21 13:23 ` Kishon Vijay Abraham I
2015-05-21 0:18 ` [PATCH v4] " Brian Norris
2015-05-12 23:28 ` [PATCH v3 5/5] ARM: dts: brcmstb: add nodes for SATA controller and PHY Brian Norris
2015-05-13 18:02 ` Florian Fainelli
2015-05-21 13:22 ` [PATCH v3 0/5] AHCI and SATA PHY support for Broadcom STB SoCs Kishon Vijay Abraham I
2015-05-21 22:00 ` Tejun Heo
2015-05-21 22:01 ` Tejun Heo
2015-05-21 22:03 ` Brian Norris
2015-05-21 22:04 ` Tejun Heo
2015-05-21 22:13 ` Brian Norris
2015-05-21 22:23 ` Tejun Heo [this message]
2015-05-21 22:38 ` Brian Norris
2015-05-25 0:08 ` Tejun Heo
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=20150521222350.GN4914@htj.duckdns.org \
--to=tj@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=gregory.0xf0@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).