From: Christoph Hellwig <hch@infradead.org>
To: Nishad Kamdar <nishadkamdar@gmail.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Joe Perches" <joe@perches.com>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Use the correct style for SPDX License Identifier
Date: Mon, 27 Apr 2020 00:25:27 -0700 [thread overview]
Message-ID: <20200427072527.GA3019@infradead.org> (raw)
In-Reply-To: <20200425133504.GA11354@nishad>
On Sat, Apr 25, 2020 at 07:05:09PM +0530, Nishad Kamdar wrote:
> This patch corrects the SPDX License Identifier style in
> header files related to XFS File System support.
> For C header files Documentation/process/license-rules.rst
> mandates C-like comments (opposed to C source files where
> C++ style should be used).
>
> Changes made by using a script provided by Joe Perches here:
> https://lkml.org/lkml/2019/2/7/46.
Please use up all 73 chars in your commit logs.
next prev parent reply other threads:[~2020-04-27 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 13:35 [PATCH] xfs: Use the correct style for SPDX License Identifier Nishad Kamdar
2020-04-27 7:25 ` Christoph Hellwig [this message]
2020-05-02 8:57 ` Nishad Kamdar
2020-04-27 15:56 ` Darrick J. Wong
2020-04-27 17:29 ` Greg Kroah-Hartman
2020-04-27 17:41 ` Joe Perches
2020-04-27 17:46 ` Greg Kroah-Hartman
2020-04-27 18:01 ` Joe Perches
2020-04-27 18:36 ` Greg Kroah-Hartman
2020-04-27 18:59 ` Joe Perches
2020-04-27 19:40 ` Linus Torvalds
2020-04-27 20:38 ` Joe Perches
2020-04-27 20:46 ` Linus Torvalds
2020-04-29 0:20 ` Joe Perches
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=20200427072527.GA3019@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nishadkamdar@gmail.com \
--cc=u.kleine-koenig@pengutronix.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 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.