From: Takashi Iwai <tiwai@suse.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Lei Huang <huanglei814@163.com>,
perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, Lei Huang <huanglei@kylinos.cn>
Subject: Re: [PATCH] ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}')
Date: Fri, 10 Apr 2026 09:46:45 +0200 [thread overview]
Message-ID: <87ik9zgsuy.wl-tiwai@suse.de> (raw)
In-Reply-To: <76ff00e6-07a3-4c0b-8906-baa13c077468@kernel.org>
On Fri, 10 Apr 2026 09:41:33 +0200,
Krzysztof Kozlowski wrote:
>
> On 10/04/2026 09:30, Takashi Iwai wrote:
> > On Fri, 10 Apr 2026 09:11:39 +0200,
> > Krzysztof Kozlowski wrote:
> >>
> >> On 01/04/2026 12:43, Krzysztof Kozlowski wrote:
> >>> On 31/03/2026 10:20, Takashi Iwai wrote:
> >>>> On Tue, 31 Mar 2026 09:54:05 +0200,
> >>>> Lei Huang wrote:
> >>>>>
> >>>>> From: Lei Huang <huanglei@kylinos.cn>
> >>>>>
> >>>>> Fix checkpatch code style errors:
> >>>>>
> >>>>> ERROR: else should follow close brace '}'
> >>>>> #2300: FILE: sound/hda/codecs/realtek/alc269.c:2300:
> >>>>> + }
> >>>>> + else
> >>>>>
> >>>>> Fixes: 31278997add6 ("ALSA: hda/realtek - Add headset quirk for Dell DT")
> >>>>> Signed-off-by: Lei Huang <huanglei@kylinos.cn>
> >>>>
> >>>> Thanks, applied to for-next branch.
> >>>
> >>> I hope you dropped the fake Fixes tag. Or at least give people chance to
> >>> review it.
> >>
> >> I see you entirely ignored all the comments about fake bug being fixed here.
> >
> > I saw your comments, but I have a different opinion.
> > In the case of HD-audio code where the code change happens very
> > actively and quite often backported to stable trees, a change like
> > this would block the further backports if missing. With a hint of
>
> No, it would not. Commits marked for backports can even mention
> dependencies.
>
> > Fixes tag, the change of the code change can be tracked more easily,
> > hence it's still worth to have.
>
> Fake fixes tag is not the solution for that. It adds effort on stable
> team for no gain, it adds work on people evaluating backported commits
> for no gain.
It actually helps a lot on distro side, judging from my long
experience of backporting (literally) million of patches for openSUSE
/ SUSE kernels.
> BTW, since I was looking at your tree - you have contributions from
> songxiebing@kylinos.cn which does not follow requirements for a *known
> identity*. IOW, it does not pass DCO requirements and should not be
> accepted.
Do you mean the form
Signed-off-by: songxiebing <songxiebing@kylinos.cn>
?
The name spelling without space is pretty normal in Chinese.
thanks,
Takashi
next prev parent reply other threads:[~2026-04-10 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 7:54 [PATCH] ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') Lei Huang
2026-03-31 8:20 ` Takashi Iwai
2026-04-01 10:43 ` Krzysztof Kozlowski
2026-04-10 7:11 ` Krzysztof Kozlowski
2026-04-10 7:30 ` Takashi Iwai
2026-04-10 7:41 ` Krzysztof Kozlowski
2026-04-10 7:46 ` Takashi Iwai [this message]
2026-04-10 8:03 ` Krzysztof Kozlowski
2026-04-10 8:10 ` Takashi Iwai
2026-04-01 10:42 ` Krzysztof Kozlowski
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=87ik9zgsuy.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=huanglei814@163.com \
--cc=huanglei@kylinos.cn \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 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.