public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-hotplug@sf-tec.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code
Date: Wed, 18 May 2005 13:43:33 +0000	[thread overview]
Message-ID: <200505181543.33888@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <200505131003.18143@bilbo.math.uni-mannheim.de>

Prarit Bhargava wrote:
> Greg KH wrote:
> > On Tue, May 17, 2005 at 11:41:01AM -0400, Prarit Bhargava wrote:
> >>Rolf Eike Beer wrote:
> >>>>+	sprintf(bss_hotplug_slot->name, "module_%c%c%c%c%.2d_b_%d_s_%d",
> >>>>+	 '0'+RACK_GET_CLASS(MODULE_GET_RACK(pcibus_info->pbi_moduleid)),
> >>>>+	 '0'+RACK_GET_GROUP(MODULE_GET_RACK(pcibus_info->pbi_moduleid)),
> >>>>+		'0'+RACK_GET_NUM(MODULE_GET_RACK(pcibus_info->pbi_moduleid)),
> >>>>+		MODULE_GET_BTCHAR(pcibus_info->pbi_moduleid),
> >>>>+		MODULE_GET_BPOS(pcibus_info->pbi_moduleid),
> >>>>+		((int)pcibus_info->pbi_buscommon.bs_persist_busnum) & 0xf,
> >>>>+		device + 1);
> >>>
> >>>*eek* Sorry, but that looks really ugly. Wouldn't it be enough do name
> >>> it like the device that would be in slot, something like
> >>> DOMAIN_BUS_SLOT and maybe one extra number?
> >>
> >>Unfortunately, yes, the longer name is prefered in this case.  The rack
> >>class
> >>ID, etc., are need to identify locations on the Altix platform.
> >
> > No, use additional sysfs files if you need to export this kind of
> > information to the user somehow.  I think IBM already does this in their
> > drivers in a sane manner (so you might want to copy them, as they have
> > already modified the userspace code to handle those sysfs files...)
>
> Okay -- I'll go with Eike's suggestion above.  D_B_S + 1 number.

D_B_S alone should be a unique identifier, so please don't use anything more 
if you don't need it to make the slot name unique.

> >>>>+	if (action = PCI_REQ_SLOT_ELIGIBLE && rc = PCI_SLOT_ALREADY_DOWN) {
> >>>
> >>>I would feel better if you add extra braces around the tests, but I'm
> >>>probably just a bit paranoid about this things. Greg?
> >>
> >>I was asked to remove the braces in an earlier version.  I too would
> >> prefer to have them but am going with current comments on the code.
> >
> > Who asked you to remove the extra braces?  It was not me.  If you like
> > them, please add them, I feel more comfortable with them too.
>
> Hrmm ... I can't remember.  But someone did definately tell me that they
> were not required.

They are not required (at least not for the compiler). But brain v0.5 can 
parse it much better if they are in there ;)

Eike

  parent reply	other threads:[~2005-05-18 13:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  8:03 [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Rolf Eike Beer
2005-05-17 15:41 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-17 20:17 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Greg KH
2005-05-18 11:33 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-18 11:42 ` Prarit Bhargava
2005-05-18 13:43 ` Rolf Eike Beer [this message]
2005-05-18 13:46 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Rolf Eike Beer
2005-05-18 13:57 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-18 14:06 ` Prarit Bhargava
2005-05-18 15:20 ` Prarit Bhargava
2005-05-18 16:23 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Greg KH
2005-05-18 16:41 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-18 16:52 ` Prarit Bhargava
2005-05-18 16:54 ` Prarit Bhargava
2005-05-18 17:06 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Greg KH
2005-05-19  7:56 ` Rolf Eike Beer
2005-05-19 13:05 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-19 15:13 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Greg KH
2005-05-20 12:11 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-20 18:26 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Greg KH
2005-05-20 23:47 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava
2005-05-21  0:24 ` Prarit Bhargava
2005-05-21  3:59 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver - SN Hotplug Driver code Greg KH
2005-05-22  1:13 ` [Pcihpd-discuss] [PATCH 5/6]: hotplug/ia64: SN Hotplug Driver Prarit Bhargava

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=200505181543.33888@bilbo.math.uni-mannheim.de \
    --to=eike-hotplug@sf-tec.de \
    --cc=linux-ia64@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