From: David Miller <davem@davemloft.net>
To: keil@b1-systems.de
Cc: tilman@imap.cc, adobriyan@gmail.com, akpm@linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] proc_fops: convert drivers/isdn/ to seq_file
Date: Thu, 14 Jan 2010 03:11:14 -0800 (PST) [thread overview]
Message-ID: <20100114.031114.257830077.davem@davemloft.net> (raw)
In-Reply-To: <1263467281.28429@pingi>
From: Karsten Keil <keil@b1-systems.de>
Date: Thu, 14 Jan 2010 11:27:45 +0100
> 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>
> Signed-off-by: Tilman Schmidt <tilman@imap.cc>
> Signed-off-by: Karsten Keil <keil@b1-systems.de>
Applied.
prev parent reply other threads:[~2010-01-14 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 10:27 [PATCH] proc_fops: convert drivers/isdn/ to seq_file Karsten Keil
2010-01-14 11:11 ` 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=20100114.031114.257830077.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=keil@b1-systems.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).