From: David Miller <davem@davemloft.net>
To: matthias.bgg@gmail.com
Cc: nelson.chang@mediatek.com, frank-w@public-files.de,
netdev@vger.kernel.org, sean.wang@mediatek.com,
linux-mips@vger.kernel.org, linux@armlinux.org.uk,
opensource@vdorst.com, linux-mediatek@lists.infradead.org,
john@phrozen.org, sr@denx.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v4 3/3] dt-bindings: net: ethernet: Update mt7622 docs and dts to reflect the new phylink API
Date: Wed, 28 Aug 2019 12:56:58 -0700 (PDT) [thread overview]
Message-ID: <20190828.125658.1743313522645522716.davem@davemloft.net> (raw)
In-Reply-To: <e45565b1-bb63-66af-16f6-5c7c1094dd67@gmail.com>
From: Matthias Brugger <matthias.bgg@gmail.com>
Date: Wed, 28 Aug 2019 11:29:45 +0200
> Thanks for taking this patch. For the next time, please make sure that dts[i]
> patches are independent from the binding description, as dts[i] should go
> through my tree. No problem for this round, just saying for the future.
That's not always possible nor reasonable, to be quite honest.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-28 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 17:43 [PATCH net-next v4 0/3] net: ethernet: mediatek: convert to PHYLINK René van Dorst
2019-08-25 17:43 ` [PATCH net-next v4 1/3] net: ethernet: mediatek: Add basic PHYLINK support René van Dorst
2019-08-25 17:43 ` [PATCH net-next v4 2/3] net: ethernet: mediatek: Re-add support SGMII René van Dorst
2019-08-25 17:43 ` [PATCH net-next v4 3/3] dt-bindings: net: ethernet: Update mt7622 docs and dts to reflect the new phylink API René van Dorst
2019-08-28 9:29 ` Matthias Brugger
2019-08-28 19:56 ` David Miller [this message]
2019-08-29 7:03 ` Matthias Brugger
2019-08-26 9:24 ` Aw: [PATCH net-next v4 0/3] net: ethernet: mediatek: convert to PHYLINK Frank Wunderlich
2019-08-28 3:19 ` David Miller
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=20190828.125658.1743313522645522716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=frank-w@public-files.de \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=nelson.chang@mediatek.com \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=sean.wang@mediatek.com \
--cc=sr@denx.de \
/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).