devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: lidongpo@hisilicon.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
	yisen.zhuang@huawei.com, salil.mehta@huawei.com, arnd@arndb.de,
	andrew@lunn.ch, xuejiancheng@hisilicon.com,
	benjamin.chenhao@hisilicon.com, caizhiyong@hisilicon.com,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] net: hix5hd2_gmac: keep the compatible string not changed
Date: Tue, 20 Dec 2016 14:13:47 -0500 (EST)	[thread overview]
Message-ID: <20161220.141347.359771649872892693.davem@davemloft.net> (raw)
In-Reply-To: <1482199769-106501-1-git-send-email-lidongpo@hisilicon.com>

From: Dongpo Li <lidongpo@hisilicon.com>
Date: Tue, 20 Dec 2016 10:09:27 +0800

> This patch series fix the patch:
> d0fb6ba75dc0 ("net: hix5hd2_gmac: add generic compatible string")
> 
> The SoC hix5hd2 compatible string has the suffix "-gmac" and
> we should not change its compatible string.
> So we should name all the compatible string with the suffix "-gmac".
> Creating a new name suffix "-gemac" is unnecessary.

Series applied.

      parent reply	other threads:[~2016-12-20 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20  2:09 [PATCH 0/2] net: hix5hd2_gmac: keep the compatible string not changed Dongpo Li
2016-12-20  2:09 ` [PATCH 1/2] net: hix5hd2_gmac: fix compatible strings name Dongpo Li
     [not found] ` <1482199769-106501-1-git-send-email-lidongpo-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2016-12-20  2:09   ` [PATCH 2/2] ARM: dts: hix5hd2: don't change the existing compatible string Dongpo Li
2016-12-20 19:13 ` David Miller [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=20161220.141347.359771649872892693.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=benjamin.chenhao@hisilicon.com \
    --cc=caizhiyong@hisilicon.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lidongpo@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=xuejiancheng@hisilicon.com \
    --cc=yisen.zhuang@huawei.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).