From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390: export ipl device parameters
Date: Mon, 26 Sep 2005 11:15:37 +0200 [thread overview]
Message-ID: <20050926091537.GA10062@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20050924004801.GB21283@suse.de>
Hi,
> > +#ifdef CONFIG_SYSFS
> Does anyone build a s390 kernel without sysfs? You can probably just
> drop this ifdef.
Yes, you're right.
> > +DEFINE_IPL_ATTR(lun, "0x%016llx\n", (unsigned long long)
> > +DEFINE_IPL_ATTR(bootprog, "%lld\n", (unsigned long long)
> Why have a format field, if you only use the same format?
I use two different formats (hexadecimal and decimal).
> > + __ATTR(device, S_IRUGO, ipl_device_show, NULL);
> Why not use __ATTR_RO() like you did above?
The name of the attribute is supposed to be 'device'. If I would use
__ATTR_RO it stringifies the first parameter and the result would be
'ipl_device' because of the function name I use.
Otherwise I would have to rename my function, which is something I
don't want to do. Somehow __ATTR_RO doesn't fit.
> > +#define IPL_PARMBLOCK_ORIGIN 0x2000
> You are just directly addressing memory with this address, right?
Yes.
> Shouldn't you iomap it or something first?
No, we don't have memory mapped IO on S390.
How about this:
From: Heiko Carstens <heiko.carstens@de.ibm.com>
Remove unnecessary ifdef + unused variable.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
diffstat:
arch/s390/kernel/setup.c | 6 ------
1 file changed, 6 deletions(-)
diff -urN a/arch/s390/kernel/setup.c b/arch/s390/kernel/setup.c
--- a/arch/s390/kernel/setup.c 2005-09-26 10:48:31.000000000 +0200
+++ b/arch/s390/kernel/setup.c 2005-09-26 11:01:12.000000000 +0200
@@ -686,8 +686,6 @@
.show = show_cpuinfo,
};
-#ifdef CONFIG_SYSFS
-
#define DEFINE_IPL_ATTR(_name, _format, _value) \
static ssize_t ipl_##_name##_show(struct subsystem *subsys, \
char *page) \
@@ -847,7 +845,6 @@
static int __init
ipl_device_sysfs_register(void) {
- struct attribute_group *attr_group;
int rc;
rc = firmware_register(&ipl_subsys);
@@ -868,12 +865,9 @@
default:
sysfs_create_group(&ipl_subsys.kset.kobj,
&ipl_unknown_attr_group);
- attr_group = &ipl_unknown_attr_group;
break;
}
return 0;
}
__initcall(ipl_device_sysfs_register);
-
-#endif /* CONFIG_SYSFS */
next prev parent reply other threads:[~2005-09-26 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 9:50 Heiko Carstens
2005-09-24 0:48 ` Greg KH
2005-09-26 9:15 ` Heiko Carstens [this message]
2005-09-26 9:24 ` Greg KH
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=20050926091537.GA10062@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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