All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Narendra.K@dell.com, helgaas@kernel.org
Cc: x86@kernel.org, linux-pci@vger.kernel.org,
	Jordan.Hargrave@dell.com, Shyam.Iyer@dell.com,
	bhelgaas@google.com
Subject: Re: dmi type 0xB1 record - unknown flag
Date: Fri, 16 Jun 2017 15:25:24 +0200	[thread overview]
Message-ID: <1497619524.4126.5.camel@suse.de> (raw)
In-Reply-To: <fb0d720dc6c441539fb5130d2628158f@BLRX13MDC105.AMER.DELL.COM>

On ven., 2017-06-16 at 09:36 +0000, Narendra.K@dell.com wrote:
> Sorry for the delay. I applied the patch to the mainline kernel version 4.12-rc5 and performed sanity test on  a  DellEMC PowerEdge R730XD system. It is working as 
> expected.  'dmesg' shows the message that 'pci=bfsort' is enabled.
> 
> I also booted kernel version 4.12-rc5 with patch applied on a DellEMC PowerEdge 1950 system which is listed in the ' pciprobe_dmi_table' quicks table.
> It is working as expected and has not caused regression on this system. 'dmesg' shows the message that 'pci=bfsort' is enabled.

Thank you for testing it on real systems, this is very useful and
appreciated.

-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2017-06-16 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 12:38 dmi type 0xB1 record - unknown flag Jean Delvare
2017-06-01 13:28 ` Narendra.K
2017-06-01 16:59   ` Bjorn Helgaas
2017-06-02  9:47     ` Narendra.K
2017-06-02 14:13   ` Jean Delvare
2017-06-06  8:02     ` Narendra.K
2017-06-15 21:39     ` Bjorn Helgaas
2017-06-16  9:36       ` Narendra.K
2017-06-16 13:25         ` 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=1497619524.4126.5.camel@suse.de \
    --to=jdelvare@suse.de \
    --cc=Jordan.Hargrave@dell.com \
    --cc=Narendra.K@dell.com \
    --cc=Shyam.Iyer@dell.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.