From: schmitz <schmitz@biophys.uni-duesseldorf.de>
To: Chen Gang <gang.chen@asianux.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Ungerer <gerg@uclinux.org>,
schmitz@debian.org, Sam Ravnborg <sam@ravnborg.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-m68k <linux-m68k@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Thorsten Glaser <tg@mirbsd.de>
Subject: Re: [PATCH] arch: m68k: include: asm: the 3rd parameter of 'insl' and 'outsl' need '<< 2'
Date: Wed, 05 Jun 2013 19:24:48 +1200 [thread overview]
Message-ID: <51AEE7C0.9060206@biophys.uni-duesseldorf.de> (raw)
In-Reply-To: <51AE87DF.5000301@asianux.com>
Chen,
> On 06/03/2013 06:48 PM, Geert Uytterhoeven wrote:
>
>>>>>> This _only_ applies to use of insl/outsl macros in parport_pc.h, which
>>>>>> is only used by Q40 on m68k. I see no reason to change anything in io.h
>>>>>> to cope with this warning.
>>>>>>
>
> I guess your meaning is :
>
> ----------------------------diff begin----------------------------------
>
> diff --git a/arch/m68k/include/asm/parport.h b/arch/m68k/include/asm/parport.h
> index 5ea75e6..dd1672a 100644
> --- a/arch/m68k/include/asm/parport.h
> +++ b/arch/m68k/include/asm/parport.h
> @@ -11,9 +11,20 @@
> #ifndef _ASM_M68K_PARPORT_H
> #define _ASM_M68K_PARPORT_H 1
>
> +#ifdef CONFIG_Q40 /* for Q40, need redefine insl/outsl */
> +
> +#ifdef insl
> +#undef insl
> +#endif
> #define insl(port,buf,len) isa_insb(port,buf,(len)<<2)
> +
> +#ifdef outsl
> +#undef outsl
> +#endif
> #define outsl(port,buf,len) isa_outsb(port,buf,(len)<<2)
>
> +#endif /* CONFIG_Q40 */
> +
> /* no dma, or IRQ autoprobing */
> static int parport_pc_find_isa_ports (int autoirq, int autodma);
> static int parport_pc_find_nonpci_ports (int autoirq, int autodma)
>
> ----------------------------diff end------------------------------------
>
No need for the #ifdef CONFIG_Q40 - Q40 is the only m68k subarch that
builds the parport_pc module (which includes parport.h), IIRC. Is that
correct, Thorsten?
>>>> It sounds reasonable.
>>>>
>>>> And excuse me, could you provide the related link directly ? I don't
>>>> know how to see the detail of 'loom.20130511T171757-995@post.gmane.org'.
>>>>
>> http://www.spinics.net/lists/linux-m68k/msg06041.html
>>
>
> OK, thanks. And sorry for replying late (during these days, I have to
> do another things, and almost can not connect net).
>
>
Thanks indeed for the link, Geert. I haven't yet had time to test
whether the io.h patch would interfere with Atari IDE or other drivers's
use of these macros - maybe this weekend.
> It seems already has another related patch for it, and it is just
> applying.
>
> So need I send it again ?
>
>
I think Thorsten submitted a patch to that effect? If so, yours should
not be necessary.
Regards,
Michael
next prev parent reply other threads:[~2013-06-05 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 9:39 Chen Gang
2013-05-30 18:52 ` Geert Uytterhoeven
2013-06-01 0:26 ` schmitz
2013-06-01 0:38 ` schmitz
2013-06-03 9:40 ` Chen Gang
2013-06-03 10:48 ` Geert Uytterhoeven
2013-06-05 0:35 ` Chen Gang
2013-06-05 7:24 ` schmitz [this message]
2013-06-06 8:38 ` Chen Gang
2013-06-06 11:52 ` Thorsten Glaser
2013-06-06 22:47 ` Michael Schmitz
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=51AEE7C0.9060206@biophys.uni-duesseldorf.de \
--to=schmitz@biophys.uni-duesseldorf.de \
--cc=gang.chen@asianux.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=schmitz@debian.org \
--cc=tg@mirbsd.de \
/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®