mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: hpp.iscas <hppiscas@163.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	Mark Brown <broonie@kernel.org>,
	"Jaroslav Kysela" <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH] ASoC: Intel: SST: Publish the PCI module aliases
Date: Tue, 8 Sep 2026 19:39:45 +0200	[thread overview]
Message-ID: <b9a15922-e51b-4b37-bead-fda39bfe9bb8@intel.com> (raw)
In-Reply-To: <20260905133133.63661-1-hppiscas@163.com>

On 9/5/2026 3:31 PM, hpp.iscas wrote:
> The legacy SST PCI driver matches Intel Tangier devices using
> 
> intel_sst_ids, but its only explicit module alias is "sst". That alias
> 
> does not match PCI modalias events when this driver is built as a module.
> 
> 
> 
> Publish its PCI table. The independently configurable SOF driver does
> 
> not provide aliases for the legacy SST module.
> 
> 
> 
> Fixes: f533a035e4da ("ASoC: Intel: mrfld - create separate module for pci part")
> 
> Signed-off-by: hpp.iscas <hppiscas@163.com>
At least on my side the entire patch is weirdly spaced. Also, I'd expect
'Name Surname <email>' format in the Signed-off-by tag. "hpp.iscas"
looks more like a nickname.

Kind regards,
Czarek

      parent reply	other threads:[~2026-09-08 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 13:31 hpp.iscas
2026-09-07 16:49 ` Mark Brown
2026-09-08 17:39 ` Cezary Rojewski [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=b9a15922-e51b-4b37-bead-fda39bfe9bb8@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=broonie@kernel.org \
    --cc=hppiscas@163.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=tiwai@suse.com \
    --cc=vkoul@kernel.org \
    --cc=yung-chuan.liao@linux.intel.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

all inboxes | Powered by JetHome®