From: Paulo Alcantara <pc@manguebit.com>
To: "Dr. David Alan Gilbert" <linux@treblig.org>,
Tom Talpey <tom@talpey.com>
Cc: Dave Kleikamp <dave.kleikamp@oracle.com>,
Steve French <smfrench@gmail.com>,
linkinjeon@kernel.org, shaggy@kernel.org,
linux-cifs@vger.kernel.org, krisman@collabora.com,
jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] dedupe smb unicode files
Date: Fri, 21 Jul 2023 18:06:57 -0300 [thread overview]
Message-ID: <16f50dff126af9b20f9b99ca056ad5fa.pc@manguebit.com> (raw)
In-Reply-To: <ZLrxYzGXJzsLmGDs@gallifrey>
"Dr. David Alan Gilbert" <linux@treblig.org> writes:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/checkpatch.pl#n3737
> if ($realfile =~ /\.(h|s|S)$/) {
> $comment = '/*';
> } elsif ($realfile =~ /\.(c|rs|dts|dtsi)$/) {
> $comment = '//';
>
> I don't get where that idea came from.
Check Documentation/process/license-rules.rst.
next prev parent reply other threads:[~2023-07-21 21:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 23:24 [PATCH v2 0/4] dedupe smb unicode files linux
2023-06-28 23:24 ` [PATCH v2 1/4] fs/smb: Remove unicode 'lower' tables linux
2023-06-28 23:24 ` [PATCH v2 2/4] fs/smb: Swing unicode common code from smb->NLS linux
2023-06-28 23:24 ` [PATCH v2 3/4] fs/smb/client: Use common code in client linux
2023-06-28 23:24 ` [PATCH v2 4/4] fs/jfs: Use common ucs2 upper case table linux
2023-07-12 23:17 ` [PATCH v2 0/4] dedupe smb unicode files Dr. David Alan Gilbert
2023-07-19 17:56 ` Steve French
2023-07-19 18:02 ` Steve French
2023-07-19 21:58 ` Dr. David Alan Gilbert
2023-07-19 22:06 ` Dave Kleikamp
2023-07-20 14:25 ` Tom Talpey
2023-07-20 23:57 ` Dr. David Alan Gilbert
2023-07-21 13:19 ` Tom Talpey
2023-07-21 13:25 ` Dr. David Alan Gilbert
2023-07-21 20:58 ` Dr. David Alan Gilbert
2023-07-21 21:06 ` Paulo Alcantara [this message]
2023-07-21 21:12 ` Tom Talpey
2023-07-21 21:12 ` Dr. David Alan Gilbert
2023-08-13 0:57 ` Dr. David Alan Gilbert
2023-08-13 3:11 ` Steve French
2023-08-27 23:14 ` Steve French
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=16f50dff126af9b20f9b99ca056ad5fa.pc@manguebit.com \
--to=pc@manguebit.com \
--cc=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=krisman@collabora.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=shaggy@kernel.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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