Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
	ohad@wizery.com, bjorn.andersson@linaro.org,
	mathieu.poirier@linaro.org, robh+dt@kernel.org, s-anna@ti.com,
	ssantosh@kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	grzegorz.jaszczyk@linaro.org, linux-remoteproc@vger.kernel.org,
	lee.jones@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/5] remoteproc: pru: Deny rproc sysfs ops for PRU client driven boots
Date: Fri, 18 Dec 2020 06:43:37 +0800	[thread overview]
Message-ID: <202012180656.jA4L7mPJ-lkp@intel.com> (raw)
In-Reply-To: <20201216165239.2744-4-grzegorz.jaszczyk@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 4130 bytes --]

Hi Grzegorz,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on next-20201217]
[cannot apply to robh/for-next remoteproc/for-next rpmsg/for-next v5.10]
[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]

url:    https://github.com/0day-ci/linux/commits/Grzegorz-Jaszczyk/Introduce-PRU-remoteproc-consumer-API/20201217-005732
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git d01e7f10dae29eba0f9ada82b65d24e035d5b2f9
config: arm64-randconfig-r025-20201217 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project cee1e7d14f4628d6174b33640d502bff3b54ae45)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/f34d9f03fd4cf7008a1bd30b1cb5ebcab67c97c9
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Grzegorz-Jaszczyk/Introduce-PRU-remoteproc-consumer-API/20201217-005732
        git checkout f34d9f03fd4cf7008a1bd30b1cb5ebcab67c97c9
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/remoteproc/pru_rproc.c:231:9: error: no member named 'deny_sysfs_ops' in 'struct rproc'
           rproc->deny_sysfs_ops = true;
           ~~~~~  ^
   drivers/remoteproc/pru_rproc.c:262:9: error: no member named 'deny_sysfs_ops' in 'struct rproc'
           rproc->deny_sysfs_ops = false;
           ~~~~~  ^
   2 errors generated.


vim +231 drivers/remoteproc/pru_rproc.c

   186	
   187	/**
   188	 * pru_rproc_get() - get the PRU rproc instance from a device node
   189	 * @np: the user/client device node
   190	 * @index: index to use for the ti,prus property
   191	 * @pru_id: optional pointer to return the PRU remoteproc processor id
   192	 *
   193	 * This function looks through a client device node's "ti,prus" property at
   194	 * index @index and returns the rproc handle for a valid PRU remote processor if
   195	 * found. The function allows only one user to own the PRU rproc resource at a
   196	 * time. Caller must call pru_rproc_put() when done with using the rproc, not
   197	 * required if the function returns a failure.
   198	 *
   199	 * When optional @pru_id pointer is passed the PRU remoteproc processor id is
   200	 * returned.
   201	 *
   202	 * Return: rproc handle on success, and an ERR_PTR on failure using one
   203	 * of the following error values
   204	 *    -ENODEV if device is not found
   205	 *    -EBUSY if PRU is already acquired by anyone
   206	 *    -EPROBE_DEFER is PRU device is not probed yet
   207	 */
   208	struct rproc *pru_rproc_get(struct device_node *np, int index,
   209				    enum pruss_pru_id *pru_id)
   210	{
   211		struct rproc *rproc;
   212		struct pru_rproc *pru;
   213		struct device *dev;
   214	
   215		rproc = __pru_rproc_get(np, index);
   216		if (IS_ERR(rproc))
   217			return rproc;
   218	
   219		pru = rproc->priv;
   220		dev = &rproc->dev;
   221	
   222		mutex_lock(&pru->lock);
   223	
   224		if (pru->client_np) {
   225			mutex_unlock(&pru->lock);
   226			put_device(dev);
   227			return ERR_PTR(-EBUSY);
   228		}
   229	
   230		pru->client_np = np;
 > 231		rproc->deny_sysfs_ops = true;
   232	
   233		mutex_unlock(&pru->lock);
   234	
   235		if (pru_id)
   236			*pru_id = pru->id;
   237	
   238		return rproc;
   239	}
   240	EXPORT_SYMBOL_GPL(pru_rproc_get);
   241	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34315 bytes --]

  reply	other threads:[~2020-12-17 22:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 16:52 [PATCH v2 0/5] Introduce PRU remoteproc consumer API Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 1/5] dt-bindings: remoteproc: Add PRU consumer bindings Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 2/5] remoteproc: pru: Add APIs to get and put the PRU cores Grzegorz Jaszczyk
2021-01-04 20:56   ` David Lechner
2020-12-16 16:52 ` [PATCH v2 3/5] remoteproc: pru: Deny rproc sysfs ops for PRU client driven boots Grzegorz Jaszczyk
2020-12-17 22:43   ` kernel test robot [this message]
2020-12-16 16:52 ` [PATCH v2 4/5] remoteproc: pru: Add pru_rproc_set_ctable() function Grzegorz Jaszczyk
2020-12-16 16:52 ` [PATCH v2 5/5] remoteproc: pru: Configure firmware based on client setup Grzegorz Jaszczyk
2021-01-04 20:11 ` [PATCH v2 0/5] Introduce PRU remoteproc consumer API David Lechner
2021-01-06 21:05   ` Suman Anna
2021-01-06 23:27 ` Mathieu Poirier
2021-01-07  0:03   ` Suman Anna
2021-01-07 22:44     ` Mathieu Poirier
2021-01-07 22:49       ` Suman Anna
2021-01-25  4:34         ` santosh.shilimkar
2021-01-25 15:43           ` Suman Anna
2021-01-25 15:56             ` [External] : " Santosh Shilimkar
2021-12-26 13:00             ` Christian Gmeiner

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=202012180656.jA4L7mPJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grzegorz.jaszczyk@linaro.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=ohad@wizery.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=ssantosh@kernel.org \
    /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