mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	H Hartley Sweeten <hsweeten@visionengravers.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	driverdevel <devel@driverdev.osuosl.org>,
	Linux-Next <linux-next@vger.kernel.org>
Subject: Re: [-next] comedi I/O accessor name clashes
Date: Fri, 20 Jun 2014 12:12:32 +0100	[thread overview]
Message-ID: <53A41720.9020609@mev.co.uk> (raw)
In-Reply-To: <CAMuHMdVhU6JZFzuPkx=wtLcPYc7wwaMFwCrZu=zG7PmCYssy-g@mail.gmail.com>

On 2014-06-20 12:07, Geert Uytterhoeven wrote:
> commit 9c340ac934dbbfd46e776465b08391baac32d486
> Author: H Hartley Sweeten <hsweeten@visionengravers.com>
> Date:   Thu May 29 10:56:32 2014 -0700
>
>      staging: comedi: ni_stc.h: add read/write callbacks to struct ni_private
>
> --- a/drivers/staging/comedi/drivers/ni_stc.h
> +++ b/drivers/staging/comedi/drivers/ni_stc.h
> @@ -1421,6 +1421,13 @@ struct ni_board_struct {
>   #define NUM_GPCT       2
>
>   struct ni_private {
> +       uint8_t (*readb)(struct comedi_device *, int reg);
> +       uint16_t (*readw)(struct comedi_device *, int reg);
> +       uint32_t (*readl)(struct comedi_device *, int reg);
> +       void (*writeb)(struct comedi_device *, uint8_t value, int reg);
> +       void (*writew)(struct comedi_device *, uint16_t value, int reg);
> +       void (*writel)(struct comedi_device *, uint32_t value, int reg);
> +
>          uint16_t (*stc_readw)(struct comedi_device *, int reg);
>          uint32_t (*stc_readl)(struct comedi_device *, int reg);
>          void (*stc_writew)(struct comedi_device *, uint16_t value, int reg);
>
> However, on several architectures, writel() and friends are macros, causing:
>
> drivers/staging/comedi/drivers/ni_atmio.c:318:38: error: macro
> "writew" passed 3 arguments, but takes just 2
>
> m68k http://kisskb.ellerman.id.au/kisskb/buildresult/11346953/
> s390 kisskb.ellerman.id.au/kisskb/buildresult/11347163/
> sparc64 kisskb.ellerman.id.au/kisskb/buildresult/11347152/
> xtensa http://kisskb.ellerman.id.au/kisskb/buildresult/11346651/
>
> Gr{oetje,eeting}s,
>
>                          Geert

Thanks, but Hartley has already fixed it and Greg has applied it to his 
staging-next branch.  It should wend it's merry way to linux-next in the 
not-too-distant future.

Cheers,
Ian.

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

  reply	other threads:[~2014-06-20 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 11:07 Geert Uytterhoeven
2014-06-20 11:12 ` Ian Abbott [this message]
2014-06-20 11:20   ` Geert Uytterhoeven
2014-06-20 16:20     ` Hartley Sweeten

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=53A41720.9020609@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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

all inboxes | Powered by JetHome®