From: Dave Penkler <dpenkler@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/3] staging: gpib: Remove depends on BROKEN
Date: Sun, 26 Jan 2025 19:18:17 +0100 [thread overview]
Message-ID: <Z5Z8aaPYfxtOnMJV@egonzo> (raw)
In-Reply-To: <202501252201.OmgbVCva-lkp@intel.com>
On Sat, Jan 25, 2025 at 10:47:53PM +0800, kernel test robot wrote:
> Hi Dave,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on staging/staging-testing]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Dave-Penkler/staging-gpib-Fix-pr_err-format-warning/20250124-190232
> base: staging/staging-testing
> patch link: https://lore.kernel.org/r/20250124105900.27592-4-dpenkler%40gmail.com
> patch subject: [PATCH 3/3] staging: gpib: Remove depends on BROKEN
> config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20250125/202501252201.OmgbVCva-lkp@intel.com/config)
> compiler: alpha-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250125/202501252201.OmgbVCva-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/202501252201.OmgbVCva-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> alpha-linux-ld: drivers/staging/gpib/hp_82341/hp_82341.o: in function `read_and_clear_event_status':
> >> (.text+0x1400): multiple definition of `read_and_clear_event_status'; drivers/staging/gpib/agilent_82350b/agilent_82350b.o:(.text+0x13c0): first defined here
> alpha-linux-ld: drivers/staging/gpib/hp_82341/hp_82341.o: in function `read_transfer_counter':
> >> (.text+0x1480): multiple definition of `read_transfer_counter'; drivers/staging/gpib/agilent_82350b/agilent_82350b.o:(.text+0x1440): first defined here
> alpha-linux-ld: drivers/staging/gpib/hp_82341/hp_82341.o: in function `set_transfer_counter':
> >> (.text+0x1510): multiple definition of `set_transfer_counter'; drivers/staging/gpib/agilent_82350b/agilent_82350b.o:(.text+0x14d0): first defined here
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
This problem has been resolved by a previous patch:
Link: https://lore.kernel.org/linux-staging/20250122103859.25499-3-dpenkler@gmail.com/T/#u
This patch has not yet been applied to the staging-testing branch.
-dave
prev parent reply other threads:[~2025-01-26 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 10:58 [PATCH 0/3] staging: gpib: Fix CONFIG_GPIB_HP82341 build failure Dave Penkler
2025-01-24 10:58 ` [PATCH 1/3] staging: gpib: Fix pr_err format warning Dave Penkler
2025-01-24 10:58 ` [PATCH 2/3] pnp: isapnp: Export isapnp_read_byte again Dave Penkler
2025-01-24 10:59 ` [PATCH 3/3] staging: gpib: Remove depends on BROKEN Dave Penkler
2025-01-25 11:39 ` kernel test robot
2025-01-25 14:16 ` kernel test robot
2025-01-26 18:13 ` Dave Penkler
2025-01-25 14:47 ` kernel test robot
2025-01-26 18:18 ` Dave Penkler [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=Z5Z8aaPYfxtOnMJV@egonzo \
--to=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@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 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.