From: kernel test robot <lkp@intel.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
"Jens Axboe" <axboe@kernel.dk>, "Matt Mackall" <mpm@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jarkko Sakkinen" <jarkko@kernel.org>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] vio: make remove callback return void
Date: Wed, 24 Feb 2021 17:44:21 +0800 [thread overview]
Message-ID: <202102241721.2y6F4IeB-lkp@intel.com> (raw)
In-Reply-To: <20210224072516.74696-1-uwe@kleine-koenig.org>
[-- Attachment #1: Type: text/plain, Size: 3043 bytes --]
Hi "Uwe,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20210224]
[also build test ERROR on v5.11]
[cannot apply to powerpc/next sparc/master sparc-next/master v5.11 v5.11-rc7 v5.11-rc6]
[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/Uwe-Kleine-K-nig/vio-make-remove-callback-return-void/20210224-153029
base: 577c283560fe8a81a23a95654c6d13e8412d22f1
config: powerpc-randconfig-r013-20210223 (attached as .config)
compiler: powerpc64le-linux-gcc (GCC) 9.3.0
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
# https://github.com/0day-ci/linux/commit/1cc965e9b41d0acfaf8d597ffeb7ef1c2031ec4c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Uwe-Kleine-K-nig/vio-make-remove-callback-return-void/20210224-153029
git checkout 1cc965e9b41d0acfaf8d597ffeb7ef1c2031ec4c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
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/tty/hvc/hvcs.c:822:13: error: conflicting types for 'hvcs_remove'
822 | static void hvcs_remove(struct vio_dev *dev)
| ^~~~~~~~~~~
drivers/tty/hvc/hvcs.c:320:12: note: previous declaration of 'hvcs_remove' was here
320 | static int hvcs_remove(struct vio_dev *dev);
| ^~~~~~~~~~~
vim +/hvcs_remove +822 drivers/tty/hvc/hvcs.c
821
> 822 static void hvcs_remove(struct vio_dev *dev)
823 {
824 struct hvcs_struct *hvcsd = dev_get_drvdata(&dev->dev);
825 unsigned long flags;
826 struct tty_struct *tty;
827
828 /* By this time the vty-server won't be getting any more interrupts */
829
830 spin_lock_irqsave(&hvcsd->lock, flags);
831
832 tty = hvcsd->port.tty;
833
834 spin_unlock_irqrestore(&hvcsd->lock, flags);
835
836 /*
837 * Let the last holder of this object cause it to be removed, which
838 * would probably be tty_hangup below.
839 */
840 tty_port_put(&hvcsd->port);
841
842 /*
843 * The hangup is a scheduled function which will auto chain call
844 * hvcs_hangup. The tty should always be valid at this time unless a
845 * simultaneous tty close already cleaned up the hvcs_struct.
846 */
847 if (tty)
848 tty_hangup(tty);
849
850 printk(KERN_INFO "HVCS: vty-server@%X removed from the"
851 " vio bus.\n", dev->unit_address);
852 };
853
---
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: 30696 bytes --]
next prev parent reply other threads:[~2021-02-24 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 7:25 [PATCH v2] vio: make remove callback return void Uwe Kleine-König
2021-02-24 9:44 ` kernel test robot [this message]
2021-02-24 11:01 ` Anatoly Pugachev
2021-02-25 11:49 ` Michael Ellerman
2021-02-25 14:01 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2021-02-25 22:18 Uwe Kleine-König
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=202102241721.2y6F4IeB-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=mpe@ellerman.id.au \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterhuewe@gmx.de \
--cc=uwe@kleine-koenig.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;
as well as URLs for NNTP newsgroup(s).