From: Stefan Assmann <sassmann@kpanic.de>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 6/6] e1000e: call ndo_stop() instead of dev_close() when running offline selftest
Date: Wed, 3 Feb 2016 09:13:45 +0100 [thread overview]
Message-ID: <56B1B6B9.7020905@kpanic.de> (raw)
In-Reply-To: <20160202.162830.131864881309085395.davem@davemloft.net>
On 02.02.2016 22:28, David Miller wrote:
>
> Always, when sending an updated version of a patch which is part of a
> series, always resubmit the entire series rather than just the patch
> which is changing.
>
> Thanks.
>
Sorry Dave, going to send out a complete V2 right away.
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Assmann <sassmann@kpanic.de>
To: David Miller <davem@davemloft.net>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH net-next 6/6] e1000e: call ndo_stop() instead of dev_close() when running offline selftest
Date: Wed, 3 Feb 2016 09:13:45 +0100 [thread overview]
Message-ID: <56B1B6B9.7020905@kpanic.de> (raw)
In-Reply-To: <20160202.162830.131864881309085395.davem@davemloft.net>
On 02.02.2016 22:28, David Miller wrote:
>
> Always, when sending an updated version of a patch which is part of a
> series, always resubmit the entire series rather than just the patch
> which is changing.
>
> Thanks.
>
Sorry Dave, going to send out a complete V2 right away.
Stefan
next prev parent reply other threads:[~2016-02-03 8:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 10:13 [Intel-wired-lan] [PATCH net-next 0/6] net/intel: call ndo_stop() instead of dev_close() when running offline selftest Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-02-02 10:13 ` [Intel-wired-lan] [PATCH net-next 1/6] i40e: " Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-02-02 10:13 ` [Intel-wired-lan] [PATCH net-next 2/6] ixgbe: " Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-02-02 10:13 ` [Intel-wired-lan] [PATCH net-next 3/6] ixgbevf: " Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-03-01 19:36 ` [Intel-wired-lan] " Bowers, AndrewX
2016-02-02 10:13 ` [Intel-wired-lan] [PATCH net-next 4/6] igb: " Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-02-02 10:13 ` [Intel-wired-lan] [PATCH net-next 5/6] e1000: " Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-02-02 10:13 ` [Intel-wired-lan] [PATCH net-next 6/6] e1000e: " Stefan Assmann
2016-02-02 10:13 ` Stefan Assmann
2016-02-02 11:09 ` [Intel-wired-lan] " kbuild test robot
2016-02-02 11:09 ` kbuild test robot
2016-02-02 12:59 ` [Intel-wired-lan] " Stefan Assmann
2016-02-02 12:59 ` Stefan Assmann
2016-02-02 21:28 ` [Intel-wired-lan] " David Miller
2016-02-02 21:28 ` David Miller
2016-02-03 8:13 ` Stefan Assmann [this message]
2016-02-03 8:13 ` Stefan Assmann
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=56B1B6B9.7020905@kpanic.de \
--to=sassmann@kpanic.de \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.