Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Chris Lu <chris.lu@mediatek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, sean.wang@mediatek.com,
	will-cy.Lee@mediatek.com, ss.wu@mediatek.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/2] Bluetooth: btmtksdio: Stop discarding the hardware device id
Date: Mon, 31 Aug 2026 17:20:12 +0000	[thread overview]
Message-ID: <178819681225.671757.15863608623551543473.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260825033634.499118-1-chris.lu@mediatek.com>

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 25 Aug 2026 11:36:32 +0800 you wrote:
> btmtksdio_setup() reads the device id from register 0x70010200 and then
> throws it away twice: an snprintf() overwrites the filename that
> btmtk_fw_get_filename() derived from it, and mt79xx_setup() passes a
> hardcoded 0 on to btmtk_setup_firmware_79xx().
> 
> Neither matters on supported hardware, since the device ids that would
> make a difference - 0x6639, 0x7925 and a flavored 0x7961 - all belong to
> parts with no SDIO interface. So this targets bluetooth-next with no
> Fixes: tags. What it buys is that the two functions stop silently ignoring
> their input, which is a trap for the next chip added to this driver.
> 
> [...]

Here is the summary with links:
  - [1/2] Bluetooth: btmtksdio: Remove redundant firmware filename override
    https://git.kernel.org/bluetooth/bluetooth-next/c/4988456a75ea
  - [2/2] Bluetooth: btmtksdio: Pass the hardware device id to mt79xx_setup()
    https://git.kernel.org/bluetooth/bluetooth-next/c/afe439f35546

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




      parent reply	other threads:[~2026-08-31 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  3:36 [PATCH 0/2] Bluetooth: btmtksdio: Stop discarding the hardware device id Chris Lu
2026-08-25  3:36 ` [PATCH 1/2] Bluetooth: btmtksdio: Remove redundant firmware filename override Chris Lu
2026-08-25  3:36 ` [PATCH 2/2] Bluetooth: btmtksdio: Pass the hardware device id to mt79xx_setup() Chris Lu
2026-08-31 17:20 ` patchwork-bot+bluetooth [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=178819681225.671757.15863608623551543473.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chris.lu@mediatek.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=sean.wang@mediatek.com \
    --cc=ss.wu@mediatek.com \
    --cc=will-cy.Lee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox