From: Mason Zhang <mason.zhang@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"open list:SPI SUBSYSTEM" <linux-spi@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <hanks.chen@mediatek.com>,
<wsd_upstream@mediatek.com>
Subject: Re: [PATCH 2/2] dt-binding: mediatek: mt6779: update spi document
Date: Mon, 1 Mar 2021 09:47:58 +0800 [thread overview]
Message-ID: <1614563278.1578.6.camel@mbjsdccf07> (raw)
In-Reply-To: <20210226170705.GB4518@sirena.org.uk>
Dear Mark:
Patch 1/2 is in this link:
lkml.org/lkml/2021/2/26/325
I will email you later about patch 1/2.
Thank you for your suggestion!
Thanks
Mason
-----------------
On Fri, 2021-02-26 at 17:07 +0000, Mark Brown wrote:
> On Fri, Feb 26, 2021 at 07:01:10PM +0800, Mason Zhang wrote:
> > this patch update spi document for MT6779 SOC.
>
> I'm missing patch 1/2 here, what's the story with dependencies?
>
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
next prev parent reply other threads:[~2021-03-01 1:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 11:01 [PATCH 2/2] dt-binding: mediatek: mt6779: update spi document Mason Zhang
2021-02-26 17:07 ` Mark Brown
2021-03-01 1:47 ` Mason Zhang [this message]
2021-03-04 15:05 ` Mark Brown
2021-06-11 12:13 Mason Zhang
2021-06-11 13:54 ` Matthias Brugger
2021-06-14 10:29 ` Mark Brown
2021-06-15 1:36 Mason Zhang
2021-06-15 1:50 Mason Zhang
2021-06-15 11:14 ` Mark Brown
2021-06-21 15:31 ` Matthias Brugger
2021-06-25 11:25 ` Mark Brown
2021-06-24 20:44 ` Rob Herring
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=1614563278.1578.6.camel@mbjsdccf07 \
--to=mason.zhang@mediatek.com \
--cc=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=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).