From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, Luca Coelho <luciano.coelho@intel.com>
Subject: Re: [PATCH 0/2] iwlwifi: fixes intended for 5.3 2019-07-08
Date: Mon, 15 Jul 2019 12:47:45 +0300 [thread overview]
Message-ID: <87r26rpr26.fsf@codeaurora.org> (raw)
In-Reply-To: <20190708155534.18241-1-luca@coelho.fi> (Luca Coelho's message of "Mon, 8 Jul 2019 18:55:32 +0300")
Luca Coelho <luca@coelho.fi> writes:
> This is the first patchset with fixes for v5.3.
>
> The changes are:
>
> * A few new PCI IDs for 9000 and 22000 series;
> * Support for C-step 22000 devices;
>
> As usual, I'm pushing this to a pending branch, for kbuild bot. And
> as we agreed, I'll delegate these patches to you in patchwork for you
> to apply them directly.
Great, thanks.
> There's no hurry with this, I know we're still in the merge window, I
> just wanted to send them out for people who have these devices and are
> having problems. It's your call: either send them during the merge
> window, if you send a new pull-req; or take it when the merge window
> closes, for v5.3-rc1.
There seems to few other fixes for v5.3 so I'll try to send a pull
request by end of this week, time permitting of course.
> Note: all this area will probably have some conflicts when merging
> with -next, because I've been sending new PCI IDs and such things for
> fixes, while some other changes are being made for -next. Let me know
> if you need any help merging, when time comes.
Ok, I'll keep on eye on those.
--
Kalle Valo
prev parent reply other threads:[~2019-07-15 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 15:55 [PATCH 0/2] iwlwifi: fixes intended for 5.3 2019-07-08 Luca Coelho
2019-07-08 15:55 ` [PATCH 1/2] iwlwifi: add new cards for 9000 and 20000 series Luca Coelho
2019-07-15 17:48 ` Kalle Valo
2019-07-08 15:55 ` [PATCH 2/2] iwlwifi: pcie: add support for qu c-step devices Luca Coelho
2019-07-15 9:47 ` 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=87r26rpr26.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=luciano.coelho@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.