From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Takashi Iwai <tiwai@suse.de>, Jason Montleon <jmontleo@redhat.com>
Cc: oder_chiou@realtek.com, cezary.rojewski@intel.com,
ckeepax@opensource.cirrus.com, regressions@lists.linux.dev,
tiwai@suse.com, alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org
Subject: Re: [PATCH v2 1/2] ASoC: rt5514: fix legacy dai naming
Date: Thu, 3 Nov 2022 16:00:15 +0100 [thread overview]
Message-ID: <63521d44-bba4-5795-fd44-fb55b9ced99f@leemhuis.info> (raw)
In-Reply-To: <87iljwmarm.wl-tiwai@suse.de>
On 03.11.22 14:24, Takashi Iwai wrote:
> - Link (or BugLink tag) to pointing to the kernel bugzilla URL
No, not BugLink. To quote Linus from here:
https://lore.kernel.org/all/CAHk-=wgs38ZrfPvy=nOwVkVzjpM3VFU1zobP37Fwd_h9iAD5JQ@mail.gmail.com/
```
> BugLink: https://lore.kernel.org/r/20220610205038.GA3050413@paulmck-ThinkPad-P17-Gen-1
> BugLink: https://lore.kernel.org/r/CAMdYzYpF4FNTBPZsEFeWRuEwSies36QM_As8osPWZSr2q-viEA@mail.gmail.com
[...]
please stop making up random tags that make no sense.
Just use "Link:"
```
Ciao, Thorsten
next prev parent reply other threads:[~2022-11-03 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 20:05 [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Jason Montleon
2022-11-02 22:05 ` Pierre-Louis Bossart
2022-11-03 7:59 ` Takashi Iwai
2022-11-03 9:54 ` Charles Keepax
2022-11-03 11:13 ` Takashi Iwai
2022-11-03 13:11 ` [PATCH v2 1/2] ASoC: rt5514: fix legacy dai naming Jason Montleon
2022-11-03 13:11 ` [PATCH v2 2/2] ASoC: rt5677: " Jason Montleon
2022-11-03 13:19 ` [PATCH v2 1/2] ASoC: rt5514: " Mark Brown
2022-11-03 13:21 ` Takashi Iwai
2022-11-03 13:24 ` Takashi Iwai
2022-11-03 15:00 ` Thorsten Leemhuis [this message]
2022-11-03 13:20 ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Jason Montleon
2022-11-03 11:57 ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression #forregzbot Thorsten Leemhuis
2022-11-05 10:13 ` Thorsten Leemhuis
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=63521d44-bba4-5795-fd44-fb55b9ced99f@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=jmontleo@redhat.com \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).