All of lore.kernel.org
 help / color / mirror / Atom feed
From: aq <aquynh@gmail.com>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>, Jay Lan <jlan@engr.sgi.com>,
	Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
	elsa-devel <elsa-devel@lists.sourceforge.net>,
	Alexander Nyberg <alexn@dsv.su.se>
Subject: Re: [PATCH 2.6.12-rc3-mm3] connector: add a fork connector
Date: Mon, 9 May 2005 06:32:38 -0700	[thread overview]
Message-ID: <9cde8bff0505090632550f3d9e@mail.gmail.com> (raw)
In-Reply-To: <1115644436.8540.83.camel@frecb000711.frec.bull.fr>

On 5/9/05, Guillaume Thouvenin <guillaume.thouvenin@bull.net> wrote:
> ChangeLog:
> 
>   - Replace the GFP_ATOMIC flag in cn_netlink_send() by
>     GFP_KERNEL|__GFP_NOFAIL
>   - Move the following code
>         #ifdef CONFIG_FORK_CONNECTOR
>         static DEFINE_PER_CPU(unsigned long, fork_counts);
>         #endif /* CONFIG_FORK_CONNECTOR */
>     in the driver/connector/cn_fork.c file.
>   - Remove the code of fork_connector() from the header file
>     and put it in cn_fork.c

this is a good idea, because it will shrink your modification to
mainline kernel by few more lines ;-)

regards,
aq

  reply	other threads:[~2005-05-09 13:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09  8:07 [PATCH 2.6.12-rc3-mm3] connector: add a fork connector Guillaume Thouvenin
2005-05-09  9:31 ` Alexander Nyberg
2005-05-09 11:38   ` Guillaume Thouvenin
2005-05-09 11:48     ` Evgeniy Polyakov
2005-05-09 21:08       ` Andrew Morton
2005-05-09 21:43         ` Evgeniy Polyakov
2005-05-10 11:13           ` aq
2005-05-10 11:24             ` Evgeniy Polyakov
2005-05-09 12:00     ` Nick Piggin
2005-05-09 12:22     ` Alexander Nyberg
2005-05-09 12:43       ` Guillaume Thouvenin
2005-05-09 13:13 ` Guillaume Thouvenin
2005-05-09 13:32   ` aq [this message]
2005-05-09 13:57   ` Alexander Nyberg
2005-05-11 11:44     ` Guillaume Thouvenin
2005-05-10 11:18   ` Guillaume Thouvenin

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=9cde8bff0505090632550f3d9e@mail.gmail.com \
    --to=aquynh@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alexn@dsv.su.se \
    --cc=elsa-devel@lists.sourceforge.net \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jlan@engr.sgi.com \
    --cc=johnpol@2ka.mipt.ru \
    --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.