mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Beniamin Sandu <beniaminsandu@gmail.com>,
	dinguyen@kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Beniamin Sandu <beniaminsandu@gmail.com>
Subject: Re: [PATCH] firmware: stratix10-rsu: correctly report unsupported DCMF commands
Date: Thu, 30 Nov 2023 16:34:17 +0800	[thread overview]
Message-ID: <202311301536.gQXR41jR-lkp@intel.com> (raw)
In-Reply-To: <20231129190336.247674-1-beniaminsandu@gmail.com>

Hi Beniamin,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.7-rc3 next-20231130]
[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/Beniamin-Sandu/firmware-stratix10-rsu-correctly-report-unsupported-DCMF-commands/20231130-055016
base:   linus/master
patch link:    https://lore.kernel.org/r/20231129190336.247674-1-beniaminsandu%40gmail.com
patch subject: [PATCH] firmware: stratix10-rsu: correctly report unsupported DCMF commands
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20231130/202311301536.gQXR41jR-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231130/202311301536.gQXR41jR-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/202311301536.gQXR41jR-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/firmware/stratix10-rsu.c: In function 'rsu_dcmf_version_callback':
>> drivers/firmware/stratix10-rsu.c:240:9: error: expected ';' before 'else'
     240 |         else
         |         ^~~~
   drivers/firmware/stratix10-rsu.c: In function 'rsu_dcmf_status_callback':
   drivers/firmware/stratix10-rsu.c:271:9: error: expected ';' before 'else'
     271 |         else
         |         ^~~~


vim +240 drivers/firmware/stratix10-rsu.c

   217	
   218	/**
   219	 * rsu_dcmf_version_callback() - Callback from Intel service layer for getting
   220	 * the DCMF version
   221	 * @client: pointer to client
   222	 * @data: pointer to callback data structure
   223	 *
   224	 * Callback from Intel service layer for DCMF version number
   225	 */
   226	static void rsu_dcmf_version_callback(struct stratix10_svc_client *client,
   227					      struct stratix10_svc_cb_data *data)
   228	{
   229		struct stratix10_rsu_priv *priv = client->priv;
   230		unsigned long long *value1 = (unsigned long long *)data->kaddr1;
   231		unsigned long long *value2 = (unsigned long long *)data->kaddr2;
   232	
   233		if (data->status == BIT(SVC_STATUS_OK)) {
   234			priv->dcmf_version.dcmf0 = FIELD_GET(RSU_DCMF0_MASK, *value1);
   235			priv->dcmf_version.dcmf1 = FIELD_GET(RSU_DCMF1_MASK, *value1);
   236			priv->dcmf_version.dcmf2 = FIELD_GET(RSU_DCMF2_MASK, *value2);
   237			priv->dcmf_version.dcmf3 = FIELD_GET(RSU_DCMF3_MASK, *value2);
   238		} else if (data->status == BIT(SVC_STATUS_NO_SUPPORT))
   239			dev_warn(client->dev, "Secure FW doesn't support DCMF version.")
 > 240		else
   241			dev_err(client->dev, "failed to get DCMF version\n");
   242	
   243		complete(&priv->completion);
   244	}
   245	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2023-11-30  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 19:03 Beniamin Sandu
2023-11-30  8:34 ` 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=202311301536.gQXR41jR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=beniaminsandu@gmail.com \
    --cc=dinguyen@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®