public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
	 miriam.rachel.korenblit@intel.com
Subject: Re: putting future iwlwifi firmware into intel/ ?
Date: Wed, 17 Apr 2024 16:11:42 +0200	[thread overview]
Message-ID: <4e07bb9f498566ed89e7e967e12f01821801acc8.camel@sipsolutions.net> (raw)
In-Reply-To: <87v84gi1v4.fsf@kernel.org>

On Wed, 2024-04-17 at 15:56 +0300, Kalle Valo wrote:
> 
> Yes, please. It would be nice to cleanup linux-firmware.git top level
> directory. But what about this:
> 
> * convert iwlwifi to first use _all_ files under intel/ and then as a
>   fallback top level directory

Yeah, that's quite annoying though since we currently look for something
like "iwlwifi-<hw>-<version>.ucode", and version will go down from some
number to another number (e.g. 73 ... 43.) So now we have to double that
loop up and try intel/...-73, ...-73, intel/...-72, ...-72, etc.?

johannes

      reply	other threads:[~2024-04-17 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 11:18 putting future iwlwifi firmware into intel/ ? Johannes Berg
2024-04-17 12:31 ` Mario Limonciello
2024-04-17 12:39   ` Johannes Berg
2024-04-17 12:42     ` Mario Limonciello
2024-04-17 12:45       ` Johannes Berg
2024-04-17 13:58         ` Mario Limonciello
2024-04-17 14:09           ` Johannes Berg
2024-04-17 14:14             ` Mario Limonciello
2024-04-17 12:56 ` Kalle Valo
2024-04-17 14:11   ` Johannes Berg [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=4e07bb9f498566ed89e7e967e12f01821801acc8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox