All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sommer, Roman" <roman.sommer@fau.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@i4.cs.fau.de, "Daniel Graefe" <daniel.graefe@fau.de>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Takashi Sakamoto" <o-takashi@sakamocchi.jp>,
	"Hans P. Möller Ebner" <hmoller@uc.cl>,
	"Kees Cook" <keescook@chromium.org>,
	"Kate Stewart" <kstewart@linuxfoundation.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Fabián Inostroza" <soulsonceonfire@gmail.com>,
	"Bhumika Goyal" <bhumirks@gmail.com>,
	"Philippe Ombredanne" <pombredanne@nexb.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] sound/line6: checkpatch: fix block comment style
Date: Mon, 18 Jun 2018 13:56:42 +0200	[thread overview]
Message-ID: <6dd9eb6c3dc6d57eb140696bed4e4a6c@fau.de> (raw)
In-Reply-To: <20180618112134.GA4289@kroah.com>

On 2018-06-18 13:21, Greg Kroah-Hartman wrote:
> On Mon, Jun 18, 2018 at 12:29:37PM +0200, Roman Sommer wrote:
>> CC: Jaroslav Kysela <perex@perex.cz>
>> CC: Takashi Iwai <tiwai@suse.com>
>> CC: Takashi Sakamoto <o-takashi@sakamocchi.jp>
>> CC: "Hans P. Möller Ebner" <hmoller@uc.cl>
>> CC: Kees Cook <keescook@chromium.org>
>> CC: Kate Stewart <kstewart@linuxfoundation.org>
>> CC: Thomas Gleixner <tglx@linutronix.de>
>> CC: "Fabián Inostroza" <soulsonceonfire@gmail.com>
>> CC: Bhumika Goyal <bhumirks@gmail.com>
>> CC: Philippe Ombredanne <pombredanne@nexb.com>
>> CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> CC: alsa-devel@alsa-project.org
>> CC: linux-kernel@vger.kernel.org
>> 
>> This patch fixed the style of multiline comments in sound/usb/line6.
> 
> Why is all of those cc: lines in the changelog body?
> 
> Very odd...
> 
> greg k-h

Hi Greg,

Sorry for the mess-up here, they were meant for the header only.

I used a newline to group people in the patches which I now know I 
should
not do.


Roman

  reply	other threads:[~2018-06-18 12:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 10:29 [PATCH 0/3] sound/usb/line6: fix some styling issues Roman Sommer
2018-06-18 10:29 ` Roman Sommer
2018-06-18 10:29 ` [PATCH 1/3] sound/line6: checkpatch: fix block comment style Roman Sommer
2018-06-18 10:29   ` Roman Sommer
2018-06-18 11:21   ` Greg Kroah-Hartman
2018-06-18 11:21     ` Greg Kroah-Hartman
2018-06-18 11:56     ` Sommer, Roman [this message]
2018-06-18 10:29 ` [PATCH 2/3] sound/line6: unsigned -> unsigned int Roman Sommer
2018-06-18 10:29   ` Roman Sommer
2018-06-18 10:29 ` [PATCH 3/3] sound/line6: add newline after declarations Roman Sommer
2018-06-18 10:29   ` Roman Sommer
2018-06-18 10:39 ` [PATCH 0/3] sound/usb/line6: fix some styling issues Takashi Iwai
2018-06-18 11:57   ` Sommer, Roman
2018-06-18 12:04     ` 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=6dd9eb6c3dc6d57eb140696bed4e4a6c@fau.de \
    --to=roman.sommer@fau.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhumirks@gmail.com \
    --cc=daniel.graefe@fau.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hmoller@uc.cl \
    --cc=keescook@chromium.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=perex@perex.cz \
    --cc=pombredanne@nexb.com \
    --cc=soulsonceonfire@gmail.com \
    --cc=tglx@linutronix.de \
    --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.