public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Jeremy Dean <deaner92@yahoo.com>,
	linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Von Dentz <luiz.dentz@gmail.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bluetooth: Remove unnecessary braces around single line statement
Date: Mon, 27 Jan 2025 17:17:20 +0100	[thread overview]
Message-ID: <452f118f-2a0d-4b54-9285-063ccbe6e5ab@web.de> (raw)
In-Reply-To: <Z5aMrXwnmEXxKWkC@vmi2410184.contaboserver.net>

> I have changed the subject.
>
> Fixes: Coding style, unnecessary braces

See also once more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.13#n145

Is such a tag really relevant for a coding style adjustment?


https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22

Regards,
Markus

  reply	other threads:[~2025-01-27 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250125165804.11486-1-deaner92.ref@yahoo.com>
2025-01-25 16:58 ` [PATCH] Bluetooth: Unnecessary braces around single line statment deaner92
2025-01-25 18:33   ` bluez.test.bot
2025-01-26  8:02   ` [PATCH] " Paul Menzel
2025-01-26 19:27     ` [PATCH] Bluetooth: Remove unnecessary braces around single line statement Jeremy Dean
2025-01-27 16:17       ` Markus Elfring [this message]
2025-01-27 21:30         ` Jeremy Dean
2025-01-27 21:38           ` Luiz Augusto von Dentz
2025-01-27 21:52             ` Jeremy Dean
2025-01-27 22:02               ` Luiz Augusto von Dentz
2025-01-28  6:09                 ` Jeremy Dean
2025-01-29 20:20   ` [PATCH] Bluetooth: Unnecessary braces around single line statment patchwork-bot+bluetooth
2025-01-27 22:10 [PATCH] Bluetooth: Remove unnecessary braces around single line statement deaner92
2025-01-27 22:31 ` bluez.test.bot
2025-01-28 19:45   ` Jeremy Dean

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=452f118f-2a0d-4b54-9285-063ccbe6e5ab@web.de \
    --to=markus.elfring@web.de \
    --cc=deaner92@yahoo.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.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