From: kernel test robot <lkp@intel.com>
To: Jakub Czapiga <czapiga@google.com>,
Mark Brown <broonie@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Konrad Adamczyk <konrada@google.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Jakub Czapiga <czapiga@google.com>
Subject: Re: [PATCH] spi: intel: Allow writeable MTD partition with module param
Date: Wed, 16 Jul 2025 13:13:51 +0800 [thread overview]
Message-ID: <202507161228.D92rDToS-lkp@intel.com> (raw)
In-Reply-To: <20250715095007.896620-1-czapiga@google.com>
Hi Jakub,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-spi/for-next]
[also build test ERROR on broonie-sound/for-next westeri-thunderbolt/next linus/master v6.16-rc6 next-20250715]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jakub-Czapiga/spi-intel-Allow-writeable-MTD-partition-with-module-param/20250715-175230
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
patch link: https://lore.kernel.org/r/20250715095007.896620-1-czapiga%40google.com
patch subject: [PATCH] spi: intel: Allow writeable MTD partition with module param
config: arc-randconfig-001-20250716 (https://download.01.org/0day-ci/archive/20250716/202507161228.D92rDToS-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250716/202507161228.D92rDToS-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202507161228.D92rDToS-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/spi/spi-intel.c:195:34: error: expected ')' before string constant
195 | ignore_protection_status,
| ^
| )
196 | "Do not block SPI flash chip write access even if it is write-protected (default=0)");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +195 drivers/spi/spi-intel.c
188
189 static bool writeable;
190 module_param(writeable, bool, 0);
191 MODULE_PARM_DESC(writeable, "Enable write access to SPI flash chip (default=0)");
192 static bool ignore_protection_status;
193 module_param(ignore_protection_status, bool, 0);
194 MODULE_PARAM_DESC(
> 195 ignore_protection_status,
196 "Do not block SPI flash chip write access even if it is write-protected (default=0)");
197
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-07-16 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 9:50 Jakub Czapiga
2025-07-16 5:13 ` kernel test robot [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=202507161228.D92rDToS-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=czapiga@google.com \
--cc=konrada@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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®