public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
	lee.jones@linaro.org, mturquette@baylibre.com, sboyd@kernel.org,
	linus.walleij@linaro.org, robh+dt@kernel.org,
	mark.rutland@arm.com, lgirdwood@gmail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com, linux-clk@vger.kernel.org,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 4/5] regulator: lochnagar: Add support for the Cirrus Logic Lochnagar
Date: Fri, 19 Oct 2018 13:06:38 +0100	[thread overview]
Message-ID: <20181019120638.GG5895@sirena.org.uk> (raw)
In-Reply-To: <70dcdc5d-73c2-d26f-6228-4bb0bb8ef612@opensource.cirrus.com>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Fri, Oct 19, 2018 at 01:02:45PM +0100, Richard Fitzgerald wrote:

> Most SPDX headers on C files that I've looked at have it this way with a
> C++ style comment above a C-style comment, though some don't. license-rules.rst
> doesn't define how or if a SPDX comment line should be merged with the following
> file header comment. I've had a bunch of patches in different subsystems all
> accepted with this mixed format (copied from existing files). Doing the same as

Right, a lot of the conversions seem to have been done very
mechanically.

> Maybe someone should update license-rules.rst to make a definite statement of the
> style instead of leaving it to become another style that varies across the kernel
> and between files.

Well volunteered!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-10-19 12:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19  9:49 [PATCH v3 1/5] mfd: lochnagar: Add initial binding documentation Charles Keepax
2018-10-19  9:50 ` [PATCH v3 2/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar Charles Keepax
2018-10-19  9:50 ` [PATCH v3 3/5] clk: " Charles Keepax
2018-10-19  9:50 ` [PATCH v3 4/5] regulator: " Charles Keepax
2018-10-19 11:26   ` Mark Brown
2018-10-19 12:02     ` Richard Fitzgerald
2018-10-19 12:06       ` Mark Brown [this message]
2018-10-19 12:19     ` Charles Keepax
2018-10-19 12:21       ` Mark Brown
2018-10-19 12:34         ` Charles Keepax
2018-10-19 12:38           ` Mark Brown
2018-10-19  9:50 ` [PATCH v3 5/5] pinctrl: " Charles Keepax
2018-10-30 13:04   ` Linus Walleij
2018-10-30 13:59     ` Charles Keepax
2018-10-19 18:08 ` [PATCH v3 1/5] mfd: lochnagar: Add initial binding documentation Stephen Boyd
2018-10-30 13:10 ` Linus Walleij

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=20181019120638.GG5895@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    /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