linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Thomas Backlund <tmb@mageia.org>, linux-wireless@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: fix firmware names for 9xxx and a0 series hw
Date: Tue, 14 Nov 2017 12:52:01 +0200	[thread overview]
Message-ID: <1510656721.4011.87.camel@coelho.fi> (raw)
In-Reply-To: <20171114103751.7761-1-tmb@mageia.org>

On Tue, 2017-11-14 at 12:37 +0200, Thomas Backlund wrote:
> iwlwifi 9xxx and a0 series hw contains an extra dash in firmware file
> name
> as seeen in modinfo output for kernel 4.14:
> 
> firmware:       iwlwifi-9260-th-b0-jf-b0--34.ucode
> firmware:       iwlwifi-9260-th-a0-jf-a0--34.ucode
> firmware:       iwlwifi-9000-pu-a0-jf-b0--34.ucode
> firmware:       iwlwifi-9000-pu-a0-jf-a0--34.ucode
> firmware:       iwlwifi-QuQnj-a0-hr-a0--34.ucode
> firmware:       iwlwifi-QuQnj-a0-jf-b0--34.ucode
> firmware:       iwlwifi-QuQnj-f0-hr-a0--34.ucode
> firmware:       iwlwifi-Qu-a0-jf-b0--34.ucode
> firmware:       iwlwifi-Qu-a0-hr-a0--34.ucode
> 
> Fix that by dropping the extra adding of '"-"'.
> 
> Signed-off-by: Thomas Backlund <tmb@mageia.org>
> cc: Luca Coelho <luciano.coelho@intel.com>
> cc: stable@vger.kernel.org
> 
> ---

Looks good, thanks!

Though I'm not sure this is worth sending to stable... Why do you think
it's needed?

Anyway, I'm applying it in our internal tree and it will reach the
mainline following our normal upstreaming process.

--
Cheers,
Luca.

  reply	other threads:[~2017-11-14 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 10:37 [PATCH] iwlwifi: fix firmware names for 9xxx and a0 series hw Thomas Backlund
2017-11-14 10:52 ` Luca Coelho [this message]
2017-11-14 11:29   ` Thomas Backlund
2017-11-14 11:38     ` Luciano Coelho
2017-11-14 11:48       ` Greg KH
2017-11-14 11:50         ` Luciano Coelho

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=1510656721.4011.87.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tmb@mageia.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).