public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: "Simon Trimmer" <simont@opensource.cirrus.com>
To: "'Mark Brown'" <broonie@kernel.org>
Cc: <linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.cirrus.com>, <Vijendar.Mukunda@amd.com>
Subject: RE: [PATCH] ASoC: amd: ps: Fix missing leading zeros in subsystem_device SSID log
Date: Tue, 31 Mar 2026 12:35:53 +0100	[thread overview]
Message-ID: <005c01dcc102$887470a0$995d51e0$@opensource.cirrus.com> (raw)
In-Reply-To: <3d2bde4e-fb69-4e94-b83f-119f073aba95@sirena.org.uk>

> -----Original Message-----
> From: Mark Brown <broonie@kernel.org>
> Sent: Tuesday, March 31, 2026 12:27 PM
> To: Simon Trimmer <simont@opensource.cirrus.com>
> Cc: linux-sound@vger.kernel.org; linux-kernel@vger.kernel.org;
> patches@opensource.cirrus.com; Vijendar.Mukunda@amd.com
> Subject: Re: [PATCH] ASoC: amd: ps: Fix missing leading zeros in
> subsystem_device SSID log
> 
> On Tue, Mar 31, 2026 at 10:41:16AM +0000, Simon Trimmer wrote:
> > Ensure that subsystem_device is printed with leading zeros when combined
> > with subsystem_vendor to form the SSID. Without this, devices with upper
> > bits unset may appear to have an incorrect SSID in the debug output.
> 
> > Fixes: aab1301cfde344 ("ASoC: amd: ps: Propagate the PCI subsystem
> Vendor and Device IDs")
> 
> Fixes?
> 
> > -			dev_dbg(dev, "SSID %x%x\n", mach-
> >mach_params.subsystem_vendor,
> > +			dev_dbg(dev, "SSID %x%0x\n", mach-
> >mach_params.subsystem_vendor,
> 
> This doesn't specify a width so how would printk know how much to zero
> pad?

Hmm, that's a good point - I'll correct it

Looking at sound/ there's a handful of other log messages making this same
mistake


      reply	other threads:[~2026-03-31 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 10:41 [PATCH] ASoC: amd: ps: Fix missing leading zeros in subsystem_device SSID log Simon Trimmer
2026-03-31 11:26 ` Mark Brown
2026-03-31 11:35   ` Simon Trimmer [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='005c01dcc102$887470a0$995d51e0$@opensource.cirrus.com' \
    --to=simont@opensource.cirrus.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.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