public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: schmitz <schmitz@biophys.uni-duesseldorf.de>
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@lists.linux-m68k.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] arch: m68k: include: asm: the 3rd parameter of 'insl' and 'outsl' need '<< 2'
Date: Mon, 03 Jun 2013 17:40:02 +0800	[thread overview]
Message-ID: <51AC6472.3060606@asianux.com> (raw)
In-Reply-To: <51A94281.7050708@biophys.uni-duesseldorf.de>

On 06/01/2013 08:38 AM, schmitz wrote:
> All,
>> Geert ,
>>>>
>>>> The related git number:
>>>>   for parport.h: "4914802 m68k,m68knommu: merge header files" in 2009
>>>>   for io_mm.h: "84b16b7 m68k/atari: ROM port ISA adapter support" in
>>>> Apr 6 2013
>>>>
>>>> The related warning (make EXTRA_CFLAG=-W ARCH=m68k allmodconfig):
>>>>   arch/m68k/include/asm/parport.h:14:0: warning: "insl" redefined
>>>> [enabled by default]
>>>>   arch/m68k/include/asm/io_mm.h:403:0: note: this is the location of
>>>> the previous definition
>>>>   arch/m68k/include/asm/parport.h:15:0: warning: "outsl" redefined
>>>> [enabled by default]
>>>>   arch/m68k/include/asm/io_mm.h:406:0: note: this is the location of
>>>> the previous definition
>>>>     
>> Is that the same problem Thorsten reported recently? parport.h should
>> either use what the arch io.h include defined, or (in the case of Q40
>> on m68k) undef and redefine as needed.
> It appears this is the same issue, see message ID
> loom.20130511T171757-995@post.gmane.org to linux-m68k (May 12th, by
> Thorsten Glaser).
> 
> 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.

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'.


Thanks.
-- 
Chen Gang

Asianux Corporation

  parent reply	other threads:[~2013-06-03  9:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  9:39 [PATCH] arch: m68k: include: asm: the 3rd parameter of 'insl' and 'outsl' need '<< 2' Chen Gang
2013-05-30 18:52 ` Geert Uytterhoeven
2013-06-01  0:26   ` schmitz
2013-06-01  0:38     ` schmitz
2013-06-01  0:38       ` schmitz
2013-06-03  9:40       ` Chen Gang [this message]
2013-06-03 10:48         ` Geert Uytterhoeven
2013-06-03 10:48           ` Geert Uytterhoeven
2013-06-05  0:35           ` Chen Gang
2013-06-05  0:35             ` Chen Gang
2013-06-05  7:24             ` schmitz
2013-06-06  8:38               ` Chen Gang
2013-06-06  8:38                 ` Chen Gang
2013-06-06 11:52               ` Thorsten Glaser
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=51AC6472.3060606@asianux.com \
    --to=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@lists.linux-m68k.org \
    --cc=sam@ravnborg.org \
    --cc=schmitz@biophys.uni-duesseldorf.de \
    --cc=schmitz@debian.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