From: Luca Coelho <luca@coelho.fi>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-next 2017-06-30
Date: Fri, 30 Jun 2017 15:56:22 +0300 [thread overview]
Message-ID: <1498827382.22048.163.camel@coelho.fi> (raw)
In-Reply-To: <874luxn3de.fsf@kamboji.qca.qualcomm.com>
On Fri, 2017-06-30 at 14:04 +0300, Kalle Valo wrote:
> Luca Coelho <luca@coelho.fi> writes:
>
> > Hi Kalle,
> >
> > Here's my final pull-request intended for v4.13. Again, this pull-
> > request includes the last two patchsets I sent out. Most importantly,
> > it contains critical fixes and FW API changes to support the upcoming FW
> > that we will release publicly for the 9000 HW family. More details in
> > the tag description.
> >
> > I have sent this out before, and kbuildbot reported success.
> >
> > Please let me know if there are any issues.
> >
> > Cheers,
> > Luca.
> >
> >
> > The following changes since commit fdcbe65d618af080ee23229f0137ffd37f2de36b:
> >
> > Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2017-06-28 22:10:48 +0300)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git tags/iwlwifi-next-for-kalle-2017-06-30
> >
> > for you to fetch changes up to ba320dd61ec91bbe98730f3407a486facc174d63:
> >
> > iwlwifi: bump MAX API for 8000/9000/A000 to 33 (2017-06-29 21:09:58 +0300)
> >
> > ----------------------------------------------------------------
> > Final set of patches for 4.13
> >
> > * Some important fixes for 9000 HW;
> > * FW API changes for the upcoming -30 ucode release;
> > * A few new PCI IDs for 9000 series;
> > * Reorganization of common files;
> > * Some more fixes and improvements here and there
> > * Initialization and other important fixes for 9000 series;
> > * Support for version 30 of the FW API for 8000 and 9000 series;
> >
> > ----------------------------------------------------------------
>
> Pulled, thanks.
>
> Let's see if I can squeeze these into 4.13 still. But in the future
> please submit patches early, for various reasons (extra work, higher
> chance of regressions etc) I really dislike having last minute patches
> for new features.
Thanks!
And ack, I will take care of the backlog now and start sending patches
probably already early next week and use the merge window to catch up.
;) After that, if I send weekly pulls, it won't back up.
--
Luca.
prev parent reply other threads:[~2017-06-30 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 10:08 pull-request: iwlwifi-next 2017-06-30 Luca Coelho
2017-06-30 11:04 ` Kalle Valo
2017-06-30 12:56 ` Luca Coelho [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=1498827382.22048.163.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=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