From: Jean Delvare <jdelvare@suse.de>
To: Jordan Hargrave <jharg93@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jordan Hargrave <jordan_hargrave@dell.com>
Subject: Re: [PATCHv3] Save SMBIOS Type 9 System Slots during DMI Scan
Date: Sun, 29 Nov 2015 15:25:30 +0100 [thread overview]
Message-ID: <20151129152530.3c2cae45@endymion.delvare> (raw)
In-Reply-To: <1448678755-14779-1-git-send-email-jordan_hargrave@dell.com>
Hi Jordan,
On Fri, 27 Nov 2015 20:45:55 -0600, Jordan Hargrave wrote:
> commit fdf6d7e7cf448b9482062d73a48895afaf38a458
> Author: Jordan Hargrave <jordan_hargrave@dell.com>
> Date: Fri Nov 27 20:39:59 2015 -0600
>
> Fix spacing
> Check invalid slot entry according to spec
>
> commit 8a7fe87241b93c72cfd6ef818a680a2c7fc2f1c7
> Author: Jordan Hargrave <jordan_hargrave@dell.com>
> Date: Thu Nov 26 15:57:24 2015 -0600
>
> Save SMBIOS Type 9 System Slots during DMI Scan
>
> PCI address of onboard devices is currently saved but not for slots.
>
> Cleaned up some code, verify clean patch
>
> PCI address of onboard devices is currently saved but not for slots.
>
> Cleaned up some code, verify clean patch
>
> Signed-off-by: Jordan Hargrave <jordan_hargrave@dell.com>
> ---
> drivers/firmware/dmi_scan.c | 53 +++++++++++++++++++++++++++++++--------------
> include/linux/dmi.h | 1 +
> 2 files changed, 38 insertions(+), 16 deletions(-)
> (...)
Format is awful but result is correct. Next time please rebase cleanly
your patch. For this time I'll do it, I must adjust it due to my own
patches anyway. So consider it applied.
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-11-29 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 2:45 [PATCHv3] Save SMBIOS Type 9 System Slots during DMI Scan Jordan Hargrave
2015-11-29 14:25 ` Jean Delvare [this message]
2016-02-09 22:56 ` [PATCH] Create pci slot files for SMBIOS Type 9 entries Jordan_Hargrave
2016-02-09 23:23 ` kbuild test robot
2016-02-10 14:50 ` Jordan_Hargrave
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=20151129152530.3c2cae45@endymion.delvare \
--to=jdelvare@suse.de \
--cc=jharg93@gmail.com \
--cc=jordan_hargrave@dell.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 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.