From: Mark Brown <broonie@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Mason Zhang <mason.zhang@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, wsd_upstream@mediatek.com,
hanks.chen@mediatek.com, linux-kernel@vger.kernel.org,
"open list:SPI SUBSYSTEM" <linux-spi@vger.kernel.org>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] dt-binding: mediatek: mt6779: update spi document
Date: Fri, 25 Jun 2021 12:25:44 +0100 [thread overview]
Message-ID: <20210625112544.GB4492@sirena.org.uk> (raw)
In-Reply-To: <732a8061-e8be-5c8a-ea75-6da87947db02@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Mon, Jun 21, 2021 at 05:31:41PM +0200, Matthias Brugger wrote:
> On 15/06/2021 13:14, Mark Brown wrote:
> > I don't have either patch 1 or a cover letter, what's the story with
> > dependencies here?
> No dependency. The dt-bindings was just send a second patch in the series. First
> one can be found here:
The point here is that if you're sending a series that's generally
because there's some dependencies so it's important to copy people on
enough of what's going on (generally at least the cover letter) so that
they know what the story is.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-25 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:50 [PATCH 2/2] dt-binding: mediatek: mt6779: update spi document Mason Zhang
2021-06-15 11:14 ` Mark Brown
2021-06-21 15:31 ` Matthias Brugger
2021-06-25 11:25 ` Mark Brown [this message]
2021-06-24 20:44 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 1:36 Mason Zhang
2021-06-11 12:13 Mason Zhang
2021-06-11 13:54 ` Matthias Brugger
2021-06-14 10:29 ` Mark Brown
2021-02-26 11:01 Mason Zhang
2021-02-26 17:07 ` Mark Brown
2021-03-01 1:47 ` Mason Zhang
2021-03-04 15:05 ` Mark Brown
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=20210625112544.GB4492@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hanks.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mason.zhang@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsd_upstream@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).