From: Bjorn Helgaas <helgaas@kernel.org>
To: Jianjun Wang <jianjun.wang@mediatek.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ryder Lee <ryder.lee@mediatek.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
davem@davemloft.net, linux-pci@vger.kernel.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sj Huang <sj.huang@mediatek.com>
Subject: Re: [v1,1/3] dt-bindings: Add YAML schemas for Gen3 PCIe controller
Date: Tue, 8 Sep 2020 15:04:07 -0500 [thread overview]
Message-ID: <20200908200407.GA628520@bjorn-Precision-5520> (raw)
In-Reply-To: <20200907120852.12090-2-jianjun.wang@mediatek.com>
On Mon, Sep 07, 2020 at 08:08:50PM +0800, Jianjun Wang wrote:
> Add YAML schemas documentation for Gen3 PCIe controller on
> MediaTek SoCs.
Please mention "mediatek" in the subject line so "git log --oneline"
is more useful.
The convention (not universally observed) seems to be something like:
dt-bindings: PCI: <driver-name>: Add YAML schema
next prev parent reply other threads:[~2020-09-08 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 12:08 [v1,0/3] PCI: mediatek: Add new generation controller support Jianjun Wang
2020-09-07 12:08 ` [v1,1/3] dt-bindings: Add YAML schemas for Gen3 PCIe controller Jianjun Wang
2020-09-08 19:50 ` Rob Herring
2020-09-09 3:08 ` Jianjun Wang
2020-09-09 17:50 ` Rob Herring
2020-09-08 20:04 ` Bjorn Helgaas [this message]
2020-09-09 3:14 ` Jianjun Wang
2020-09-08 20:21 ` Rob Herring
2020-09-09 3:39 ` Jianjun Wang
2020-09-07 12:08 ` [v1,2/3] PCI: mediatek: Add new generation controller support Jianjun Wang
2020-09-07 12:08 ` [v1,3/3] MAINTAINERS: update entry for MediaTek PCIe controller Jianjun Wang
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=20200908200407.GA628520@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jianjun.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sj.huang@mediatek.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).