From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Lukas Bulwahn <lukas.bulwahn@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the staging.current tree
Date: Wed, 8 Jan 2025 12:48:20 +0100 [thread overview]
Message-ID: <2025010802-superglue-marshland-1ea4@gregkh> (raw)
In-Reply-To: <20250108214240.482e0ca5@canb.auug.org.au>
On Wed, Jan 08, 2025 at 09:42:40PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the staging.current tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> ld: drivers/staging/gpib/tnt4882/mite.o: in function `mite_dma_disarm':
> mite.c:(.text+0x1240): multiple definition of `mite_dma_disarm'; drivers/comedi/drivers/mite.o:mite.c:(.text+0x1ac0): first defined here
>
> Exposed by commit
>
> 84b172cea4a2 ("staging: gpib: refer to correct config symbol in tnt4882 Makefile")
>
> It is not, of course, the real cause of the build failure. The duplicate
> version of mite_dma_disarm() in drivers/staging/gpib/tnt4882/mite.c is
> not actually used anywhere, so I applied the following patch for today.
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 8 Jan 2025 21:07:23 +1100
> Subject: [PATCH] fix for "staging: gpib: refer to correct config symbol in
> tnt4882 Makefile"
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/staging/gpib/tnt4882/mite.c | 9 ---------
> drivers/staging/gpib/tnt4882/mite.h | 1 -
> 2 files changed, 10 deletions(-)
>
> diff --git a/drivers/staging/gpib/tnt4882/mite.c b/drivers/staging/gpib/tnt4882/mite.c
> index 90341f8c394e..22035e53ec35 100644
> --- a/drivers/staging/gpib/tnt4882/mite.c
> +++ b/drivers/staging/gpib/tnt4882/mite.c
> @@ -170,15 +170,6 @@ int mite_dma_tcr(struct mite_struct *mite)
> return tcr;
> }
>
> -void mite_dma_disarm(struct mite_struct *mite)
> -{
> - int chor;
> -
> - /* disarm */
> - chor = CHOR_ABORT;
> - writel(chor, mite->mite_io_addr + CHAN_OFFSET(0) + MITE_CHOR);
> -}
> -
> void mite_dump_regs(struct mite_struct *mite)
> {
> void *addr = 0;
> diff --git a/drivers/staging/gpib/tnt4882/mite.h b/drivers/staging/gpib/tnt4882/mite.h
> index 2ecd83379974..dbfc59468228 100644
> --- a/drivers/staging/gpib/tnt4882/mite.h
> +++ b/drivers/staging/gpib/tnt4882/mite.h
> @@ -64,7 +64,6 @@ void mite_list_devices(void);
> int mite_dma_tcr(struct mite_struct *mite);
>
> void mite_dma_arm(struct mite_struct *mite);
> -void mite_dma_disarm(struct mite_struct *mite);
>
> void mite_dump_regs(struct mite_struct *mite);
> void mite_setregs(struct mite_struct *mite, unsigned long ll_start, int chan, int dir);
> --
> 2.45.2
>
> --
> Cheers,
> Stephen Rothwell
Ah, I just beat you to it:
https://lore.kernel.org/r/2025010809-padding-survive-91b3@gregkh
I'll queue this up later today, thanks!
greg k-h
next prev parent reply other threads:[~2025-01-08 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 10:42 linux-next: build failure after merge of the staging.current tree Stephen Rothwell
2025-01-08 11:48 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-14 6:00 Stephen Rothwell
2017-12-14 7:27 ` Greg KH
2011-06-08 1:41 Stephen Rothwell
2011-06-08 16:11 ` Greg KH
2011-06-08 16:58 ` Mauro Carvalho Chehab
2011-06-08 16:21 ` Greg KH
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=2025010802-superglue-marshland-1ea4@gregkh \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=sfr@canb.auug.org.au \
/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