[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9aea2179b54f83084e22eee137819b7@milecki.pl>
Date: Tue, 18 Jul 2023 18:59:01 +0200
From: Rafał Miłecki <rafal@...ecki.pl>
To: kernel test robot <lkp@...el.com>
Cc: Rafał Miłecki <zajec5@...il.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
oe-kbuild-all@...ts.linux.dev,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Alban Bedel <albeu@...e.fr>,
Christian Marangi <ansuelsmth@...il.com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "nvmem: add new config option"
On 2023-07-18 18:00, kernel test robot wrote:
> drivers/mtd/mtdcore.c: In function 'mtd_nvmem_add':
>>> drivers/mtd/mtdcore.c:542:29: warning: unused variable 'node'
>>> [-Wunused-variable]
> 542 | struct device_node *node = mtd_get_of_node(mtd);
> | ^~~~
My patch I mentioned:
[PATCH V4] nvmem: add explicit config option to read old syntax fixed OF
cells
adds following line:
config.add_legacy_fixed_of_cells = of_device_is_compatible(node,
"nvmem-cells");
So this is a false kernel bot warning (but I understand kernel bot
couldn't understand it needs my other patch).
Powered by blists - more mailing lists