Re: [PATCH v5 0/2] checkpatch: add verbose mode

2021-02-20 Thread Joe Perches
On Sat, 2021-02-20 at 17:32 +0530, Dwaipayan Ray wrote: > Add a new verbose mode to checkpatch. The verbose test > descriptions are read from the checkpatch documentation > file at `Documentation/dev-tools/checkpatch.rst`. > > The verbose mode is optional and can be enabled by the > flag -v or

Re: [PATCH v4 2/2] docs: add documentation for checkpatch

2021-02-19 Thread Joe Perches
On Wed, 2021-02-17 at 22:24 +0530, Dwaipayan Ray wrote: > Add documentation for kernel script checkpatch.pl. > This documentation is also parsed by checkpatch to > enable a verbose mode. > > The checkpatch message types are grouped by usage. Under > each group the types are described briefly. 34

Re: [PATCH v4 1/2] checkpatch: add verbose mode

2021-02-19 Thread Joe Perches
On Wed, 2021-02-17 at 22:24 +0530, Dwaipayan Ray wrote: > Add a new verbose mode to checkpatch.pl to emit additional verbose > test descriptions. The verbose mode is optional and can be enabled > by the flag -v or --verbose. [] > The verbose descriptions are not shown when the --terse option > is

Re: [PATCH RFC v3 2/3] docs: add documentation for checkpatch

2021-02-17 Thread Joe Perches
On Tue, 2021-02-16 at 19:48 +0530, Dwaipayan Ray wrote: > On Sun, Feb 14, 2021 at 10:27 PM Joe Perches wrote: > > On Sat, 2021-02-13 at 18:45 +0530, Dwaipayan Ray wrote: > > > Add documentation for kernel script checkpatch.pl. > > > This documentation is also parsed by

Re: [PATCH 02/29] alpha: Avoid comma separated statements

2021-02-16 Thread Joe Perches
On Tue, 2021-02-16 at 15:39 +0100, Robert Richter wrote: > On 30.01.21 10:54:42, Joe Perches wrote: > > On Mon, 2020-08-24 at 21:55 -0700, Joe Perches wrote: > > > Use semicolons and braces. > > > > ping? > > > > > > > > Signed-off-by: Joe P

Re: [PATCH RFC v3 2/3] docs: add documentation for checkpatch

2021-02-15 Thread Joe Perches
On Sun, 2021-02-14 at 12:15 +, Matthew Wilcox wrote: > On Sat, Feb 13, 2021 at 06:45:12PM +0530, Dwaipayan Ray wrote: > > +Checkpatch (scripts/checkpatch.pl) is a perl script which checks for > > trivial style > > It's quite amusing that this patch contains lines > 80 columns. Then you

Re: [PATCH RFC v3 2/3] docs: add documentation for checkpatch

2021-02-15 Thread Joe Perches
On Mon, 2021-02-15 at 21:20 +0530, Dwaipayan Ray wrote: > Also someone pointed out in the list that some lines in the patch contained > > 80 > columns. Checkpatch doesn't generate any warning for that. Is it something > that > could be added to checkpatch or was it decided against at some

Re: [PATCH RFC v3 2/3] docs: add documentation for checkpatch

2021-02-14 Thread Joe Perches
On Sat, 2021-02-13 at 18:45 +0530, Dwaipayan Ray wrote: > Add documentation for kernel script checkpatch.pl. > This documentation is also parsed by checkpatch to > enable a verbose mode. > > The message types in checkpatch are documented with rst > field lists. A total of 33 checkpatch type

Re: [PATCH] proc: Convert S_ permission uses to octal

2021-02-12 Thread Joe Perches
On Fri, 2021-02-12 at 17:48 -0600, Eric W. Biederman wrote: > Matthew Wilcox writes: > > On Fri, Feb 12, 2021 at 04:01:48PM -0600, Eric W. Biederman wrote: > > > Perhaps we can do something like: > > > > > > #define S_IRWX 7 > > > #define S_IRW_ 6 > > > #define S_IR_X 5 > > > #define S_IR__ 4 >

Re: [PATCH] proc: Convert S_ permission uses to octal

2021-02-12 Thread Joe Perches
On Fri, 2021-02-12 at 17:44 -0600, Eric W. Biederman wrote: > I certainly do not see sufficient consensus to go around changing code > other people maintain. Every patch by a non-maintainer that doesn't have commit rights to whatever tree is just a proposal. > My suggest has the nice property

[PATCH] mm: Reduce mem_dump_obj() object size

2021-02-12 Thread Joe Perches
372 4078891ed1 mm/util.o.old Signed-off-by: Joe Perches --- mm/util.c | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/mm/util.c b/mm/util.c index c37e24d5fa43..143c627fb3e8 100644 --- a/mm/util.c +++ b/mm/util.c @@ -997,22 +997,26 @@ int

Re: [PATCH] proc: Convert S_ permission uses to octal

