Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: pierre-louis.bossart@linux.dev, yung-chuan.liao@linux.intel.com,
	julian.haarmann@student.kit.edu, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] soundwire: dmi-quirks: Disable ghost device on Lenovo Yoga 9i
Date: Mon, 15 Jun 2026 09:34:18 +0100	[thread overview]
Message-ID: <ai+5CrWRj5lYv4F2@opensource.cirrus.com> (raw)
In-Reply-To: <ai2eWeTlhFtNWpr9@vaman>

On Sat, Jun 13, 2026 at 11:45:53PM +0530, Vinod Koul wrote:
> On 08-06-26, 17:02, Charles Keepax wrote:
> > There is also a "non-pro" version of the Lenovo Yoga 9i (83SE) which
> > also needs a quirk to disable a non-existent Realtek device. Add this
> > missing quirk.
> > 
> > Co-developed-by: Julian Haarmann <julian.haarmann@student.kit.edu>
> 
> Need sob by Julian.
> 
>  - Co-developed-by: states that the patch was co-created by several developers;
>    it is a used to give attribution to co-authors (in addition to the author
>    attributed by the From: tag) when multiple people work on a single patch.
>    Every Co-developed-by: must be immediately followed by a Signed-off-by: of
>    the associated co-author.

Julian, I assume your happy with me adding your signed off by?

Thanks,
Charles

      reply	other threads:[~2026-06-15  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 16:02 [PATCH] soundwire: dmi-quirks: Disable ghost device on Lenovo Yoga 9i Charles Keepax
2026-06-13 18:15 ` Vinod Koul
2026-06-15  8:34   ` Charles Keepax [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=ai+5CrWRj5lYv4F2@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=julian.haarmann@student.kit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=pierre-louis.bossart@linux.dev \
    --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