From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 0/6][pull request] 100GbE Intel Wired LAN Driver Updates 2018-05-07
Date: Tue, 08 May 2018 00:10:45 -0400 (EDT) [thread overview]
Message-ID: <20180508.001045.1674673870907537309.davem@davemloft.net> (raw)
In-Reply-To: <20180507144521.6979-1-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Mon, 7 May 2018 07:45:15 -0700
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE
Hmmm...
[davem@localhost net-next]$ git pull --no-ff git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE
>From git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue
* branch 100GbE -> FETCH_HEAD
Already up to date.
[davem@localhost net-next]$
next prev parent reply other threads:[~2018-05-08 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 14:45 [net-next 0/6][pull request] 100GbE Intel Wired LAN Driver Updates 2018-05-07 Jeff Kirsher
2018-05-07 14:45 ` [net-next 1/6] fm10k: setup VLANs for l2 accelerated macvlan interfaces Jeff Kirsher
2018-05-07 14:45 ` [net-next 2/6] fm10k: reduce duplicate fm10k_stat macro code Jeff Kirsher
2018-05-08 16:59 ` Joe Perches
2018-05-08 17:40 ` Keller, Jacob E
2018-05-07 14:45 ` [net-next 3/6] fm10k: use variadic arguments to fm10k_add_stat_strings Jeff Kirsher
2018-05-07 14:45 ` [net-next 4/6] fm10k: use macro to avoid passing the array and size separately Jeff Kirsher
2018-05-07 14:45 ` [net-next 5/6] fm10k: warn if the stat size is unknown Jeff Kirsher
2018-05-07 14:45 ` [net-next 6/6] fm10k: don't protect fm10k_queue_mac_request by fm10k_host_mbx_ready Jeff Kirsher
2018-05-08 4:10 ` David Miller [this message]
2018-05-09 15:19 ` [net-next 0/6][pull request] 100GbE Intel Wired LAN Driver Updates 2018-05-07 Jeff Kirsher
2018-05-09 0:29 ` 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=20180508.001045.1674673870907537309.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--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).