public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
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 02:24:45 -0700	[thread overview]
Message-ID: <20050926092445.GA4791@suse.de> (raw)
In-Reply-To: <20050926091537.GA10062@osiris.boeblingen.de.ibm.com>

On Mon, Sep 26, 2005 at 11:15:37AM +0200, Heiko Carstens wrote:
> 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).

Sorry, I was referring to the (unsigned long long) duplication there,
not the format field.

> > > +	__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.

Ok, fair enough.

> > > +#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.

Neither do we on x86, yet we force everyone to use the proper function
calls, for when that code is then ported to other arches.  No reason
s390 should be alone with getting away from that :)

> How about this:
> 
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
> 
> Remove unnecessary ifdef + unused variable.

<snip>

Looks fine to me.

thanks,

greg k-h

      reply	other threads:[~2005-09-26  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  9:50 [PATCH] s390: export ipl device parameters Heiko Carstens
2005-09-24  0:48 ` Greg KH
2005-09-26  9:15   ` Heiko Carstens
2005-09-26  9:24     ` Greg KH [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=20050926092445.GA4791@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=heiko.carstens@de.ibm.com \
    --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