From: Jean Delvare <jdelvare@suse.de>
To: Jordan Hargrave <jharg93@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Save SMBIOS Type 9 System Slots during DMI Scan
Date: Mon, 30 Nov 2015 12:01:27 +0100 [thread overview]
Message-ID: <1448881287.4551.11.camel@chaos.site> (raw)
In-Reply-To: <CAC1Azdck8vZEq4GCyJyL_jrzToZO4iGL-ZSdik8pkoEacJ_5xA@mail.gmail.com>
Hi Jordan,
Le Saturday 28 November 2015 à 20:54 -0600, Jordan Hargrave a écrit :
>
>
> On Sat, Nov 28, 2015 at 2:46 AM, Jean Delvare <jdelvare@suse.de>
> wrote:
> Hi Jordan,
>
> Once again: please keep the list included in your replies.
> Others may
> be able to help. Also the list is archived for later
> reference.
>
>
>
> The list wasn't in the cc:? I sent the diff with git send-email --cc
When you send the patches, the list is there. However when I review and
then you reply using your regular email client, this is HTML and list is
dropped. Not good.
>(...)
> We have a few machines in the SUSE Labs network which use PCI
> segments.
> SGI UV3000 uses segments 0000, 0001, 1000, 1001, 1002 and
> 1003, and it
> implements SMBIOS 2.7. SGI UV100 uses segments 0000, 0001,
> 1000 and
> 1001. Fujitsu PrimeQuest 2800E uses segments 0000 and 0001,
> and it
> implements SMBIOS 2.7.
>
> Also SGI Altix 450 (ia64) uses PCI segments 0001, 0002, 0011,
> 0012 and
> 0021. It doesn't seem to have a valid DMI table though.
>
> So yes, PCI bus segments are used, although not often.
>
>
> Can you send me a full dmidecode -u and lspci -vvvxxxx on those
> systems?
Sure, will send privately.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2015-11-30 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 22:02 Jordan Hargrave
2015-11-27 12:04 ` Jean Delvare
[not found] ` <CAC1AzddaBmBPpH11gDbsK=rjYTtACsK4p3C+jsuF7-m+qsDkBg@mail.gmail.com>
2015-11-28 8:46 ` Jean Delvare
[not found] ` <CAC1Azdck8vZEq4GCyJyL_jrzToZO4iGL-ZSdik8pkoEacJ_5xA@mail.gmail.com>
2015-11-30 11:01 ` Jean Delvare [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=1448881287.4551.11.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=jharg93@gmail.com \
--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®