Netdev List
 help / color / mirror / Atom feed
From: Pavlos Parissis <pavlos.parissis@gmail.com>
To: "Fujinaka, Todd" <todd.fujinaka@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] Instability of i40e driver on 4.9 kernel
Date: Wed, 25 Oct 2017 23:49:26 +0200	[thread overview]
Message-ID: <f93f4088-ce28-181c-6812-c4bea8479c72@gmail.com> (raw)
In-Reply-To: <9B4A1B1917080E46B64F07F2989DADD697A3FFD1@ORSMSX114.amr.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1048 bytes --]

On 21/10/2017 02:07 πμ, Fujinaka, Todd wrote:
> You picked a bunch of places to post this, and you really should've used a
> different place: e1000-devel@lists.sourceforge.net
> 

Just subscribed to that ML and mailed about it.

> Also, since you flagged the "communities" post as "answered", you're not likely
> to get any follow-up. The Intel communities are also not monitored as much by
> the wired networking people at Intel.

I don't see it as "answered" when I visit the page, maybe the fact I have replied
with extra information is confusing something. Anyway, it isn't that important
since the "communities" posts aren't monitored by Intel people, which makes sense
as it is very time consuming to monitor mailing lists and web forums at the same time.

> 
> Please let us know if you have any specific issues, and please provide exact
> reproduction steps so we can investigate your issues, and please use
> e1000-devel.

I hope the information I provided in my mail to e1000-devel is enough.

Thanks,
Pavlos


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-10-25 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 23:02 Instability of i40e driver on 4.9 kernel Pavlos Parissis
2017-10-21  0:07 ` [Intel-wired-lan] " Fujinaka, Todd
2017-10-25 21:49   ` Pavlos Parissis [this message]
2017-10-27 23:16     ` Paweł Staszewski

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=f93f4088-ce28-181c-6812-c4bea8479c72@gmail.com \
    --to=pavlos.parissis@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=todd.fujinaka@intel.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