From: FabF <fabian.frederick@skynet.be>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.7-rc1-mm1] lp int copy_to_user replaced
Date: Thu, 27 May 2004 20:06:55 +0200 [thread overview]
Message-ID: <1085681215.2070.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20040527180118.GQ12308@parcelfarce.linux.theplanet.co.uk>
On Thu, 2004-05-27 at 20:01, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> On Thu, May 27, 2004 at 07:32:08PM +0200, FabF wrote:
> > Andrew,
> >
> > Here's a patch to have standard __put_user for integer transfers in lp
> > driver.Is it correct ?
>
> What the hell for? copy_to_user()/copy_from_user() is perfectly OK here.
>
And why the hell use generic functions when we have neat small type
exchange macros ?
FabF
next prev parent reply other threads:[~2004-05-27 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 17:32 FabF
2004-05-27 17:39 ` Arjan van de Ven
2004-05-27 17:45 ` FabF
2004-05-27 17:43 ` Chris Wright
2004-05-27 18:01 ` viro
2004-05-27 18:06 ` FabF [this message]
2004-05-27 18:13 ` viro
2004-05-27 19:01 ` Andrew Morton
2004-05-27 18:15 ` Davide Libenzi
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=1085681215.2070.27.camel@localhost.localdomain \
--to=fabian.frederick@skynet.be \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®