From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org Wireless"
<linux-wireless@vger.kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-08-14
Date: Thu, 14 Aug 2014 18:30:54 -0700 [thread overview]
Message-ID: <027436B7-E5DF-4AFB-B43C-65AB41D0200D@holtmann.org> (raw)
In-Reply-To: <20140815095547.75d9e9d4@canb.auug.org.au>
Hi Stephen,
>> Here's our first bluetooth-next pull request for the 3.18 kernel. Our
>> tree is based on net-next so you'd need to pull from there first before
>> pulling from our tree.
>
> This is in a branch that will be included in linux-next today. I guess
> you didn't read my (very often) repeated request that no v3.18 material
> be included until after v3.17-rc1 is released ... Please do not do that.
to be honest I did not know about this rule. Next time, I will create a special tree for the time during the merge window so that we can continue pushing out patches for the next release. For us the world is not standing still just because we have a 2 week merge window.
Regards
Marcel
next prev parent reply other threads:[~2014-08-15 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 14:50 Johan Hedberg
2014-08-14 23:55 ` Stephen Rothwell
2014-08-14 23:58 ` Stephen Rothwell
2014-08-15 1:30 ` Marcel Holtmann [this message]
2014-08-15 14:45 ` John W. Linville
2014-08-15 16:32 ` Marcel Holtmann
2014-08-25 19:59 ` John W. Linville
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=027436B7-E5DF-4AFB-B43C-65AB41D0200D@holtmann.org \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®