From: Niklas Cassel <cassel@kernel.org>
To: Pei Xiao <xiaopei01@kylinos.cn>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [libata:for-next 7/7] drivers/ata/pata_parport/pata_parport.c:707:13: warning: conflicting types for 'pi_remove_one'; have 'void(struct device *)'
Date: Thu, 10 Sep 2026 03:03:09 +0200 [thread overview]
Message-ID: <aqIBzTU8VK4KQRrJ@ryzen> (raw)
In-Reply-To: <1f3cbeb0-29ca-405e-8604-4a4fcb55e0a1@kylinos.cn>
On Thu, Sep 10, 2026 at 08:53:40AM +0800, Pei Xiao wrote:
> 在 2026/9/10 07:15, kernel test robot 写道:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git for-next
> > head: d82c5cf658c306979c786a6702487cf9fbc2b5de
> > commit: d82c5cf658c306979c786a6702487cf9fbc2b5de [7/7] ata: pata_parport: unregister devices on protocol unregister
> > config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20260910/202609100732.jcpwPdM6-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 16.1.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260910/202609100732.jcpwPdM6-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/202609100732.jcpwPdM6-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > drivers/ata/pata_parport/pata_parport.c: In function 'pi_remove_by_proto':
> > drivers/ata/pata_parport/pata_parport.c:621:17: error: implicit declaration of function 'pi_remove_one' [-Wimplicit-function-declaration]
> hi Maintainer,
> I'm very sorry about this. I haven't had my physical machine with me
> recently, so this patch hasn't been tested. What should I do now? Do I
> need to revert this patch, or should I just fix this compilation error?
I dropped this series from for-7.4.
Please send a new version that you have actually tested.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-09-10 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 23:15 [libata:for-next 7/7] drivers/ata/pata_parport/pata_parport.c:707:13: warning: conflicting types for 'pi_remove_one'; have 'void(struct device *)' kernel test robot
2026-09-10 0:53 ` Pei Xiao
2026-09-10 1:03 ` Niklas Cassel [this message]
2026-09-10 1:04 ` Pei Xiao
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=aqIBzTU8VK4KQRrJ@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xiaopei01@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.