From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: net-next closure?
Date: Wed, 02 Sep 2015 23:30:21 -0700 (PDT) [thread overview]
Message-ID: <20150902.233021.1918833228551169263.davem@davemloft.net> (raw)
In-Reply-To: <1441259435.3084.3.camel@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 02 Sep 2015 22:50:35 -0700
> I was just about to send out my last series of patches and noticed you
> sent Linus your pull request. So I am guessing that your net-next tree
> is now closed, correct? Just want to make sure before sending anything
> out and did not want to dump patches on you right before the closure of
> your net-next.
Yeah, I already applied too much crap after the merge window openned
up so net-next is definitely closed now.
Thanks.
prev parent reply other threads:[~2015-09-03 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 5:50 net-next closure? Jeff Kirsher
2015-09-03 6:30 ` 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=20150902.233021.1918833228551169263.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;
as well as URLs for NNTP newsgroup(s).