2021-02-12 Thread Joe Perches
On Fri, 2021-02-12 at 16:01 -0600, Eric W. Biederman wrote: > Joe Perches writes: > > > Convert S_ permissions to the more readable octal. > > > > Done using: > > $ ./scripts/checkpatch.pl -f --fix-inplace --types=SYMBOLIC_PERMS > > fs/proc/*.[ch] > >

[PATCH] drm: Convert S_ permission uses to octal

2021-02-12 Thread Joe Perches
files is usually an error. Consider more restrictive permissions. #688: FILE: drivers/gpu/drm/msm/adreno/a5xx_debugfs.c:157: + debugfs_create_file("reset", 0222, minor->debugfs_root, dev, _fops); Signed-off-by: Joe Perches --- drivers/gpu/drm/amd/

[PATCH] proc: Convert S_ permission uses to octal

2021-02-12 Thread Joe Perches
...@mail.gmail.com/ Signed-off-by: Joe Perches --- fs/proc/base.c| 216 +- fs/proc/fd.c | 6 +- fs/proc/generic.c | 8 +- fs/proc/kcore.c | 2 +- fs/proc/kmsg.c| 2 +- fs/proc/namespaces.c | 2 +- fs/proc/nommu.c

Re: [PATCH] drm/msm/dp: Add a missing semi-colon

2021-02-12 Thread Joe Perches
On Mon, 2021-02-08 at 10:57 -0800, Stephen Boyd wrote: > Quoting Joe Perches (2021-02-06 21:06:54) > > Wow, that's really unfortunate that dp_panel_update_tu_timings > > is also void. > > > > Perhaps this as YA checkpatch warning: > > > > --- >

Re: [PATCH v4 1/2] pinctrl: use to octal permissions for debugfs files

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 14:28 -0800, Drew Fustini wrote: > Switch over pinctrl debugfs files to use octal permissions as they are > preferred over symbolic permissions. Refer to commit f90774e1fd27 > ("checkpatch: look for symbolic permissions and suggest octal instead"). > > Note: S_IFREG flag is

Re: [PATCH v4 2/2] pinctrl: pinmux: Add pinmux-select debugfs file

2021-02-10 Thread Joe Perches
On Thu, 2021-02-11 at 10:11 +0300, Dan Carpenter wrote: > On Wed, Feb 10, 2021 at 02:28:54PM -0800, Drew Fustini wrote: > > + ret = strncpy_from_user(buf, user_buf, PINMUX_MAX_NAME * 2); > > + if (ret < 0) { > > + dev_err(pctldev->dev, "failed to copy buffer from userspace"); > > +

Re: [PATCH] Documentation: Replace more lkml.org links with lore

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 15:40 -0800, Kees Cook wrote: > As started by commit 05a5f51ca566 ("Documentation: Replace lkml.org > links with lore"), replace a few more scattered lkml.org links with > lore to better use a single source that's more likely to stay available > long-term. The subject title

Re: [PATCH v2 1/2] pinctrl: use to octal permissions for debugfs files

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 13:21 -0800, Drew Fustini wrote: > I will change from the incorrect 0400 to 0444. Thanks. > As for S_IFREG, it does seem like leaving off S_IFREG is the most common > case when using octal permissions with debugfs_create_*(): > > $ git grep debugfs_create drivers/ |grep

Re: [PATCH v4 3/3] vsprintf: dump full information of page flags in pGp

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 13:51 +0100, Petr Mladek wrote: > On Wed 2021-02-10 00:21:37, Yafang Shao wrote: > > On Tue, Feb 9, 2021 at 9:53 PM Petr Mladek wrote: [] > >  for (p = pff; p < pff + ARRAY_SIZE(pff); p++) { > > This looks a bit non-standard. IMHO, Joe was not against using index. > He

Re: [PATCH 2/2] checkpatch: Don't check for mutex_trylock_recursive()

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 09:52 +0100, Sebastian Andrzej Siewior wrote: > mutex_trylock_recursive() has been removed from the tree, there is no > need to check for it. > > Remove traces of mutex_trylock_recursive()'s existence. Yay. Assuming patch 1 is applied, thanks. > > Signed-off-by:

Re: [PATCH v2 1/2] pinctrl: use to octal permissions for debugfs files

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 12:18 +0200, Andy Shevchenko wrote: > On Wed, Feb 10, 2021 at 10:30 AM Joe Perches wrote: > > On Tue, 2021-02-09 at 23:49 -0800, Drew Fustini wrote: > > > > - debugfs_create_file("pinctrl-devices", S_IFREG | S_IRUGO, > > > +

Re: [PATCH v2 1/2] pinctrl: use to octal permissions for debugfs files

2021-02-10 Thread Joe Perches
On Tue, 2021-02-09 at 23:49 -0800, Drew Fustini wrote: > Switch over pinctrl debugfs files to use octal permissions as they are > preferred over symbolic permissions. Refer to commit f90774e1fd27 > ("checkpatch: look for symbolic permissions and suggest octal instead"). > > Signed-off-by: Drew

Re: [PATCH] MAINTAINERS: replace non-matching patterns for loongson{2,3}

2021-02-10 Thread Joe Perches
On Wed, 2021-02-10 at 08:59 +0100, Lukas Bulwahn wrote: > Commit ffe1f9356fbe ("MAINTAINERS: Add Loongson-2/Loongson-3 maintainers") > adds quite generic file entries for drivers/*/*loongson{2,3}* and > drivers/*/*/*loongson{2,3}* to be informed on changes to all loongson{2,3} > files in drivers.

