From: Mark Brown <broonie@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Maruthi Srinivas Bayyavarapu
<maruthi.srinivas.bayyavarapu@xilinx.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Vishal Sagar <vsagar@xilinx.com>,
Michal Simek <michal.simek@xilinx.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: xlnx: change license header format style
Date: Wed, 19 Dec 2018 16:24:34 +0000 [thread overview]
Message-ID: <20181219162434.GE8130@sirena.org.uk> (raw)
In-Reply-To: <20181219151704.GA5040@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
On Wed, Dec 19, 2018 at 07:17:04AM -0800, Christoph Hellwig wrote:
> On Wed, Dec 19, 2018 at 03:10:40PM +0530, Maruthi Srinivas Bayyavarapu wrote:
> > Changed License header from C to C++ style comment block.
> Why this completely pointless uglification that goes counter to
> the common style all over the kernel?
I asked for it, when you end up with a C++ comment immediately adjacent
to a C comment block it doesn't exactly look clean and intentional
either.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-19 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 9:40 [PATCH] ASoC: xlnx: change license header format style Maruthi Srinivas Bayyavarapu
2018-12-19 15:17 ` Christoph Hellwig
2018-12-19 16:24 ` Mark Brown [this message]
2018-12-20 16:00 ` Applied "ASoC: xlnx: change license header format style" to the asoc tree Mark Brown
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=20181219162434.GE8130@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=hch@infradead.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maruthi.srinivas.bayyavarapu@xilinx.com \
--cc=michal.simek@xilinx.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=vsagar@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox