From: Reaper Li_OC <ReaperLiOC@glenfly.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Jason Tao(SH-RD)" <JasonTao@glenfly.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs.
Date: Wed, 26 Apr 2023 03:30:48 +0000 [thread overview]
Message-ID: <20230426033609.GA18215@sqa-PC> (raw)
In-Reply-To: <875y9kujue.wl-tiwai@suse.de>
> This is almost fine, but could just correct minor warnings
> scripts/checkpatch.pl complains?
Appreciate for your help, have fixed the warnings and resend the v3
patch.
WARNING: multiple messages have this Message-ID (diff)
From: Reaper Li_OC <ReaperLiOC@glenfly.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "perex@perex.cz" <perex@perex.cz>,
"Jason Tao(SH-RD)" <JasonTao@glenfly.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs.
Date: Wed, 26 Apr 2023 03:30:48 +0000 [thread overview]
Message-ID: <20230426033609.GA18215@sqa-PC> (raw)
In-Reply-To: <875y9kujue.wl-tiwai@suse.de>
> This is almost fine, but could just correct minor warnings
> scripts/checkpatch.pl complains?
Appreciate for your help, have fixed the warnings and resend the v3
patch.
next prev parent reply other threads:[~2023-05-01 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 10:15 [PATCH v2] ALSA: hda: Glenfly: add HD Audio PCI IDs and HDMI Codec Vendor IDs Reaper Li
2023-04-25 10:15 ` Reaper Li
2023-04-25 14:17 ` Takashi Iwai
2023-04-25 14:17 ` Takashi Iwai
2023-04-26 3:30 ` Reaper Li_OC [this message]
2023-04-26 3:30 ` Reaper Li_OC
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 10:29 ReaperLi
2023-04-14 12:17 ` Takashi Iwai
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=20230426033609.GA18215@sqa-PC \
--to=reaperlioc@glenfly.com \
--cc=JasonTao@glenfly.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.