From: Julian Haarmann <julian.haarmann@student.kit.edu>
To: Charles Keepax <ckeepax@opensource.cirrus.com>,
Vinod Koul <vkoul@kernel.org>
Cc: <pierre-louis.bossart@linux.dev>,
<yung-chuan.liao@linux.intel.com>, <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: Thu, 18 Jun 2026 04:25:31 +0200 [thread overview]
Message-ID: <d3d88133651998ec4cee5b831978fe8e4c16b14b.camel@student.kit.edu> (raw)
In-Reply-To: <ai+5CrWRj5lYv4F2@opensource.cirrus.com>
On Mon, 2026-06-15 at 09:34 +0100, Charles Keepax wrote:
> 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
As discussions (https://github.com/thesofproject/linux/issues/5801) are
still ongoing on if this is actually the best way to handle the issue,
I'd hold off on merging right now. I'm adding my signed off anyways
because I'm not the expert here.
Signed-off-by: Julian Haarmann <julian.haarmann@student.kit.edu>
Julian
next prev parent reply other threads:[~2026-06-18 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 16:02 Charles Keepax
2026-06-13 18:15 ` Vinod Koul
2026-06-15 8:34 ` Charles Keepax
2026-06-18 2:25 ` Julian Haarmann [this message]
2026-06-18 8:31 ` Charles Keepax
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=d3d88133651998ec4cee5b831978fe8e4c16b14b.camel@student.kit.edu \
--to=julian.haarmann@student.kit.edu \
--cc=ckeepax@opensource.cirrus.com \
--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
all inboxes | Powered by JetHome®