From: Oleg Verych <olecom@flower.upol.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
Trent Piepho <xyzzy@speakeasy.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [RFC PATCH 1/3] Add ability to keep track of callers of symbol_(get|put)
Date: Sun, 11 Mar 2007 22:12:27 +0100 [thread overview]
Message-ID: <E1HQVL9-0007nM-I0@flower> (raw)
In-Reply-To: <20070311000938.80202418.akpm@linux-foundation.org>
> From: Andrew Morton
> Newsgroups: gmane.linux.kernel
> Subject: Re: [RFC PATCH 1/3] Add ability to keep track of callers of symbol_(get|put)
> Date: Sun, 11 Mar 2007 00:09:38 -0800
>
>> On Sat, 10 Mar 2007 02:31:35 -0200 Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
>> From: Trent Piepho <xyzzy@speakeasy.org>
>>
>> When a module uses symbol_get() to increase the ref count of another
>> module, there is no record what module called symbol_get(). A module
>> can
>> show up as having other users, but there is no way to tell who those
>> users are.
>>
>> This adds that ability to symbol_put() and symbol_get().
>
> One day I'll write a script which unwordwraps patches and then you'll all
> need to find new ways of torturing me.
I don't support twisted patches, but before they will be resent, because
word wrapping may lead to 80-colums rule, please find useful this:
sed -r '
# assume only line started from [+-] got wrapped
# start what ever first line
/^[-+]/{
:more;
# append next line, to check wrapped addition
N;
# if it is one, i.e starts not with [ \t+-], '@@' or 'diff'
# do "\n" -> " "
s_\n([^d@ \t+-])_ \1_g;
# loop until find one(addition), because line(s) already here
T more;
# special case of empty line
s_\n$_&_
t more;
b;
};'
____
next prev parent reply other threads:[~2007-03-11 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 4:31 [RFC PATCH 1/3] Add ability to keep track of callers of symbol_(get|put) Mauro Carvalho Chehab
2007-03-11 2:29 ` Rusty Russell
2007-03-11 8:09 ` Andrew Morton
2007-03-11 21:12 ` Oleg Verych [this message]
2007-03-12 14:07 ` Trent Piepho
2007-03-12 22:13 ` Rusty Russell
2007-03-13 6:33 ` Trent Piepho
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=E1HQVL9-0007nM-I0@flower \
--to=olecom@flower.upol.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=xyzzy@speakeasy.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