From: David Miller <davem@davemloft.net>
To: M.Stam@fugro.nl
Cc: ben@decadent.org.uk, ckeepax@opensource.wolfsonmicro.com,
riku.voipio@iki.fi, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: "asix: Don't reset PHY on if_up for ASIX 88772" breaks net on arndale platform
Date: Wed, 12 Nov 2014 12:43:33 -0500 (EST) [thread overview]
Message-ID: <20141112.124333.526512550325097947.davem@davemloft.net> (raw)
In-Reply-To: <C89EFD3CD56F64468D3D206D683A8D2203A003FE@ldam-msx2.fugro-nl.local>
Please do not top-post.
prev parent reply other threads:[~2014-11-12 17:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 7:22 "asix: Don't reset PHY on if_up for ASIX 88772" breaks net on arndale platform Riku Voipio
2014-11-04 8:19 ` Stam, Michel [FINT]
2014-11-04 9:43 ` Riku Voipio
2014-11-04 10:23 ` Stam, Michel [FINT]
2014-11-04 20:09 ` Charles Keepax
2014-11-05 12:04 ` "asix: Don't reset PHY on if_up for ASIX 88772" breaks net onarndale platform Stam, Michel [FINT]
2014-11-05 12:39 ` Riku Voipio
2014-11-05 16:21 ` Stam, Michel [FINT]
2014-11-05 15:02 ` Charles Keepax
2014-11-05 16:17 ` "asix: Don't reset PHY on if_up for ASIX 88772" breaks netonarndale platform Stam, Michel [FINT]
2014-11-06 9:06 ` "asix: Don't reset PHY on if_up for ASIX 88772" breaks net on arndale platform Riku Voipio
2014-11-06 10:01 ` Charles Keepax
2014-11-06 12:04 ` Riku Voipio
2014-11-06 12:39 ` Stam, Michel [FINT]
2014-11-06 12:46 ` Charles Keepax
2014-11-06 14:01 ` "asix: Don't reset PHY on if_up for ASIX 88772" breaks net onarndale platform Stam, Michel [FINT]
2014-11-06 14:09 ` Charles Keepax
2014-11-07 8:44 ` Riku Voipio
2014-11-12 0:23 ` "asix: Don't reset PHY on if_up for ASIX 88772" breaks net on arndale platform Ben Hutchings
2014-11-12 9:49 ` Stam, Michel [FINT]
2014-11-12 17:43 ` 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=20141112.124333.526512550325097947.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=M.Stam@fugro.nl \
--cc=ben@decadent.org.uk \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=riku.voipio@iki.fi \
/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).