From: Arjan van de Ven <arjan@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: EDAC, core EDAC support code
Date: Sun, 16 Oct 2005 10:25:24 +0200 [thread overview]
Message-ID: <1129451124.2911.6.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1129403217.17923.22.camel@localhost.localdomain>
> +
> +static ctl_table mc_table[] = {
> + {-1, "panic_on_ue", &panic_on_ue,
> + sizeof(int), 0644, NULL, proc_dointvec},
> + {-2, "log_ue", &log_ue,
> + sizeof(int), 0644, NULL, proc_dointvec},
> + {-3, "log_ce", &log_ce,
> + sizeof(int), 0644, NULL, proc_dointvec},
> + {-4, "poll_msec", &poll_msec,
> + sizeof(int), 0644, NULL, proc_dointvec},
> + {-7, "panic_on_pci_parity", &panic_on_pci_parity,
> + sizeof(int), 0644, NULL, proc_dointvec},
> + {-8, "check_pci_parity", &check_pci_parity,
> + sizeof(int), 0644, NULL, proc_dointvec},
> +#ifdef CONFIG_EDAC_DEBUG
> + {-9, "debug_level", &edac_debug_level,
> + sizeof(int), 0644, NULL, proc_dointvec},
> +#endif
> + {0}
> +};
why aren't these module parameters? Nowadays you can have sysfs-runtime
changable module parameters... sounds a lot nicer than adding a chunk of
sysctl stuff
> +
> +#ifdef CONFIG_PROC_FS
> +static const char *mem_types[] = {
> + [MEM_EMPTY] = "Empty",
> + [MEM_RESERVED] = "Reserved",
> + [MEM_UNKNOWN] = "Unknown",
> + [MEM_FPM] = "FPM",
> + [MEM_EDO] = "EDO",
> + [MEM_BEDO] = "BEDO",
> + [MEM_SDR] = "Unbuffered-SDR",
> + [MEM_RDR] = "Registered-SDR",
> + [MEM_DDR] = "Unbuffered-DDR",
> + [MEM_RDDR] = "Registered-DDR",
> + [MEM_RMBS] = "RMBS"
> +};
why proc? Again this sounds like a platform sysfs thing...
next prev parent reply other threads:[~2005-10-16 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 19:06 Alan Cox
2005-10-16 3:05 ` Nish Aravamudan
2005-10-16 8:25 ` Arjan van de Ven [this message]
2005-10-17 1:48 ` Doug Thompson
2005-10-17 6:38 ` Arjan van de Ven
2005-10-17 17:59 ` Alan Cox
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=1129451124.2911.6.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®