From: Leilk Liu <leilk.liu@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH V5 0/3] Add compatible for Mediatek MT8186
Date: Thu, 10 Feb 2022 09:15:37 +0800 [thread overview]
Message-ID: <2707120457e962a78e3c4ffd231ca25a7138ae72.camel@mediatek.com> (raw)
In-Reply-To: <YgO+pXPtptHCQ9Zu@sirena.org.uk>
On Wed, 2022-02-09 at 13:16 +0000, Mark Brown wrote:
> On Wed, Feb 09, 2022 at 09:44:40AM +0800, Leilk Liu wrote:
> > V5:
> > 1. re-send these patchs based on v5.17-rc1.
> > 2. add the flags: "Reviewed-by Rob Herring".
>
> Please do not submit new versions of already applied patches, please
> submit incremental updates to the existing code. Modifying existing
> commits creates problems for other users building on top of those
> commits so it's best practice to only change pubished git commits if
> absolutely essential.
Sorry to ignore the applied mail before I sent this new versions,
thanks for your reminder.
prev parent reply other threads:[~2022-02-10 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 1:44 Leilk Liu
2022-02-09 1:44 ` [PATCH V5 1/3] dt-bindings: spi: Convert spi-slave-mt27xx to json-schema Leilk Liu
2022-02-09 1:44 ` [PATCH V5 2/3] dt-bindings: spi: Convert spi-mt65xx " Leilk Liu
2022-02-09 1:44 ` [PATCH V5 3/3] dt-bindings: spi: Add compatible for Mediatek MT8186 Leilk Liu
2022-02-09 13:16 ` [PATCH V5 0/3] " Mark Brown
2022-02-10 1:15 ` Leilk Liu [this message]
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=2707120457e962a78e3c4ffd231ca25a7138ae72.camel@mediatek.com \
--to=leilk.liu@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 \
/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
all inboxes | Powered by JetHome®