From: Jaeden Amero <jaeden.amero@ni.com>
To: fengguang.wu@intel.com
Cc: linux-next@vger.kernel.org, sfr@canb.auug.org.au,
gregkh@linuxfoundation.org, alan@linux.intel.com,
kernel-janitors@vger.kernel.org, linux-serial@vger.kernel.org,
Jaeden Amero <jaeden.amero@ni.com>
Subject: Re: [tty:tty-next 10/16] fs/compat_ioctl.c:869:1: error: 'TIOCSRS485' undeclared here (not in a function)
Date: Mon, 24 Sep 2012 10:39:44 -0500 [thread overview]
Message-ID: <1348501185-23657-1-git-send-email-jaeden.amero@ni.com> (raw)
In-Reply-To: <20120922005021.GM5959@localhost>
On Sat, 22 Sep 2012 08:50:21 +0800, Fengguang Wu wrote:
> FYI, kernel build failed on
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
> tty-next
> head: ac57e7f38ea6fe7358cd0b7a2f2d21aef5ab70cd
> commit: 84c3b84860440a9e3a3666c14112f41311b8f623 [10/16]
> compat_ioctl: Add RS-485 IOCTLs to the list
> config: mips-fuloong2e_defconfig
>
> All related error/warning messages:
>
> fs/compat_ioctl.c:869:1: error: 'TIOCSRS485' undeclared here (not in
> a function)
> fs/compat_ioctl.c:870:1: error: 'TIOCGRS485' undeclared here (not in
> a function)
I could fix this by defining these IOCTLs for all architectures that
don't have them yet, but I'm unsure of what values to give them or why
MIPS isn't using 'include/asm-generic/ioctls.h'.
Perhaps it is better to leave adding those IOCTLs up to those who add
the first RS-485 capable driver for that platform and to wrap the use
of these defines in compat_ioctl.c with #ifdefs, as I've done in this
patch. What do you think is best?
Cheers,
Jaeden Amero
Jaeden Amero (1):
compat_ioctl: Avoid using undefined RS-485 IOCTLs
fs/compat_ioctl.c | 4 ++++
1 file changed, 4 insertions(+)
--
1.7.12
next prev parent reply other threads:[~2012-09-24 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 0:50 [tty:tty-next 10/16] fs/compat_ioctl.c:869:1: error: 'TIOCSRS485' undeclared here (not in a function) Fengguang Wu
2012-09-24 15:39 ` Jaeden Amero [this message]
2012-09-24 15:39 ` [PATCH] compat_ioctl: Avoid using undefined RS-485 IOCTLs Jaeden Amero
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=1348501185-23657-1-git-send-email-jaeden.amero@ni.com \
--to=jaeden.amero@ni.com \
--cc=alan@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).