public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takenori Nagano <t-nagano@ah.jp.nec.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, vgoyal@in.ibm.com,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	k-miyoshi@cb.jp.nec.com, kexec@lists.infradead.org,
	Bernhard Walle <bwalle@suse.de>, Keith Owens <kaos@ocs.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	kdb@oss.sgi.com
Subject: Re: [PATCH 1/2] add tunable_notifier function ,take2
Date: Thu, 25 Oct 2007 17:02:12 +0900	[thread overview]
Message-ID: <47204D84.1060706@ah.jp.nec.com> (raw)
In-Reply-To: <20071024111629.3e28b452.rdunlap@xenotime.net>

Randy Dunlap wrote:
> On Thu, 18 Oct 2007 17:53:00 +0900 Takenori Nagano wrote:
> 
>> This patch adds new notifier function tunable_notifier_chain. Its base is
>> atomic_notifier_chain.
>>
>> Thanks,
>>
>> ---
>>
>> Signed-off-by: Takenori Nagano <t-nagano@ah.jp.nec.com>
>>
>> ---
>> diff -uprN linux-2.6.23.orig/kernel/sys.c linux-2.6.23/kernel/sys.c
>> --- linux-2.6.23.orig/kernel/sys.c	2007-10-10 05:31:38.000000000 +0900
>> +++ linux-2.6.23/kernel/sys.c	2007-10-18 10:08:52.728000000 +0900
>> @@ -38,6 +38,7 @@
>>  #include <linux/syscalls.h>
>>  #include <linux/kprobes.h>
>>  #include <linux/user_namespace.h>
>> +#include <linux/debugfs.h>
>>  
>>  #include <asm/uaccess.h>
>>  #include <asm/io.h>
>> @@ -393,6 +394,243 @@ int blocking_notifier_call_chain(struct 
>>  EXPORT_SYMBOL_GPL(blocking_notifier_call_chain);
> 
>> +/**
>> + *	tunable_atomic_notifier_chain_register
>> + *				- Add notifier to an tunable notifier chain
> 
> Function name & short description must be on one (long?) line.  :(

OK. I'll fix next version.

>> +
>> +int __kprobes __tunable_atomic_notifier_call_chain(
>> +					struct tunable_atomic_notifier_head *nh,
>> +					unsigned long val, void *v,
>> +					int nr_to_call, int *nr_calls)
>> +{
>> +	int ret;
>> +
>> +	rcu_read_lock();
>> +	ret = notifier_call_chain(&nh->head, val, v, nr_to_call, nr_calls);
>> +	rcu_read_unlock();
>> +	return ret;
>> +}
>> +
>> +EXPORT_SYMBOL_GPL(__tunable_atomic_notifier_call_chain);
> 
> Blank line is usually omitted before EXPORT_SYMBOL....

OK. I'll fix, too.

Thanks,
  Takenori

> ---
> ~Randy
> 
> 

  reply	other threads:[~2007-10-25  8:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4716FFDB.7090502@ah.jp.nec.com>
2007-10-18  6:45 ` [PATCH 1/2] add tunable_notifier function ,take2 Takenori Nagano
2007-10-18  6:45 ` [PATCH 2/2] implement new notifier function to panic_notifier_list ,take2 Takenori Nagano
2007-10-18  8:53 ` [PATCH 1/2] add tunable_notifier function ,take2 Takenori Nagano
2007-10-24 18:16   ` Randy Dunlap
2007-10-25  8:02     ` Takenori Nagano [this message]
2007-10-18  8:53 ` [PATCH 2/2] implement new notifier function to panic_notifier_list ,take2 Takenori Nagano
2007-10-24 18:11   ` Randy Dunlap
2007-10-25  7:59     ` Takenori Nagano
     [not found] <47FF0EA5.8090804@ah.jp.nec.com>
2008-04-11  7:53 ` [PATCH 1/2] add tunable_notifier function ,take2 Takenori Nagano
2008-04-11 19:55   ` Greg KH

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=47204D84.1060706@ah.jp.nec.com \
    --to=t-nagano@ah.jp.nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=k-miyoshi@cb.jp.nec.com \
    --cc=kaos@ocs.com.au \
    --cc=kdb@oss.sgi.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=vgoyal@in.ibm.com \
    /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