From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CC1A846BF; Fri, 20 Mar 2026 07:18:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773991140; cv=none; b=mgJxq0pEeZdUUF0Gmyn7cwma9QPcF2vEStQtg+CA1ICTScmy1RUZvBQVL5MJQ/DVJpYoWs5WCZ9EN/oy+KuF2zBt589ToFWeGrfeJdwqOHekNOoJVO2DaSzs9dzGiFo7t+KUlHovPByEtTkMDqcuwhkkjQ7VR3Gh8QSVzkUmDJ0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773991140; c=relaxed/simple; bh=AEqQPYUEZ4vsLq2WyrblhoJ6ilvfdqPVGj7c7wf970E=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=LjHcpjsaS+C8bVKYZcVodAawjPK6KzoO1hsUvtLZapzAWnxPE5RC4/a4jVCkuWCSAAkdW36Uk8XibaD90OyFGqHc6NbvsutegsG0QDr99vWK7wTCJjmOZ2sL7NpkEKNMVLC6KNeOBqzymhy5k2Opxb+1bvi0N3D+oapWyY51NmY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=HOsbeRkC; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="HOsbeRkC" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=AEqQPYUEZ4vsLq2WyrblhoJ6ilvfdqPVGj7c7wf970E=; t=1773991138; x=1775200738; b=HOsbeRkCyI38PfSKlgARiOSsolpCLx91bGaZCoxW9dPN0rF IcizZ6V7uPHoY9bkEykUSAmFvF25bi1ddEACRfpbsImglT4WBkK4u96oaq5NyodWNUCyCkTuZtDtc PW7ZTLFf9xf/vAMjtVtwUltmYRsvOpRXCUDWgD9+g+Mi5fo1IL5jS1Ikl6R6bpy/LbyJDK2ODvrD+ 3i558hg2S5unTE/CIV08TBR2gwKPTa+hLGXFxHK30OYS//gAbxz2dBKmDc0AeZyEjhTTd8NvYOK81 Tr1rDJab4XnSRHpVizLWWB4OqoWBIxFmipLR5LJVOXMr8fF4BMo6p+6GRNxlcC7g==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98.2) (envelope-from ) id 1w3U8F-00000006T5W-2DnO; Fri, 20 Mar 2026 08:18:55 +0100 Message-ID: <7339202222542df9858308d3a42f438b4abf516d.camel@sipsolutions.net> Subject: Re: [PATCH wireless-next 14/35] wifi: mm81x: add mac.c From: Johannes Berg To: Lachlan Hodges Cc: Dan Callaghan , Arien Judge , Nathan Chancellor , Nick Desaulniers , Bill Wendling , Justin Stitt , ayman.grais@morsemicro.com, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Date: Fri, 20 Mar 2026 08:18:54 +0100 In-Reply-To: (sfid-20260320_073931_534695_7E5DC23D) References: <20260227041108.66508-1-lachlan.hodges@morsemicro.com> <20260227041108.66508-15-lachlan.hodges@morsemicro.com> <1ca86ec4a1af1edfb791ca65023ab1979507c5bc.camel@sipsolutions.net> <888ab7ed9c72d19765e87f00b17dd95963cbca18.camel@sipsolutions.net> (sfid-20260320_073931_534695_7E5DC23D) Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Fri, 2026-03-20 at 17:39 +1100, Lachlan Hodges wrote: > >=20 > Thinking about this a bit further, the initial items on the todo > list are more or less as follows: >=20 > 1. hostapd support (mostly unrelated, some minor tweaks to hwsim) > 2. Rx reporting - mainly mac and cfg with some minor driver changes > =C2=A0=C2=A0=C2=A0+ usermode aswell > 3. iw and iwinfo support (again, unrelated) > 4. extend regulatory support - this will be a big challenge and once > =C2=A0=C2=A0=C2=A0again mostly cfg and mac >=20 > So most driver work would just be plumbing through any required > changes for the above, no large features in the near future. >=20 > > which is probably simpler if I apply driver patches too, > > otherwise you have to synchronise pull requests to when I apply patches > > to my tree? OTOH, to pass the bot checks you already have to do that > > anyway, unless sending cfg/mac/driver patches in one series, which also > > isn't great since it ends to bury the cfg/mac patches. >=20 > Initially that works with us if you apply the patches :) Works for me too :) > I have made an account with the user "lhodges" on patchwork - no > issues with that. Nice, thanks, I'll go request you be added as admin, so I can delegate the right patches to you automatically. > We haven't got a public tree tracking wireless-next > yet. Nothing necessarily blocking that except internal processes, I > assume there's no issue adding it later? Indeed, no problem at all. I'd still somewhat prefer to have the initial commit as a pull request, but if you really don't have a public git tree now you can also send a big single commit with all the right things to me in private, and then I'll put it somewhere and send it to the list. We can figure this out either way, no big deal. Thanks, johannes