From: Jiri Kosina <jkosina@suse.cz>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-input@vger.kernel.org,
Alexander <pikachu@millennium.udm.ru>,
bunk@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix build failure in hiddev_ioctl with gcc 3.2
Date: Mon, 3 Mar 2008 11:36:01 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0803031127530.15209@jikos.suse.cz> (raw)
In-Reply-To: <20080302231209.36e2c619@hyperion.delvare>
On Sun, 2 Mar 2008, Jean Delvare wrote:
> Fix build failure in hiddev_ioctl with gcc 3.2:
> http://bugzilla.kernel.org/show_bug.cgi?id=10121
> The trick is to move the handling of ioctls which need to allocate
> memory to separate functions.
Hmm, I can't say I like doing these shuffles just because of gcc 3.2
behvior ... but as there are apparently already other patches in Linus'
tree which did just that, I will have to follow this precedent.
Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2008-03-03 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 22:12 [PATCH] Fix build failure in hiddev_ioctl with gcc 3.2 Jean Delvare
2008-03-03 10:36 ` Jiri Kosina [this message]
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=Pine.LNX.4.64.0803031127530.15209@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=bunk@kernel.org \
--cc=khali@linux-fr.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pikachu@millennium.udm.ru \
/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).