linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Robinson <pbrobinson@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:TI WILINK WIRELES..." <linux-wireless@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	Kalle Valo <kvalo@codeaurora.org>,
	Josh Boyer <jwboyer@kernel.org>, Ferry Toth <fntoth@gmail.com>
Subject: Re: commit 0f0aefd733f7 to linux-firmware effectively broke all of the setups with old kernels
Date: Mon, 15 Feb 2021 18:02:59 +0000	[thread overview]
Message-ID: <CALeDE9PkZnrZ=cXKB16+oZ0=O=3XSYqsgXi9TKeuWT7KqXrdNQ@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VecgvsDqRwmyJZb8z0n4XAUjEStrVmXDZ9-knud7_eO3A@mail.gmail.com>

> Seems the commit 0f0aefd733f7 to linux-firmware effectively broke all
> of the setups with the old kernels. Firmware name is an ABI (!) and
> replacing it like this will definitely break systems with older
> kernels. Linux firmware package likely, but unfortunately, should
> carry on both versions as long as it's needed. Alternative solution is
> to provide the links during installation.

It does provide the links using the copy-firmware.sh and the details in WHENCE.

The alternative is to leave firmwares in place with CVEs.

  reply	other threads:[~2021-02-15 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 14:35 commit 0f0aefd733f7 to linux-firmware effectively broke all of the setups with old kernels Andy Shevchenko
2021-02-15 18:02 ` Peter Robinson [this message]
2021-02-15 18:25   ` Andy Shevchenko

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='CALeDE9PkZnrZ=cXKB16+oZ0=O=3XSYqsgXi9TKeuWT7KqXrdNQ@mail.gmail.com' \
    --to=pbrobinson@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=fntoth@gmail.com \
    --cc=jwboyer@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).