From: Michael Walle <michael@walle.cc>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kbuild@lists.01.org, lkp@intel.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Pratyush Yadav <p.yadav@ti.com>
Subject: Re: [mtd:spi-nor/next 16/18] drivers/mtd/spi-nor/debugfs.c:84 spi_nor_params_show() warn: '%ph' cannot be followed by 'n'
Date: Wed, 11 May 2022 13:35:16 +0200 [thread overview]
Message-ID: <f1399a5413d8f151e536c7005eca6763@walle.cc> (raw)
In-Reply-To: <202205110320.WNi7ZQaB-lkp@intel.com>
Am 2022-05-11 12:17, schrieb Dan Carpenter:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
> spi-nor/next
> head: cdbc44dbb2c73d8bafa1a8ae0d780608be5dbd40
> commit: 0257be79fc4a16a3252ce80aa13b3640f728c425 [16/18] mtd: spi-nor:
> expose internal parameters via debugfs
> config: x86_64-randconfig-m001-20220509
> (https://download.01.org/0day-ci/archive/20220511/202205110320.WNi7ZQaB-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> smatch warnings:
> drivers/mtd/spi-nor/debugfs.c:84 spi_nor_params_show() warn: '%ph'
> cannot be followed by 'n'
>
> vim +84 drivers/mtd/spi-nor/debugfs.c
>
> 0257be79fc4a16 Michael Walle 2022-04-29 73 static int
> spi_nor_params_show(struct seq_file *s, void *data)
> 0257be79fc4a16 Michael Walle 2022-04-29 74 {
> 0257be79fc4a16 Michael Walle 2022-04-29 75 struct spi_nor *nor =
> s->private;
> 0257be79fc4a16 Michael Walle 2022-04-29 76 struct
> spi_nor_flash_parameter *params = nor->params;
> 0257be79fc4a16 Michael Walle 2022-04-29 77 struct
> spi_nor_erase_map *erase_map = ¶ms->erase_map;
> 0257be79fc4a16 Michael Walle 2022-04-29 78 struct
> spi_nor_erase_region *region;
> 0257be79fc4a16 Michael Walle 2022-04-29 79 const struct flash_info
> *info = nor->info;
> 0257be79fc4a16 Michael Walle 2022-04-29 80 char buf[16], *str;
> 0257be79fc4a16 Michael Walle 2022-04-29 81 int i;
> 0257be79fc4a16 Michael Walle 2022-04-29 82
> 0257be79fc4a16 Michael Walle 2022-04-29 83 seq_printf(s,
> "name\t\t%s\n", info->name);
> 0257be79fc4a16 Michael Walle 2022-04-29 @84 seq_printf(s,
> "id\t\t%*phn\n", info->id_len, info->id);
>
> Maybe N was intended instead of n? (I have no idea).
Thanks for reporting. Yeah I had %*phN previously but then
I wanted to switch to "xx xx xx" style and i missed checking
printk-formats.rst. %*phn worked as intended ;) I'll send
a fixup patch.
-michael
prev parent reply other threads:[~2022-05-11 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 10:17 Dan Carpenter
2022-05-11 11:35 ` Michael Walle [this message]
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=f1399a5413d8f151e536c7005eca6763@walle.cc \
--to=michael@walle.cc \
--cc=dan.carpenter@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=p.yadav@ti.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
all inboxes | Powered by JetHome®