linux-kernel - linux-next: request to include ath.git tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ed7163yd.fsf@kernel.org>
Date: Tue, 06 Aug 2024 18:55:38 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jeff Johnson <quic_jjohnson@...cinc.com>,
    ath12k@...ts.infradead.org, linux-wireless@...r.kernel.org,
    linux-kernel@...r.kernel.org
Subject: linux-next: request to include ath.git tree

Hi Stephen,

ath.git is a tree for Atheros and Qualcomm Wi-Fi drivers residing under
drivers/net/wireless/ath/. Jeff and I are the maintainers. Over the
years multiple people have been requesting including the tree to
linux-next and finally we are biting the bullet.

So we are requesting to pull two branches from our ath.git tree to linux-next:

git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git for-current
git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git for-next

for-current feeds the wireless tree and for-next feeds the wireless-next
tree.

Because our for-next branch is very active one problem with is that the
chances of having conflicts between the branches is high and that would
be extra work for you :/ Do you have any suggestions for this? For
example, should we create temporary merges for you or something like
that? Just for this reason we do try to keep the number of patches going
to for-current minimal and only take important fixes.

Kalle