Re: [PATCH] Documentation: Replace lkml.org links with lore

2021-02-09 Thread Joe Perches
On Tue, 2021-02-09 at 23:28 -0800, Kees Cook wrote: > On Sun, Jan 10, 2021 at 12:41:44PM -0800, Joe Perches wrote: > > Replace the lkml.org links with lore to better use a single source > > that's more likely to stay available long-term. > > What's the best way to teach che

Re: [PATCH v4] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-09 Thread Joe Perches
On Wed, 2021-02-10 at 04:07 +, Song Liu wrote: > > On Feb 9, 2021, at 6:10 PM, Joe Perches wrote: > > On Tue, 2021-02-09 at 13:19 -0800, Song Liu wrote: > > > BPF programs explicitly initialise global variables to 0 to make sure > > > clang (v10 or o

Re: [PATCH v4] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-09 Thread Joe Perches
On Tue, 2021-02-09 at 13:19 -0800, Song Liu wrote: > BPF programs explicitly initialise global variables to 0 to make sure > clang (v10 or older) do not put the variables in the common section. Acked-by: Joe Perches So the patch is OK now, but I have a question about the concept: Do yo

Re: [PATCH v3] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-09 Thread Joe Perches
On Tue, 2021-02-09 at 19:44 +, Song Liu wrote: > > On Feb 9, 2021, at 10:59 AM, Joe Perches wrote: > > On Tue, 2021-02-09 at 10:33 -0800, Song Liu wrote: > > > BPF programs explicitly initialise global variables to 0 to make sure > > > clang (v10 or o

Re: [PATCH v3] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-09 Thread Joe Perches
ror > messages like: > > ERROR: do not initialise globals to 0 > #19: FILE: samples/bpf/tracex1_kern.c:21: > > Cc: Andy Whitcroft > Cc: Joe Perches > Signed-off-by: Song Liu > > --- > Changes v2 => v3: >   1. Fix regex. Unfortunately, this has

Re: [PATCH v2] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-09 Thread Joe Perches
ror > messages like: > > ERROR: do not initialise globals to 0 > #19: FILE: samples/bpf/tracex1_kern.c:21: > > Cc: Andy Whitcroft > Cc: Joe Perches > Signed-off-by: Song Liu > > --- > Changes v1 => v2: >   1. Add function exclude_global_initialisers() to kee

Re: [PATCH] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-08 Thread Joe Perches
On Mon, 2021-02-08 at 15:40 -0800, Song Liu wrote: > BPF programs explicitly initialise global variables to 0 to make sure > clang (v10 or older) do not put the variables in the common section. > Skip "initialise globals to 0" check for BPF programs to elimiate error > messages like: > >

Re: [PATCH] checkpatch: do not apply "initialise globals to 0" check to BPF progs

2021-02-08 Thread Joe Perches
On Mon, 2021-02-08 at 15:40 -0800, Song Liu wrote: > BPF programs explicitly initialise global variables to 0 to make sure > clang (v10 or older) do not put the variables in the common section. > Skip "initialise globals to 0" check for BPF programs to elimiate error > messages like: > >

Re: [PATCH v1 2/2] ACPI: OSL: Clean up printing messages

2021-02-08 Thread Joe Perches
On Mon, 2021-02-08 at 19:59 +0100, Rafael J. Wysocki wrote: > Replace the ACPI_DEBUG_PRINT() instance in osl.c unrelated to the > ACPICA debug with acpi_handle_debug(), add a pr_fmt() definition > to osl.c and replace direct printk() usage in that file with the > suitable pr_*() calls. [] >

Re: [PATCH] staging: gasket: fix indentation and lines ending with open parenthesis

2021-02-07 Thread Joe Perches
On Sun, 2021-02-07 at 19:39 +0530, Mahak Gupta wrote: > This patch fixes warnings of 'checkpatch.pl'. According to > Linux coding guidelines, code should be aligned properly to > match with open parenthesis and lines should not end with > open parenthesis. Perhaps try using temporaries to reduce

Re: [PATCH] staging: gasket: fix indentation and lines ending with open parenthesis

2021-02-07 Thread Joe Perches
On Sun, 2021-02-07 at 19:39 +0530, Mahak Gupta wrote: > This patch fixes warnings of 'checkpatch.pl'. According to > Linux coding guidelines, code should be aligned properly to > match with open parenthesis and lines should not end with > open parenthesis. > > Signed-off-by: Mahak Gupta > --- >  

Re: [PATCH] staging: octeon: convert all uses of strlcpy to strscpy in ethernet-mdio.c

2021-02-07 Thread Joe Perches
On Sun, 2021-02-07 at 15:55 +0100, Greg KH wrote: > On Sun, Feb 07, 2021 at 02:48:04PM +, Phillip Potter wrote: > > Convert three calls to strlcpy inside the cvm_oct_get_drvinfo function > > to strscpy calls. Fixes a style warning. > > Is it really safe to do this type of conversion here?

Re: [PATCH] printk: Userspace format enumeration support

2021-02-07 Thread Joe Perches
On Sun, 2021-02-07 at 14:13 +, Chris Down wrote: > Joe Perches writes: > > > There are certainly printks which can't be trivially monitored using the > > > printk > > > format alone, but the vast majority of the ones that are monitored _do_ > > >

Re: [PATCH] I was wondering why I can't set the resolution to 2560x1080, while in windows 7 I can without a problem. I looked at the radeon driver code and found it doesn't support this resolution. So

2021-02-07 Thread Joe Perches
Your subject needs to be changed and a commit log added. > diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c > b/drivers/gpu/drm/radeon/radeon_connectors.c [] > @@ -37,6 +37,8 @@ >  #include >  #include > > +extern int hdmimhz; > + >  static int radeon_dp_handle_hpd(struct drm_connector

Re: [PATCH] drm/msm/dp: Add a missing semi-colon

2021-02-06 Thread Joe Perches
On Sat, 2021-02-06 at 20:18 -0800, Stephen Boyd wrote: > A missing semicolon here causes my external display to stop working. > Indeed, missing the semicolon on the return statement leads to > dp_panel_update_tu_timings() not existing because the compiler thinks > it's part of the return statement

Re: [PATCH] printk: Userspace format enumeration support

2021-02-06 Thread Joe Perches
On Sat, 2021-02-06 at 21:21 +, Chris Down wrote: > Joe Perches writes: > > On Fri, 2021-02-05 at 22:25 +, Chris Down wrote: > > > Petr Mladek writes: > > > >   + is already optinaly added by pr_fmt() to the printed > > > > strings > >

Re: [PATCH] printk: Userspace format enumeration support

2021-02-06 Thread Joe Perches
On Fri, 2021-02-05 at 22:25 +, Chris Down wrote: > Petr Mladek writes: > >   + is already optinaly added by pr_fmt() to the printed strings > > as: pr_fmt(): ... > > pr_fmts are not consistently used across the kernel, and sometimes differ > from > the module itself. Many modules

Re: [PATCH] checkpatch: Don't warn about colon termination in linker scripts

2021-02-06 Thread Joe Perches
On Sat, 2021-02-06 at 13:04 +, Chris Down wrote: > Oh, apologies -- I was somehow operating under the mistaken memory that this > was under Andrew's purview and neglected to run get_maintainer. > > I'll resend. :-) No need really. The patch is fine.

Re: [PATCH] checkpatch: Don't warn about colon termination in linker scripts

2021-02-05 Thread Joe Perches
On Thu, 2021-02-04 at 16:32 +, Chris Down wrote: > This check erroneously flags cases like the one in my recent printk > enumeration patch[0], where the spaces are syntactic, and `section:' vs. > `section :' is syntactically important: > > ERROR: space prohibited before that ':' (ctx:WxW)

Re: Small student project idea on appropriate integration trees in MAINTAINERS

2021-02-05 Thread Joe Perches
On Fri, 2021-02-05 at 07:42 +0100, Lukas Bulwahn wrote: > On Fri, Jan 29, 2021 at 12:54 AM Jonathan Corbet wrote: > > > > On Fri, 22 Jan 2021 09:22:24 +0100 > > Lukas Bulwahn wrote: > > > > > In this project, we can make use of: > > > > > > - gitdm [git://git.lwn.net/gitdm.git]: gitdm

Re: [PATCH v2 2/3] fs/efs: Correct spacing after C keywords

2021-02-04 Thread Joe Perches
On Thu, 2021-02-04 at 21:14 -0800, Amy Parker wrote: > In EFS code, some C keywords (most commonly 'for') do not have spaces > before their instructions, such as for() vs for (). The kernel style > guide indicates that these should be of the latter variant. This patch > updates them

Re: [PATCH v2 1/3] fs/efs: Use correct brace styling for statements

2021-02-04 Thread Joe Perches
On Thu, 2021-02-04 at 21:14 -0800, Amy Parker wrote: > Many single-line statements have unnecessary braces, and some statement > pairs have mismatched braces. This is a clear violation of the kernel > style guide, which mandates that single line statements have no braces > and that pairs with

Re: [PATCH] ceph: minor coding style tweaks

2021-02-03 Thread Joe Perches
On Thu, 2021-02-04 at 14:32 +0800, Zhiyuan Dai wrote: > Fixed some coding style issues, improve code reading. Might describe the patch does 3 things: o Move the pointer location struct foo* bar; -> struct foo *bar; o Move brace position from struct foo { to

Re: [PATCH] firewire: convert sysfs sprintf/snprintf family to sysfs_emit

2021-02-03 Thread Joe Perches
On Thu, 2021-02-04 at 14:50 +0800, Jiapeng Chong wrote: > Fix the following coccicheck warning: > > ./drivers/firewire/core-device.c:375:8-16: WARNING: use scnprintf or > sprintf. [] > diff --git a/drivers/firewire/core-device.c b/drivers/firewire/core-device.c [] > @@ -372,8 +372,7 @@ static

Re: [PATCH v1 2/5] ACPI: battery: Clean up printing messages

2021-02-02 Thread Joe Perches
On Mon, 2021-02-01 at 19:44 +0100, Rafael J. Wysocki wrote: > On Mon, Feb 1, 2021 at 7:37 PM Joe Perches wrote: > > > > On Mon, 2021-02-01 at 19:16 +0100, Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > > > Replace the ACPI_DE

Re: [PATCH 2/3] printk: hard-code CONSOLE_LOGLEVEL_MIN in printk.c

2021-02-02 Thread Joe Perches
On Tue, 2021-02-02 at 19:06 +0900, Sergey Senozhatsky wrote: > On (21/02/02 16:02), Masahiro Yamada wrote: > >  include/linux/printk.h | 1 - > >  kernel/printk/printk.c | 2 +- > >  2 files changed, 1 insertion(+), 2 deletions(-) > > > > diff --git a/include/linux/printk.h b/include/linux/printk.h

Re: [Linux-kernel-mentees] Patches from the future - can checkpatch help?

2021-02-02 Thread Joe Perches
On Mon, 2021-02-01 at 22:41 +0530, Dwaipayan Ray wrote: > The idea of a bot seems nice though in general. > People do have all the style checking scripts at their disposal, but still > we see style issues on the list. > > Something similar to the kernel test robot, but for style issues seems

Re: [PATCH v2 3/3] vsprintf: dump full information of page flags in pGp

2021-02-01 Thread Joe Perches
On Mon, 2021-02-01 at 14:15 +, Matthew Wilcox wrote: > On Mon, Feb 01, 2021 at 07:56:10PM +0800, Yafang Shao wrote: > > - Before the patch, > > [ 6343.396602] Slab 0x4382e02b objects=33 used=3 > > fp=0x9ae06ffc flags=0x17c0010200(slab|head) > > > > - After the patch, > >

Re: [PATCH v1 2/5] ACPI: battery: Clean up printing messages

2021-02-01 Thread Joe Perches
On Mon, 2021-02-01 at 19:16 +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Replace the ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() instances > in battery.c with acpi_handle_debug() and acpi_handle_info() calls, > respectively, drop the _COMPONENT and ACPI_MODULE_NAME() definitions >

Re: [PATCH v2 3/3] vsprintf: dump full information of page flags in pGp

2021-02-01 Thread Joe Perches
On Mon, 2021-02-01 at 19:56 +0800, Yafang Shao wrote: > Currently the pGp only shows the names of page flags, rather than > the full information including section, node, zone, last cpupid and > kasan tag. While it is not easy to parse these information manually > because there're so many flavors.

Re: [PATCH] Staging: wimax: i2400m: fixing several coding style issues.

2021-01-31 Thread Joe Perches
On Sun, 2021-01-31 at 23:42 +0300, dev.dra...@bk.ru wrote: > diff --git a/drivers/staging/wimax/i2400m/rx.c > b/drivers/staging/wimax/i2400m/rx.c [] > @@ -764,9 +763,9 @@ unsigned __i2400m_roq_update_ws(struct i2400m *i2400m, > struct i2400m_roq *roq, >   new_nws);

Re: [PATCH 08/29] dma-buf: Avoid comma separated statements

2021-01-31 Thread Joe Perches
On Wed, 2021-02-03 at 14:26 +0100, Christian König wrote: > Am 30.01.21 um 19:47 schrieb Joe Perches: > > On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > > > Use semicolons and braces. > > Ping? > > > Signed-off-by: Joe Perches > Reviewed-by: Chri

Re: [PATCH 26/29] lib: zstd: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  lib/zstd/compress.c | 120 ++-- >  lib/zstd/fse_compress.c | 24 +--- >  lib/zstd/huf_compress.c | 6 +-

Re: [PATCH 25/29] lib/zlib: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  lib/zlib_deflate/deftree.c | 49 +++--- >  1 file changed, 35 insertions(+), 14 deletions(-) > > diff --g

Re: [PATCH 24/29] reiserfs: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  fs/reiserfs/fix_node.c | 36 >  1 file changed, 24 insertions(+), 12 deletions(-) > > diff --git a/fs/rei

Re: [PATCH 23/29] fuse: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  fs/fuse/dir.c | 24 >  1 file changed, 16 insertions(+), 8 deletions(-) > > diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c

Re: [PATCH 19/29] s390/tty3270: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  drivers/s390/char/tty3270.c | 6 -- >  1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/drivers/s390/char/tty3270.c b/driver

Re: [PATCH 13/29] bcache: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  drivers/md/bcache/bset.c | 12 >  drivers/md/bcache/sysfs.c | 6 -- >  2 files changed, 12 insertions(+), 6 deletions(-) > >

Re: [PATCH 06/29] drbd: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  drivers/block/drbd/drbd_receiver.c | 6 -- >  1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/drivers/block/drbd/drbd_receiver

Re: [PATCH 05/29] ata: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  drivers/ata/pata_icside.c | 21 + >  1 file changed, 13 insertions(+), 8 deletions(-) > > diff --git a/drivers/ata/pata_i

Re: [PATCH 04/29] sparc: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  arch/sparc/kernel/smp_64.c | 7 +-- >  1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/arch/sparc/kernel/smp_64.c b/arch/

Re: [PATCH 03/29] ia64: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > Signed-off-by: Joe Perches > --- >  arch/ia64/kernel/smpboot.c | 7 +-- >  1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/arch/ia64/kernel/smpboot.c b/arch/

Re: [PATCH 01/29] coding-style.rst: Avoid comma statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:55 -0700, Joe Perches wrote: > Commas are not how statements are terminated. > Always use semicolons and braces if necessary. ping? > > Signed-off-by: Joe Perches > --- >  Documentation/process/coding-style.rst | 17 + >  1 file c

Re: [PATCH 02/29] alpha: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:55 -0700, Joe Perches wrote: > Use semicolons and braces. ping? > > Signed-off-by: Joe Perches > --- >  arch/alpha/kernel/pci_iommu.c | 8 +--- >  arch/alpha/oprofile/op_model_ev4.c | 22 ++ >  arch/alpha/oprofil

Re: [PATCH 10/29] drm/i915: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. Ping? > Signed-off-by: Joe Perches > --- >  drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 8 +--- >  drivers/gpu/drm/i915/gt/intel_gt_requests.c| 6 -- >  drive

Re: [PATCH 09/29] drm/gma500: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. Ping? > Signed-off-by: Joe Perches > --- >  drivers/gpu/drm/gma500/mdfld_intel_display.c | 44 +--- >  1 file changed, 28 insertions(+), 16 deletions(-) > > diff --git a/d

Re: [PATCH 08/29] dma-buf: Avoid comma separated statements

2021-01-30 Thread Joe Perches
On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote: > Use semicolons and braces. Ping? > Signed-off-by: Joe Perches > --- >  drivers/dma-buf/st-dma-fence.c | 7 +-- >  1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/drivers/dma-buf/st-dma-fence.c b/d

Re: [PATCH v3 28/34] misc: Intel tsens IA host driver.

2021-01-30 Thread Joe Perches
On Fri, 2021-01-29 at 18:20 -0800, mgr...@linux.intel.com wrote: > From: "C, Udhayakumar" > > Add Intel tsens IA host driver for Intel Edge.AI Computer Vision > platforms. [] > diff --git a/drivers/misc/intel_tsens/intel_tsens_host.c > b/drivers/misc/intel_tsens/intel_tsens_host.c [] > +static

Re: [PATCH 2/5] bits_per_long.h: introduce SMALL_CONST() macro

2021-01-29 Thread Joe Perches
On Fri, 2021-01-29 at 23:10 +0200, Andy Shevchenko wrote: > On Fri, Jan 29, 2021 at 10:49 PM Yury Norov wrote: [] > > @@ -37,7 +37,7 @@ > >  #define GENMASK(h, l) \ > > (GENMASK_INPUT_CHECK(h, l) + __GENMASK(h, l)) > > > > -#define BITS_FIRST(nr) GENMASK(nr), 0) > > +#define

[PATCH] misc: pvpanic: sysfs_emit uses should have a newline

2021-01-29 Thread Joe Perches
Add newline terminations to the sysfs_emit uses added by -next commit 8d6da6575ffe ("misc: pvpanic: introduce events device attribue") Signed-off-by: Joe Perches --- drivers/misc/pvpanic.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/misc/pvpanic.c

Re: [PATCH -next] acpi: fpdt: drop errant comma in pr_info()

2021-01-28 Thread Joe Perches
On Thu, 2021-01-28 at 15:25 -0800, Randy Dunlap wrote: > Drop a mistaken comma in the pr_info() args to prevent the > build warning. > > ../drivers/acpi/acpi_fpdt.c: In function 'acpi_init_fpdt': > ../include/linux/kern_levels.h:5:18: warning: too many arguments for format >

Re: [PATCH] staging: net: wimax: i2400m: fw: remove redundant initialization of variable result

2021-01-28 Thread Joe Perches
On Thu, 2021-01-28 at 17:37 +, Colin King wrote: > From: Colin Ian King > > The variable result is being initialized with a value that is never > read and it is being updated later with a new value. The initialization > is redundant and can be removed. Isn't WIMAX dead? Shouldn't it be

Re: [PATCH v2 1/3] checkpatch: add verbose mode

2021-01-28 Thread Joe Perches
On Thu, 2021-01-28 at 20:08 +0530, Dwaipayan Ray wrote: > Add a new verbose mode to checkpatch.pl to emit additional verbose > test descriptions. The verbose mode is optional and can be enabled > by the flag -v or --verbose. [] > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl [] >

Re: [PATCH v15 09/10] arm64: Call kmalloc() to allocate DTB buffer

2021-01-27 Thread Joe Perches
On Thu, 2021-01-28 at 00:52 -0300, Thiago Jung Bauermann wrote: > The problem is that this patch implements only part of the suggestion, > which isn't useful in itself. So the patch series should either drop > this patch or consolidate the FDT allocation between the arches. > > I just tested on

Re: [PATCH 3/3] printk: dump full information of page flags in pGp

2021-01-27 Thread Joe Perches
On Thu, 2021-01-28 at 10:19 +0800, Yafang Shao wrote: > Currently the pGp only shows the names of page flags, rather than > the full information including section, node, zone, last cpupid and > kasan tag. While it is not easy to parse these information manually > because there're so many flavors.

Re: [PATCH] Bluetooth: af_bluetooth: checkpatch: fix indentation and alignment

2021-01-27 Thread Joe Perches
On Thu, 2021-01-28 at 00:05 +0900, Tomoyuki Matsushita wrote: > Signed-off-by: Tomoyuki Matsushita checkpatch is pretty stupid so whatever it recommends needs to be looked at carefully by a human and fixed appropriately. > diff --git a/net/bluetooth/af_bluetooth.c b/net/bluetooth/af_bluetooth.c

Re: [PATCH] KVM: x86/mmu: Add '__func__' in rmap_printk()

2021-01-27 Thread Joe Perches
On Wed, 2021-01-27 at 19:23 +0100, Paolo Bonzini wrote: > On 27/01/21 18:25, Joe Perches wrote: > > > > -#ifdef MMU_DEBUG > > -bool dbg = 0; > > -module_param(dbg, bool, 0644); > > -#endif > > - > >  #define PTE_PREFETCH_NUM 8 > >  

Re: [PATCH v10] staging: fbtft: add tearing signal detect

2021-01-27 Thread Joe Perches
> Comments are the exception to the "no spaces at the start of a line" > rule. I was expecting that the kbuild-bot would send a Smatch warning > for inconsistent indenting, but comments are not counted there either. > > I'm sort of surprised that we don't have checkpatch rule about the > missing

Re: [PATCH v10] staging: fbtft: add tearing signal detect

2021-01-27 Thread Joe Perches
On Wed, 2021-01-27 at 17:49 +0300, Dan Carpenter wrote: > On Wed, Jan 27, 2021 at 03:25:20PM +0100, Greg KH wrote: > > Andy and Joe, there's something wrong here that is missing the fact that > > a line is being indented with spaces and not tabs in the patch > > at > >

Re: [PATCH] KVM: x86/mmu: Add '__func__' in rmap_printk()

2021-01-27 Thread Joe Perches
On Wed, 2021-01-27 at 11:54 +0100, Paolo Bonzini wrote: > On 27/01/21 03:08, Stephen Zhang wrote: > > Given the common pattern: > > > > rmap_printk("%s:"..., __func__,...) > > > > we could improve this by adding '__func__' in rmap_printk(). Currently, the MMU_DEBUG control is not defined so

Re: [PATCH RFC 1/3] checkpatch: add verbose mode

2021-01-27 Thread Joe Perches
On Wed, 2021-01-27 at 01:57 +0530, Dwaipayan Ray wrote: > On Wed, Jan 27, 2021 at 1:41 AM Joe Perches wrote: > > On Wed, 2021-01-27 at 00:05 +0530, Dwaipayan Ray wrote: > > > Add a new verbose mode to checkpatch.pl to emit additional verbose > > > test descriptions. &g

Re: [PATCH] Revert "checkpatch: add check for keyword 'boolean' in Kconfig definitions"

2021-01-26 Thread Joe Perches
Signed-off-by: Masahiro Yamada Acked-by: Joe Perches > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl [] > @@ -3390,13 +3390,6 @@ sub process { >   } >   } >   > -# discourage the use of boolean for type definition attributes of

Re: [PATCH RFC 1/3] checkpatch: add verbose mode

2021-01-26 Thread Joe Perches
On Wed, 2021-01-27 at 00:05 +0530, Dwaipayan Ray wrote: > Add a new verbose mode to checkpatch.pl to emit additional verbose > test descriptions. > > The verbose mode is optional and can be enabled by the flag > --verbose. > > The test descriptions are itself loaded from the checkpatch

Re: [PATCH v3] rtlwifi: Simplify bool comparison

2021-01-26 Thread Joe Perches
On Tue, 2021-01-26 at 16:31 +0800, Jiapeng Zhong wrote: > Fix the following coccicheck warning: > ./drivers/net/wireless/realtek/rtlwifi/ps.c:798:7-21: WARNING: > Comparison to bool > ./drivers/net/wireless/realtek/rtlwifi/rtl8821ae/phy.c:3848:7-17: > WARNING: Comparison of 0/1 to bool variable []

Anyone have ideas for checkpatch improvements ?

2021-01-24 Thread Joe Perches

Re: Anyone have ideas for checkpatch improvements ?

2021-01-24 Thread Joe Perches
One of the linux-mentees, Dwaipayan Ray, asked me in a private email for ideas for improvements to checkpatch. Though I am not his nominal mentor, my response to him was the below. Does anyone have any more ideas for checkpatch improvements or enhancements? --- On Fri, 2021-01-15 at 21:02

Re: [PATCH v3] checkpatch: add warning for avoiding .L prefix symbols in assembly files

2021-01-23 Thread Joe Perches
> > Suggested-by: Mark Brown > Link: https://lore.kernel.org/lkml/20210112210154.gi4...@sirena.org.uk > Signed-off-by: Aditya Srivastava Acked-by: Joe Perches > --- > * Applies perfectly on next-20210122 > > Changes in v3: > - Modify regex for SYM_*_START/END pa

Re: [PATCH] usb: typec: tcpci_maxim: remove redundant assignment

2021-01-23 Thread Joe Perches
> diff --git a/drivers/usb/typec/tcpm/tcpci_maxim.c > b/drivers/usb/typec/tcpm/tcpci_maxim.c On Sat, 2021-01-23 at 18:14 +0800, angkery wrote: > From: Junlin Yang > > PTR_ERR(chip->tcpci) has been used as a return value, > it is not necessary to assign it to ret, so remove it. [] [] > @@ -461,7

Re: [PATCH v2] checkpatch: add warning for avoiding .L prefix symbols in assembly files

2021-01-23 Thread Joe Perches
On Sat, 2021-01-23 at 20:44 +0530, Aditya Srivastava wrote: > objtool requires that all code must be contained in an ELF symbol. > Symbol names that have a '.L' prefix do not emit symbol table entries, as > they have special meaning for the assembler. > > '.L' prefixed symbols can be used within

[PATCH] checkpatch: Add kmalloc_array_node to unnecessary OOM message check

2021-01-22 Thread Joe Perches
commit 5799b255c491 ("include/linux/slab.h: add kmalloc_array_node() and kcalloc_node()") was added in 2017. Update the unnecessary OOM message test to include it. Signed-off-by: Joe Perches Reported-by: Jakub Kicinski --- Maybe not worth fixing, but no real effort to fix either.

Re: [PATCH] checkpatch: add warning for avoiding .L prefix symbols in assembly files

2021-01-22 Thread Joe Perches
On Fri, 2021-01-22 at 18:48 +0530, Aditya wrote: > On 21/1/21 12:13 am, Joe Perches wrote: > > I believe the test should be: > > > > if ($realfile =~ /\.S$/ && > > $line =~ /^\+\s*SYM_[A-Z]+_(?:START|END)(?:_[A-Z_]+)?\s*\(\s*\.L/) { > > Joe, w

Re: [PATCH] diffconfig: use python3 instead of python in Shebang line

2021-01-22 Thread Joe Perches
On Sat, 2021-01-23 at 02:16 +0900, Masahiro Yamada wrote: > On Sat, Jan 23, 2021 at 12:51 AM Joe Perches wrote: > > > > On Fri, 2021-01-22 at 07:06 +0900, Masahiro Yamada wrote: > > > I use Ubuntu, where /usr/bin/python is a symlink > > > to /us

Re: [PATCH] diffconfig: use python3 instead of python in Shebang line

2021-01-22 Thread Joe Perches
On Fri, 2021-01-22 at 07:06 +0900, Masahiro Yamada wrote: > I use Ubuntu, where /usr/bin/python is a symlink > to /usr/bin/python3. Odd, here: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.10 Release:20.10 Codename: groovy $ ls

Re: [PATCH] diffconfig: use python3 instead of python in Shebang line

2021-01-21 Thread Joe Perches
On Fri, 2021-01-22 at 05:25 +0900, Masahiro Yamada wrote: > On Fri, Jan 22, 2021 at 2:17 AM Scott Branden > wrote: > > > > Use python3 instead of python in diffconfig Shebang line. > > python2 was sunset January 1, 2000 and environments do not need > > to support python any more. python2 was

Re: [PATCH] scripts/spelling.txt: increase error-prone spell checking

2021-01-21 Thread Joe Perches
On Thu, 2021-01-21 at 18:14 +0900, Naoki Hayama wrote: > On 2021/01/21 17:41, Luca Ceresoli wrote: > > On 21/01/21 04:21, Chunyou Tang wrote: > > > On Wed, 20 Jan 2021 19:09:05 -0800 Joe Perches wrote: > > > > On Wed, 2021-01-20 at 19:02 -0800, Randy Dunlap wrote

Re: [PATCH] scripts/spelling.txt: increase error-prone spell checking

2021-01-20 Thread Joe Perches
On Wed, 2021-01-20 at 19:02 -0800, Randy Dunlap wrote: > On 1/20/21 6:07 PM, ChunyouTang wrote: > > From: tangchunyou > > > > Increase direcly,maping,manger spelling error check > > Hi, > I don't see all of those in the patch below. > What happened? I think mostly it's just a poor commit

<    1   2   3   4   5   6   7   8   9   10   >