From: Joe Perches <email@example.com> To: Jean Delvare <firstname.lastname@example.org> Cc: Andy Whitcroft <email@example.com>, Andrew Morton <firstname.lastname@example.org>, LKML <email@example.com> Subject: Re: [PATCH 0/3] Add missing types to checkpatch.pl --list-types Date: Sat, 02 Sep 2017 15:58:05 -0700 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20170902230315.724835b5@endymion> On Sat, 2017-09-02 at 23:03 +0200, Jean Delvare wrote: > Oh, btw, is there any purpose in listing a number in front of each > type? Not really. I did that because I wanted a header and because I had no idea how many of those types existed and I was too lazy to count. > It makes it look like one can pass that number instead of the > type name, however it doesn't work, and I don't think it should as the > numbering isn't stable and could change with any update of the script. True. > Can't we simplify the output and simply print the list of type names? <shrug> If you want.
next prev parent reply index Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-02 15:51 Jean Delvare 2017-09-02 15:52 ` [PATCH 1/3] checkpatch: fix typo in comment Jean Delvare 2017-09-02 15:53 ` [PATCH 2/3] checkpatch: rename variables to avoid confusion Jean Delvare 2017-09-02 15:56 ` [PATCH 3/3] checkpatch: add 6 missing types to --list-types Jean Delvare 2017-09-02 16:25 ` [PATCH 0/3] Add missing types to checkpatch.pl --list-types Joe Perches 2017-09-02 19:13 ` Jean Delvare 2017-09-02 21:03 ` Jean Delvare 2017-09-02 22:58 ` Joe Perches [this message] 2017-09-04 8:03 ` Jean Delvare
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git git clone --mirror https://lore.kernel.org/lkml/10 lkml/git/10.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ email@example.com public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git