From: David Miller <davem@davemloft.net>
To: sean.wang@mediatek.com
Cc: rdunlap@infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, blogic@openwrt.org,
nbd@openwrt.org, nelson.chang@mediatek.com, lkp@intel.com
Subject: Re: [PATCH -next] net: ethernet: mediatek: fix mtk_eth_soc build errors & warnings
Date: Wed, 05 Jun 2019 11:34:41 -0700 (PDT) [thread overview]
Message-ID: <20190605.113441.1657641162705180640.davem@davemloft.net> (raw)
In-Reply-To: <1559726369.9003.4.camel@mtkswgap22>
From: Sean Wang <sean.wang@mediatek.com>
Date: Wed, 5 Jun 2019 17:19:29 +0800
> Thanks for your help. But it seems I've already made the same fixup
> for the problem in
> http://lists.infradead.org/pipermail/linux-mediatek/2019-June/020301.html
> as soon as the kbuild test robot reported this.
No, that's not how this works.
You fix networking build fixes by sending the fix here to netdev.
Randy submitted the fix properly, so I'm applying his patch to my
tree.
prev parent reply other threads:[~2019-06-05 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 5:52 [PATCH -next] net: ethernet: mediatek: fix mtk_eth_soc build errors & warnings Randy Dunlap
2019-06-05 9:19 ` Sean Wang
2019-06-05 18:34 ` 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=20190605.113441.1657641162705180640.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=blogic@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nbd@openwrt.org \
--cc=nelson.chang@mediatek.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sean.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.