From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: net-next merge window closure
Date: Mon, 08 Dec 2014 21:54:26 -0500 (EST) [thread overview]
Message-ID: <20141208.215426.649046798788880346.davem@davemloft.net> (raw)
In-Reply-To: <1418091638.2410.21.camel@jtkirshe-mobl>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Mon, 08 Dec 2014 18:20:38 -0800
> With Linus releasing 3.18, and you parsing through the 100+ patches
> currently in the queue getting net-next ready to push to Linus for 3.19,
> I have a request/question. I have 13 more i40e patches I was hoping to
> submit to net-next before the closure (it was twelve until Joe's last
> suggestion). I can get them submitted later tonight, but if it is going
> to cause to much of an issue, I can wait for net-next to open later this
> month.
>
> Just wanted to check with you before dumping more patches onto your work
> load. :-)
Just send it in, it'll be noise in the backlog I'll be processing today
and tomorrow.
Thanks for asking.
prev parent reply other threads:[~2014-12-09 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 2:20 net-next merge window closure Jeff Kirsher
2014-12-09 2:54 ` David Miller [this message]
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=20141208.215426.649046798788880346.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox