All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Kernel Janitors List <kernel-janitors@lists.osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [KJ] [RFC] A need for "yesno"-function? (and "cleanup" of
Date: Fri, 16 Mar 2007 17:09:02 +0000	[thread overview]
Message-ID: <45FACF2E.3040600@student.ltu.se> (raw)
In-Reply-To: <1174062833.26648.56.camel@tara.firmix.at>

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)

Richard Knutsson

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

WARNING: multiple messages have this Message-ID (diff)
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Bernd Petrovitsch <bernd@firmix.at>
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) (was: Re: [KJ] [RFC] A need for a "yesno"-function?)
Date: Fri, 16 Mar 2007 18:09:02 +0100	[thread overview]
Message-ID: <45FACF2E.3040600@student.ltu.se> (raw)
In-Reply-To: <1174062833.26648.56.camel@tara.firmix.at>

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)

Richard Knutsson


  reply	other threads:[~2007-03-16 17:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 14:08 [KJ] [RFC] A need for a "yesno"-function? Richard Knutsson
2007-03-16  3:36 ` Arnaldo Carvalho de Melo
2007-03-16 15:24   ` [KJ] [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h) Richard Knutsson
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     ` [KJ] [RFC] A need for "yesno"-function? (and "cleanup" of Bernd Petrovitsch
2007-03-16 16:33       ` [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h) (was: Re: [KJ] [RFC] A need for a "yesno"-function?) Bernd Petrovitsch
2007-03-16 17:09       ` Richard Knutsson [this message]
2007-03-16 17:09         ` Richard Knutsson
2007-03-16 17:15         ` [KJ] [RFC] A need for "yesno"-function? (and "cleanup" of Bernd Petrovitsch
2007-03-16 17:15           ` [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h) Bernd Petrovitsch
2007-03-16 23:20     ` [KJ] [RFC] A need for "yesno"-function? (and "cleanup" of Jan Engelhardt
2007-03-16 23:20       ` [RFC] A need for "yesno"-function? (and "cleanup" of kernel.h) (was: Re: [KJ] [RFC] A need for a "yesno"-function?) Jan Engelhardt
2007-03-17  0:59       ` [KJ] [RFC] A need for "yesno"-function? (and "cleanup" of Richard Knutsson
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=45FACF2E.3040600@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=acme@ghostprotocols.net \
    --cc=bernd@firmix.at \
    --cc=kernel-janitors@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.