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 9149C402459; Tue, 24 Mar 2026 15:25:08 +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=1774365909; cv=none; b=RkR2f33IrXC82NHJkBXWI9pIJldMhw7EzKXjqe4ePolFjvUg1iR1GZnzsm5IU7umt90W4BTPNe8WzqLnpvzfs047/pXWX0UFiLM2+9TKBmHMg+dVfz+utPiW4xQ6RESIjrdoCg3KCOjgsXLTUZFnXRGpRTxKIEfMrphl4Nr9rFc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774365909; c=relaxed/simple; bh=JNyYFA76J+jQHcBV1rf+dBeWcK1puB0zpjFH0YPVt7c=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=FWY21vJYx+3VrYCIy9UeKB1KxYaSosR0C+naoUq1+ZBLS4w0fwMH+xk871XWHFHXW59m8MIr+es0F3yp0tt66rOzbrj36B4iWdGs5pmq+wtEl25W70U/vgUgHdfcwckPu7OvuvAUBbyUw3hKx901Xs74WbZ2PqovOm3ok8n/St8= 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=b14Pkza7; 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="b14Pkza7" 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=HnMY1RSwhTCYvBir6obZ+OuRp6EWJUCF7twCrDHIGWw=; t=1774365908; x=1775575508; b=b14Pkza7uhSf3cGA/sCfkuipU5d9DMuPWIW8VEWRBEwhwGG 3mTXQfM17WnxK356BQkH/6eC47P1/gEvW21SQWUmOPhLs3nUU2drWuNpJyoYTH58L1bUULkcwOm6v SuQq5oSfe9Hmd6Wtrc7w7hy15ug+26a5gEYVIkKim5nsij54xIBmty8evrAGarSzWLxnXIZEFwLXn 9vnmRwr6VRSIORIOkRn68nxb7n9Ud55LrtpkD7pGdnhyLX/OcWniRwdSVj7j8dpp0/IBFHDxOKmbb kwmm/uGHTkR6hI2Poof+uUyZZ82cEXMt2W/cXi5nvOjngGpAr+ml4Vvsb91GKB+A==; 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 1w53co-0000000Azl0-1BAa; Tue, 24 Mar 2026 16:24:58 +0100 Message-ID: <3d2f9e4d3f06f93e8eb191ade69f4b43752a36bf.camel@sipsolutions.net> Subject: Re: pull request: mt76-next 2026-03-23 From: Johannes Berg To: Felix Fietkau , linux-wireless Cc: Ryder Lee , devicetree@vger.kernel.org, Krzysztof Kozlowski , Conor Dooley Date: Tue, 24 Mar 2026 16:24:57 +0100 In-Reply-To: References: 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-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Mon, 2026-03-23 at 10:33 +0100, Felix Fietkau wrote: > The following changes since commit 9ac76f3d0bb2940db3a9684d596b9c8f301ef3= 15: >=20 > Merge tag 'wireless-next-2026-03-19' of https://git.kernel.org/pub/scm= /linux/kernel/git/wireless/wireless-next (2026-03-19 15:30:20 +0100) >=20 > are available in the Git repository at: >=20 > https://github.com/nbd168/wireless tags/mt76-next-2026-03-23 [...] > dt-bindings: net: wireless: mt76: add mt79 PCI devices > dt-bindings: net: wireless: mt76: clarify backoff limit usage OK I have no idea what happened here, apparently Ryder has a super messed up email setup that ended up sending different versions with the same Message-Id, so the lore archive is a big mess ... whatever is going on there, please fix that. But given what I _can_ see about these patches in the archive, I don't want to pull this now unless I get a clear ACK from DT maintainers. johannes