From: Bernd Petrovitsch <bernd@firmix.at>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Kernel Janitors List <kernel-janitors@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h)
Date: Fri, 16 Mar 2007 18:15:50 +0100 [thread overview]
Message-ID: <1174065350.26648.58.camel@tara.firmix.at> (raw)
In-Reply-To: <45FACF2E.3040600@student.ltu.se>
On Fri, 2007-03-16 at 18:09 +0100, Richard Knutsson wrote:
> Bernd Petrovitsch wrote:
> > On Fri, 2007-03-16 at 16:24 +0100, Richard Knutsson wrote:
> > [...]
> >
> >> more readable). The big problem is, where to put it? Seems wrong to put
> >> in <linux/string.h> since it appear to be a replica of userspace's
> >> <string.h> (otherwise, why put mem*-functions in there?).
> >>
> >
> > memcpy(3) and memcmp(3) are also there in user-space.
> >
> Did I miss something or did you just restate what was stated? (If it was
> not a replica, I think the mem*-functions would be better placed in
> memory.h, or such)
Ah, I misunderstood it as if you wonder why mem*() functions in
<string.h>.
Sorry.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2007-03-16 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45F95351.60308@student.ltu.se>
[not found] ` <39e6f6c70703152036m778ea054gf32723d0eda2be68@mail.gmail.com>
2007-03-16 15:24 ` [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h) (was: Re: [KJ] [RFC] A need for a "yesno"-function?) Richard Knutsson
2007-03-16 16:33 ` Bernd Petrovitsch
2007-03-16 17:09 ` Richard Knutsson
2007-03-16 17:15 ` Bernd Petrovitsch [this message]
2007-03-16 23:20 ` Jan Engelhardt
2007-03-17 0:59 ` [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h) Richard Knutsson
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=1174065350.26648.58.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=acme@ghostprotocols.net \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricknu-0@student.ltu.se \
/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®