All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: sean.wang@kernel.org
Cc: nbd@nbd.name,  lorenzo.bianconi@redhat.com,
	 sean.wang@mediatek.com, deren.wu@mediatek.com,
	 mingyen.hsieh@mediatek.com, linux-wireless@vger.kernel.org,
	 linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/6] Revert "wifi: mt76: mt7925: Update mt7925_mcu_uni_[tx,rx]_ba for MLO"
Date: Wed, 08 Jan 2025 17:00:13 +0200	[thread overview]
Message-ID: <87v7uppczm.fsf@kernel.org> (raw)
In-Reply-To: <20250108022509.217803-1-sean.wang@kernel.org> (sean wang's message of "Tue, 7 Jan 2025 18:25:04 -0800")

sean.wang@kernel.org writes:

> From: Ming Yen Hsieh <mingyen.hsieh@mediatek.com>
>
> This reverts commit 3cc610e9069db69e4a0f6304993f4c98db52c3c7.

Why? The commit message should always answer that.

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

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


      parent reply	other threads:[~2025-01-08 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  2:25 [PATCH 1/6] Revert "wifi: mt76: mt7925: Update mt7925_mcu_uni_[tx,rx]_ba for MLO" sean.wang
2025-01-08  2:25 ` [PATCH 2/6] wifi: mt76: mt7925: fix the wrong link_idx when has p2p_device sean.wang
2025-01-08  2:25 ` [PATCH 3/6] wifi: mt76: mt7925: fix the wrong simultaneous cap for MLO sean.wang
2025-01-08  2:25 ` [PATCH 4/6] wifi: mt76: mt7925: adjust rm BSS flow to prevent next connection failure sean.wang
2025-01-08  2:25 ` [PATCH 5/6] wifi: mt76: mt7925: integrate *mlo_sta_cmd and *sta_cmd sean.wang
2025-01-08  2:25 ` [PATCH 6/6] wifi: mt76: mt7925: update the power-saving flow sean.wang
2025-01-08 15:00 ` Kalle Valo [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=87v7uppczm.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=deren.wu@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=mingyen.hsieh@mediatek.com \
    --cc=nbd@nbd.name \
    --cc=sean.wang@kernel.org \
    --cc=sean.wang@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.