From: David Miller <davem@davemloft.net>
To: linus.walleij@linaro.org
Cc: netdev@vger.kernel.org, ulli.kroll@googlemail.com,
f.fainelli@gmail.com, mirq-linux@rere.qmqm.pl, andrew@lunn.ch
Subject: Re: [PATCH net-next 3/5 v3] net: gemini: Allow multiple ports to instantiate
Date: Thu, 12 Jul 2018 17:39:40 -0700 (PDT) [thread overview]
Message-ID: <20180712.173940.1072922556088754807.davem@davemloft.net> (raw)
In-Reply-To: <20180711193245.21980-3-linus.walleij@linaro.org>
From: Linus Walleij <linus.walleij@linaro.org>
Date: Wed, 11 Jul 2018 21:32:43 +0200
> The code was not tested with two ports actually in use at
> the same time. (I blame this on lack of actual hardware using
> that feature.) Now after locating a system using both ports,
> add necessary fix to make both ports come up.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Applied.
next prev parent reply other threads:[~2018-07-13 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 19:32 [PATCH net-next 1/5 v3] net: gemini: Look up L3 maxlen from table Linus Walleij
2018-07-11 19:32 ` [PATCH net-next 2/5 v3] net: gemini: Improve connection prints Linus Walleij
2018-07-11 19:57 ` Andrew Lunn
2018-07-13 0:39 ` David Miller
2018-07-11 19:32 ` [PATCH net-next 3/5 v3] net: gemini: Allow multiple ports to instantiate Linus Walleij
2018-07-13 0:39 ` David Miller [this message]
2018-07-11 19:32 ` [PATCH net-next 4/5 v3] net: gemini: Move main init to port Linus Walleij
2018-07-13 0:39 ` David Miller
2018-07-11 19:32 ` [PATCH net-next 5/5 v3] net: gemini: Indicate that we can handle jumboframes Linus Walleij
2018-07-11 19:57 ` Andrew Lunn
2018-07-13 0:39 ` David Miller
2018-07-13 0:39 ` [PATCH net-next 1/5 v3] net: gemini: Look up L3 maxlen from table 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=20180712.173940.1072922556088754807.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=ulli.kroll@googlemail.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).