From: Johannes Berg <johannes@sipsolutions.net>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: Emily Chien <emily.chien@canonical.com>,
Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>,
Anthony Wong <anthony.wong@canonical.com>,
netdev@vger.kernel.org, Johannes Stezenbach <js@sig21.net>
Subject: Re: About the alx WoL feature
Date: Tue, 22 May 2018 09:44:57 +0200 [thread overview]
Message-ID: <1526975097.6787.4.camel@sipsolutions.net> (raw)
In-Reply-To: <CAFv23QkYwaJ1+aLLBeWkfRDyVt28imMdRBz_3ujgcWeL0AHJ-Q@mail.gmail.com>
+netdev
Hi,
> Sorry to write to you directly, I'm not sure if I should CC some
> public lists, please feel free to add them if that's the right way to
> do.
I think it is, adding netdev.
> I would like to add back the alx WoL feature which is reverted by you
> 5 years ago, and we have some discussions here[1] and here[2].
[...]
> 1. https://patchwork.kernel.org/patch/10331135/
> 2. https://patchwork.kernel.org/patch/10396651/
> David Miller insists to fix the wake up issue before we can add this
> feature back,
Rightfully so!
> so I'm wondering if you still have the machine which can
> reproduce the wake up issue or know who might have the machine and
> willing to help.
I still have the machine that I initially did this development on, but
it's been purposed as my NAS so testing on it is somewhat awkward.
However, as far as I remember (why the hell are you doing this 5 years
later?!) the problem never occurred on my machine. Perhaps on Johannes
Stezenbach's machine? I don't recall, but see emails in my inbox from
him related to alx WoL.
> We can try contacting Qualcomm and/or Rivet Network to sort out the issue.
Good luck with that, heh.
johannes
parent reply other threads:[~2018-05-22 7:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAFv23QkYwaJ1+aLLBeWkfRDyVt28imMdRBz_3ujgcWeL0AHJ-Q@mail.gmail.com>]
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=1526975097.6787.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=acelan.kao@canonical.com \
--cc=andrew@lunn.ch \
--cc=anthony.wong@canonical.com \
--cc=davem@davemloft.net \
--cc=emily.chien@canonical.com \
--cc=js@sig21.net \
--cc=netdev@vger.kernel.org \
/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).