From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 0/8][pull request] Intel Wired LAN Driver Updates
Date: Mon, 17 Sep 2012 01:15:34 -0700 [thread overview]
Message-ID: <1347869734.2093.7.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20120917.005636.200884862654234164.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Mon, 2012-09-17 at 00:56 -0400, David Miller wrote:
>
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Sun, 16 Sep 2012 21:15:34 -0700
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-next
> master
>
> Sigh...
>
> You changed this tree.
>
> It originally had the IGB PTP changes, which you asked me to
> reconsider.
>
> So I went to pull them in and now it had these new changes in
> it, which I accidently pushed out to net-next instead of the
> IGB stuff.
>
> Never do this. If you wanted me to consider to sets of
> changes seperatedly, put them in seperate branches for me
> to pull from.
Sorry, I had not heard anything after several days, and since there had
been a number of changes to the tree since I last sent out the push
message I was going to re-sbumbit them against an updated tree.
I will put together a branch with the igb patches now.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-17 8:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 4:15 [net-next 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2012-09-17 4:15 ` [net-next 1/8] e1000: add byte queue limits Jeff Kirsher
2012-09-17 4:15 ` [net-next 2/8] ixgbe: Fix ordering of things so that PF correctly configures its VLANs Jeff Kirsher
2012-09-17 4:15 ` [net-next 3/8] ixgbe: Fix VF rate limiting to correctly account for more queues per VF Jeff Kirsher
2012-09-17 4:15 ` [net-next 4/8] ixgbe: fix reporting of spoofed packets Jeff Kirsher
2012-09-17 4:15 ` [net-next 5/8] ixgbe: add debugfs support Jeff Kirsher
2012-09-17 4:15 ` [net-next 6/8] ixgbe: added netdev_ops file to debugfs Jeff Kirsher
2012-09-17 4:15 ` [net-next 7/8] ixgbe: added reg_ops " Jeff Kirsher
2012-09-17 4:15 ` [net-next 8/8] ixgbe: Improve statistics accuracy for DDP traffic Jeff Kirsher
2012-09-17 4:56 ` [net-next 0/8][pull request] Intel Wired LAN Driver Updates David Miller
2012-09-17 8:15 ` Jeff Kirsher [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-01 0:53 Jeff Kirsher
2014-01-02 4:01 ` David Miller
2013-09-06 5:43 Jeff Kirsher
2013-09-06 5:58 ` Jeff Kirsher
2013-06-14 3:55 Jeff Kirsher
2013-04-26 4:57 Jeff Kirsher
2013-04-27 3:34 ` David Miller
2012-10-23 10:24 Jeff Kirsher
2012-10-23 17:28 ` David Miller
2012-08-31 5:16 Jeff Kirsher
2012-08-31 20:03 ` David Miller
2012-07-17 10:09 Jeff Kirsher
2012-07-17 10:22 ` David Miller
2012-05-04 10:35 Jeff Kirsher
2012-05-04 15:49 ` David Miller
2012-05-01 8:51 Jeff Kirsher
2011-11-16 12:51 Jeff Kirsher
2011-11-16 23:12 ` David Miller
2011-11-16 23:21 ` Jeff Kirsher
2011-11-16 23:32 ` David Miller
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=1347869734.2093.7.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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;
as well as URLs for NNTP newsgroup(s).