mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Young <hidave.darkstar@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/07] kernel.h string cleanup
Date: Fri, 26 Feb 2010 15:33:20 +0800	[thread overview]
Message-ID: <a8e1da1002252333g6e8bf94crba465c59c0cbc07a@mail.gmail.com> (raw)
In-Reply-To: <b6fcc0a1002252315k1fd5360ehf5ea33566c19515d@mail.gmail.com>

On Fri, Feb 26, 2010 at 3:15 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> On Fri, Feb 26, 2010 at 3:14 AM, Dave Young <hidave.darkstar@gmail.com> wrote:
>> Yeah, same question, then where should they go?
>
> Should I hand a patch to you, so you can repost it?

Please, if you think spliting is not necessary, you can just say that,
or feel free to send a patch.

>
>> I think string.h is fine.
>
> It obviously isn't fine.
>
> Why all of sudden kernel.h split when kernel.h is for simple misc stuff
> for which there is no other place.
>

It will be better to move some of them to proper place instead of kernel.h

-- 
Regards
dave

  reply	other threads:[~2010-02-26  7:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 15:53 Dave Young
2010-02-25 18:55 ` Alexey Dobriyan
2010-02-26  1:14   ` Dave Young
2010-02-26  7:15     ` Alexey Dobriyan
2010-02-26  7:33       ` Dave Young [this message]
2010-02-26  7:42         ` Joe Perches
2010-02-26  9:55           ` Dave Young
2010-02-26  9:58             ` Alexey Dobriyan
2010-02-26 10:51               ` Dave Young
2010-02-26 14:27             ` Steven Rostedt
2010-02-27  9:55               ` Dave Young
2010-02-27 10:20       ` Frederic Weisbecker

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=a8e1da1002252333g6e8bf94crba465c59c0cbc07a@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 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®