From: Claudio Scordino <claudio@evidence.eu.com>
To: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Cc: Rick Bronson <rick@efn.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-serial@vger.kernel.org
Subject: RS485: ioctls defined twice ?
Date: Sun, 15 Aug 2010 16:22:13 +0200 [thread overview]
Message-ID: <4C67F815.8020808@evidence.eu.com> (raw)
Hi all,
is there any reason why ioctls TIOCGRS485 and TIOCSRS485 are defined (with the same values) in both include/asm-generic/ioctls.h and arch/arm/include/asm/ioctls.h ?
The same happens also for avr32, powerpc and cris (which, however, defines a different value for TIOCSRS485).
Is it duplicated code ?
Or should these values stay in both asm/ioctls.h and asm-generic/ioctls.h ?
Many thanks,
Claudio
next reply other threads:[~2010-08-15 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 14:22 Claudio Scordino [this message]
2010-08-15 15:38 ` RS485: ioctls defined twice ? Russell King - ARM Linux
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=4C67F815.8020808@evidence.eu.com \
--to=claudio@evidence.eu.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=rick@efn.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;
as well as URLs for NNTP newsgroup(s).