public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: ath10k <ath10k@lists.infradead.org>,
	 ath11k <ath11k@lists.infradead.org>,
	 ath12k <ath12k@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: New staging repos for ath1*k firmware
Date: Fri, 17 May 2024 08:32:52 +0300	[thread overview]
Message-ID: <878r09gfzv.fsf@kernel.org> (raw)
In-Reply-To: <bac97f31-4a70-4c4c-8179-4ede0b32f869@quicinc.com> (Jeff Johnson's message of "Wed, 6 Mar 2024 11:23:06 -0800")

Jeff Johnson <quic_jjohnson@quicinc.com> writes:

> Historically, prior to being incorporated into the linux-firmware
> project, firmware for kernel.org ath1*k drivers has been first published
> to Kalle's GitHub:
> https://github.com/kvalo/ath10k-firmware
> https://github.com/kvalo/ath11k-firmware
> (ath12k firmware was pushed to the ath11k-firmware repo on a temporary
> basis in anticipation of this move)
>
> But in order to have repos with multiple maintainers, as well as to have
> a hosting platform with more control, we have moved to CodeLinaro:
> https://git.codelinaro.org/clo/ath-firmware/ath10k-firmware
> https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware
> https://git.codelinaro.org/clo/ath-firmware/ath12k-firmware
>
> Note that most people should not care about this -- normally you should
> use the firmware that is in the official linux-firmware repo:
> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/
>
> You should only need to access the staging repos if you need a previous
> version to work around an issue, or if you are testing new firmware that
> is supposed to fix a problem that you've reported.
>
> Please let Kalle & I know if you have any issues with these new repos!

The final reminder that the github.com repositories will be deleted in
two weeks. If someone is still using them switch to the new
git.codelinaro.org location NOW.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  parent reply	other threads:[~2024-05-17  5:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 19:23 New staging repos for ath1*k firmware Jeff Johnson
2024-03-07  8:39 ` Robert Marko
2024-03-07 16:49   ` Kalle Valo
2024-03-09 17:58     ` Sebastian Gottschall
2024-03-13 19:32       ` Jeff Johnson
2024-03-14  7:54         ` Robert Marko
2024-03-14 22:27         ` Felix Kaechele
2024-09-10  9:00   ` Sven Eckelmann
2024-09-10  9:23     ` Kalle Valo
2024-09-10 11:39       ` Sven Eckelmann
2024-09-10 11:46         ` Robert Marko
2024-09-11 19:18         ` Jeff Johnson
2024-05-17  5:32 ` Kalle Valo [this message]
2024-06-03 20:11   ` Kalle Valo
2024-06-03 20:21     ` pgupta
2024-06-03 20:47       ` Jeff Johnson
2025-11-21 13:28 ` Paweł Owoc

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=878r09gfzv.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.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