From: "rwarsow@gmx.de" <rwarsow@gmx.de>
To: linux-kernel@vger.kernel.org, bpoirier@suse.com
Subject: Re: [PATCH] e1000e: Fix e1000_check_for_copper_link_ich8lan return value.
Date: Wed, 10 Jan 2018 02:50:32 +0100 [thread overview]
Message-ID: <3e6f2ca6-75cb-6902-80ad-f95fbd03a11d@gmx.de> (raw)
...
thanks for quick supoort !!!
--
Greeting
Ronald
next reply other threads:[~2018-01-10 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 1:50 rwarsow [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 0:29 [PATCH] e1000e: Fix e1000_check_for_copper_link_ich8lan return value rwarsow
2018-01-10 1:34 ` Benjamin Poirier
2018-01-14 8:23 ` Greg KH
2017-12-18 16:50 rwarsow
2017-12-08 10:45 [PATCH 4.4 71/96] e1000e: Separate signaling for link check/link up Christian Hesse
2017-12-11 7:26 ` [PATCH] e1000e: Fix e1000_check_for_copper_link_ich8lan return value Benjamin Poirier
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=3e6f2ca6-75cb-6902-80ad-f95fbd03a11d@gmx.de \
--to=rwarsow@gmx.de \
--cc=bpoirier@suse.com \
--cc=linux-kernel@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).