Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: linux-wireless@vger.kernel.org
Subject: Re: 4.8 merge window closing
Date: Wed, 13 Jul 2016 10:18:28 +0300	[thread overview]
Message-ID: <8760saatvf.fsf@purkki.adurom.net> (raw)
In-Reply-To: <878txg2ld6.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Tue, 05 Jul 2016 17:46:45 +0300")

Kalle Valo <kvalo@codeaurora.org> writes:

> Linus released 4.7-rc6 last Sunday but didn't give any hints how close
> the real release is, but nevertheless the merge window for 4.8 is
> getting quite close so if there's anything you want to have in
> wireless-drivers-next for 4.8 better send them NOW. Especially as I
> won't have that much time to apply patches the next two weeks.

Due to travelling Linus gave us one more week so the deadline for
wireless-drivers patches is now next Sunday (or so). As I'm taking it
easy this week still I will start actively applying patches only next
week, but better to have the patches reviewed and ready by then.

-- 
Kalle Valo

      reply	other threads:[~2016-07-13  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 14:46 4.8 merge window closing Kalle Valo
2016-07-13  7:18 ` Kalle Valo [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=8760saatvf.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@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