All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:10:32 +0200	[thread overview]
Message-ID: <877bqfgrrb.wl-tiwai@suse.de> (raw)
In-Reply-To: <6fdc548e-34c5-44ab-8e4e-6d58ea6b07a8@kernel.org>

On Fri, 10 Apr 2026 10:03:12 +0200,
Krzysztof Kozlowski wrote:
> 
> On 10/04/2026 09:46, Takashi Iwai wrote:
> > 
> > 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.
> 
> It is a copy of email username.

... and the username shows the real name in this case :)

> I am no expert, but usually Latin
> transliterations have differences from usernames (and Google confirms
> that space is expected for transliteration, although Google is no expert
> either), so this looks like semi-configured Git.

Yeah, it's possible, but also it's a common pattern, too.

Strictly speaking, it's rather a mistake, and I'm no fan of that
style, too.  OTOH, since it's relatively broadly used and can serve
for denoting the known identity, at least, I took as is.


thanks,

Takashi

  reply	other threads:[~2026-04-10  8:10 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
2026-04-10  8:03             ` Krzysztof Kozlowski
2026-04-10  8:10               ` Takashi Iwai [this message]
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=877bqfgrrb.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.