From: Rusty Russell <rusty@rustcorp.com.au>
To: Chris Wilson <chris@qwirx.com>
Cc: mikejc@us.ibm.com,
Linux Kernel Janitors
<kernel-janitor-discuss@lists.sourceforge.net>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] create_proc_read_entry in arch/ppc/iSeries/rtc.c
Date: Mon, 02 Dec 2002 15:47:35 +1100 [thread overview]
Message-ID: <20021202053207.348322C340@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 18 Nov 2002 19:19:00 -0000." <Pine.LNX.4.44.0211181909260.15091-200000@top.qwarx.com>
In message <Pine.LNX.4.44.0211181909260.15091-200000@top.qwarx.com> you write:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
> Send mail to mime@docserver.cac.washington.edu for more info.
>
> ---1044231485-1031583466-1037559336=:16702
> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
> Content-ID: <Pine.LNX.4.44.0211171855531.16702@top.qwarx.com>
>
> Dear Sir,
>
> As part of the Linux Kernel Janitors audit of misc_register usage,
> I would like to submit my related patch to arch/ppc/iSeries/rtc.c.
> --- linux-2.5.47/arch/ppc/iSeries/rtc.c Mon Nov 11 03:28:15 2002
> +++ linux-2.5.47-chris/arch/ppc/iSeries/rtc.c Sun Nov 17 21:29:25 2002
> static int __init rtc_init(void)
> {
> - if (misc_register(&rtc_dev))
> + if (misc_register(&rtc_dev)) {
> + printk(KERN_ERR "iSeries-rtc: cannot register misc device.\n");
> return -ENODEV;
> - create_proc_read_entry ("driver/rtc", 0, 0, rtc_read_proc, NULL);
> + }
But this cannot sanely fail (it cannot be a module). It's probably
better to do something like inserting a check inside misc_register and
create_proc_read_entry:
BUG_ON(booting && failed);
Maybe even create a "NOFAIL_ON_BOOT(condition)" which does this for
you.
Thoughts?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
parent reply other threads:[~2002-12-02 5:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.44.0211181909260.15091-200000@top.qwarx.com>]
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=20021202053207.348322C340@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=chris@qwirx.com \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikejc@us.ibm.com \
--cc=torvalds@transmeta.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
Powered by JetHome