devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yankejian@huawei.com
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	catalin.marinas@arm.com, will.deacon@arm.com,
	huangdaode@hisilicon.com, liguozhu@huawei.com, arnd@arndb.de,
	fengguang.wu@intel.com, salil.mehta@huawei.com,
	andriy.shevchenko@linux.intel.com, lisheng011@huawei.com,
	haifeng.wei@huawei.com, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com
Subject: Re: [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf
Date: Tue, 12 Jan 2016 21:54:37 -0500 (EST)	[thread overview]
Message-ID: <20160112.215437.1621931833367908392.davem@davemloft.net> (raw)
In-Reply-To: <1452654073-28039-1-git-send-email-yankejian@huawei.com>


This is so confusing.  Why are you submitting a singleton patch and
then a 2 patch series for the same exact hns driver?

Please do not do this.

  parent reply	other threads:[~2016-01-13  2:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  3:01 [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf Kejian Yan
2016-01-13  2:52 ` Yankejian (Hackim Yim)
2016-01-13  2:54 ` David Miller [this message]
2016-01-13  3:00   ` Yankejian (Hackim Yim)
     [not found] ` <1452654073-28039-1-git-send-email-yankejian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-01-13  3:01   ` [patch v3 net-next 0/2] dts: hisi: fixes no syscon fault when init mdio Kejian Yan
2016-01-13  3:01   ` [patch v3 net-next 1/2] " Kejian Yan
2016-01-13  3:01 ` [patch v3 net-next 2/2] net: hns: fixes no syscon error " Kejian Yan
  -- strict thread matches above, loose matches on Subject: below --
2016-01-13  3:14 [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf Kejian Yan
2016-01-14  3:00 ` Yisen Zhuang
     [not found]   ` <56970F48.9060504-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-01-14  9:43     ` Andy Shevchenko
     [not found]       ` <1452764635.2521.28.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-01-18 11:35         ` Yankejian (Hackim Yim)
2016-01-20  6:49       ` Yankejian (Hackim Yim)
     [not found]         ` <569F2DEC.9040209-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-01-20  9:36           ` Andy Shevchenko
2016-01-20 11:10             ` Yankejian (Hackim Yim)
     [not found] ` <1452654880-28980-1-git-send-email-yankejian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-01-15  2:28   ` 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=20160112.215437.1621931833367908392.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=galak@codeaurora.org \
    --cc=haifeng.wei@huawei.com \
    --cc=huangdaode@hisilicon.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=liguozhu@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lisheng011@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=will.deacon@arm.com \
    --cc=yankejian@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).