From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: isdn@linux-pingi.de, netdev@vger.kernel.org, adobriyan@gmail.com,
tilman@imap.cc
Subject: Re: [patch 1/2] proc_fops: convert drivers/isdn/ to seq_file
Date: Sun, 03 Jan 2010 21:26:48 -0800 (PST) [thread overview]
Message-ID: <20100103.212648.225653590.davem@davemloft.net> (raw)
In-Reply-To: <200912220025.nBM0PVBC005140@imap1.linux-foundation.org>
From: akpm@linux-foundation.org
Date: Mon, 21 Dec 2009 16:25:31 -0800
> From: Alexey Dobriyan <adobriyan@gmail.com>
>
> Convert code away from ->read_proc/->write_proc interfaces. Switch to
> proc_create()/proc_create_data() which make addition of proc entries
> reliable wrt NULL ->proc_fops, NULL ->data and so on.
>
> Problem with ->read_proc et al is described here commit
> 786d7e1612f0b0adb6046f19b906609e4fe8b1ba "Fix rmmod/read/write races in
> /proc entries"
>
> [akpm@linux-foundation.org: CONFIG_PROC_FS=n build fix]
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> Cc: Karsten Keil <isdn@linux-pingi.de>
> Cc: Tilman Schmidt <tilman@imap.cc>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Tilman has requested some fixes to the documentation text.
So I'm waiting for a fixed up version.
prev parent reply other threads:[~2010-01-04 5:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 0:25 [patch 1/2] proc_fops: convert drivers/isdn/ to seq_file akpm
2009-12-23 12:30 ` Tilman Schmidt
2010-01-05 21:19 ` Alexey Dobriyan
2010-01-10 18:42 ` Tilman Schmidt
2010-01-10 21:29 ` David Miller
2010-01-10 23:33 ` Karsten Keil
2010-01-14 1:37 ` [ISDN] " Karsten Keil
2010-01-14 1:53 ` David Miller
2010-01-14 2:39 ` Karsten Keil
2010-01-14 2:43 ` David Miller
2010-01-14 4:29 ` David Miller
2010-01-14 11:01 ` David Miller
2010-01-04 5:26 ` David Miller [this message]
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=20100103.212648.225653590.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=isdn@linux-pingi.de \
--cc=netdev@vger.kernel.org \
--cc=tilman@imap.cc \
/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;
as well as URLs for NNTP newsgroup(s).