devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Leilk Liu <leilk.liu@mediatek.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	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, ryder.lee@mediatek.com
Subject: Re: [PATCH v2 0/1] add SPI driver support for mt7629
Date: Tue, 27 Nov 2018 11:43:24 +0000	[thread overview]
Message-ID: <20181127114324.GA3206@sirena.org.uk> (raw)
In-Reply-To: <1543285790-11379-1-git-send-email-leilk.liu@mediatek.com>

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

On Tue, Nov 27, 2018 at 10:29:49AM +0800, Leilk Liu wrote:
> From cf719ac350c36cb58e2013b58f73ad04f6981384 Mon Sep 17 00:00:00 2001
> From: Leilk Liu <leilk.liu@mediatek.com>
> Date: Tue, 27 Nov 2018 10:18:30 +0800
> Subject: [PATCH v2 0/1] add SPI driver support for mt7629
> 
> v2:
> remove "mediatek,mt7629-spi" compatible according Matthias's advice.

Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff.  This reduces mail volume and ensures that 
any important information is recorded in the changelog rather than being
lost. 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2018-11-27 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  2:29 [PATCH v2 0/1] add SPI driver support for mt7629 Leilk Liu
2018-11-27  2:29 ` [PATCH v2 1/1] spi: mediatek: Add bindings for mediatek MT7629 soc platform Leilk Liu
2018-11-27 11:43 ` Mark Brown [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=20181127114324.GA3206@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=leilk.liu@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=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=ryder.lee@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).