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 00/12][pull request] Intel Wired LAN Driver Updates
Date: Mon, 29 Jul 2013 02:17:47 -0700 [thread overview]
Message-ID: <1375089467.32309.40.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20130729.014643.2227589840281609643.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
On Mon, 2013-07-29 at 01:46 -0700, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Mon, 29 Jul 2013 01:34:45 -0700
>
> > On Mon, 2013-07-29 at 00:34 -0700, David Miller wrote:
> >> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> >> Date: Sun, 28 Jul 2013 19:08:55 -0700
> >>
> >> > When will your kernel.org net-next be updated? I ask because I have a
> >> > series for ixgbe I am putting together and wanted to make sure it is
> >> > against the latest net-next.
> >>
> >> Are you asking when I will next merge 'net' into 'net-next'? If so,
> >> I'll likely do it some time tomorrow.
> >
> > I am not worried about that. I just cloned your net-next tree and did
> > not see your pull of my net-next tree which had the e100 and e1000e
> > patches. I am working on creating another series against net-next and
> > the tip on kernel.org is:
> >
> > commit 9d4a0314642918cbda9ed4012df51e8df608fce6
> > Author: Hannes Frederic Sowa <hannes@stressinduktion.org>
> > Date: Fri Jul 26 17:05:16 2013 +0200
> >
> > ipv4, ipv6: send igmpv3/mld packets with TC_PRIO_CONTROL
> >
> > which is several days old. So I was not sure if I just make my series
> > against my net-next tip.
>
> Weird, it should have all of your changes.
>
> Tip is currently:
>
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=fe6f700d6cbb7e8a61711e325f53d9c9e0a42a4c
>
> net/mlx4_core: Respond to operation request by firmware
All looks fine now, thanks!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-29 9:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 11:41 [net-next 00/12][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-07-28 11:41 ` [net-next 01/12] e100: dump small buffers via %*ph Jeff Kirsher
2013-07-28 11:41 ` [net-next 02/12] e1000e: restore call to pci_clear_master() Jeff Kirsher
2013-07-28 11:41 ` [net-next 03/12] e1000e: Remove duplicate assignment of default rx/tx ring size Jeff Kirsher
2013-07-28 11:41 ` [net-next 04/12] e1000e: Use marco instead of digit for defining e1000_rx_desc_packet_split Jeff Kirsher
2013-07-28 11:41 ` [net-next 05/12] e1000e: disable ASPM L1 on 82583 Jeff Kirsher
2013-07-28 11:41 ` [net-next 06/12] e1000e: iAMT connections drop on driver unload when jumbo frames enabled Jeff Kirsher
2013-07-28 11:41 ` [net-next 07/12] e1000e: low throughput using 4K jumbos on I218 Jeff Kirsher
2013-07-28 11:41 ` [net-next 08/12] e1000e: Tx hang on I218 when linked at 100Half and slow response at 10Mbps Jeff Kirsher
2013-07-28 11:41 ` [net-next 09/12] e1000e: ethtool unnecessarily takes device out of RPM suspend Jeff Kirsher
2013-07-28 11:41 ` [net-next 10/12] e1000e: enable support for new device IDs Jeff Kirsher
2013-07-28 11:41 ` [net-next 11/12] e1000e: do not resume device from RPM suspend to read PHY status registers Jeff Kirsher
2013-07-28 11:41 ` [net-next 12/12] e1000e: fix I217/I218 PHY initialization flow Jeff Kirsher
2013-07-28 20:21 ` [net-next 00/12][pull request] Intel Wired LAN Driver Updates David Miller
2013-07-28 23:11 ` Jeff Kirsher
2013-07-29 0:20 ` David Miller
2013-07-29 2:08 ` Jeff Kirsher
2013-07-29 7:34 ` David Miller
2013-07-29 8:34 ` Jeff Kirsher
2013-07-29 8:46 ` David Miller
2013-07-29 9:17 ` Jeff Kirsher [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 10:22 Jeff Kirsher
2013-12-11 2:30 ` David Miller
2013-05-21 22:03 Jeff Kirsher
2013-05-22 20:57 ` David Miller
2013-03-28 9:00 Jeff Kirsher
2013-03-28 18:39 ` David Miller
2012-10-23 4:26 Jeff Kirsher
2012-10-23 6:51 ` David Miller
2012-05-10 6:46 Jeff Kirsher
2012-05-11 3:18 ` David Miller
2012-03-17 8:50 Jeff Kirsher
2012-03-17 9:06 ` David Miller
2012-01-26 7:21 Jeff Kirsher
2012-01-26 18:49 ` David Miller
2012-01-26 21:27 ` 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=1375089467.32309.40.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).