From: Boris Petkov <bp@alien8.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Isaac Vaughn <isaac.vaughn@Knights.ucf.edu>,
Yazen Ghannam <yazen.ghannam@amd.com>,
"trivial@kernel.org" <trivial@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
x86@kernel.org, linux-hwmon@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] Add PCI device IDs for family 17h, model 70h
Date: Fri, 06 Sep 2019 15:09:16 +0200 [thread overview]
Message-ID: <6B3FCC26-7A2F-438F-B442-EA665DDD0569@alien8.de> (raw)
In-Reply-To: <20190906130206.GB7255@roeck-us.net>
On September 6, 2019 3:02:06 PM GMT+02:00, Guenter Roeck <linux@roeck-us.net> wrote:
>Also, how is this patch different to the patches already in linux-next
>?
Which are those? Care to share their linux-next commit IDs with us?
--
Sent from a small device: formatting sux and brevity is inevitable.
next prev parent reply other threads:[~2019-09-06 13:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 21:13 [PATCH] amd64_edac - Add Family 17h Model 70h PCI IDs Isaac Vaughn
2019-09-04 21:53 ` Borislav Petkov
2019-09-04 22:21 ` Ghannam, Yazen
2019-09-05 1:21 ` Isaac Vaughn
2019-09-05 7:09 ` Borislav Petkov
2019-09-05 13:17 ` Isaac Vaughn
2019-09-05 13:54 ` Borislav Petkov
2019-09-06 1:01 ` [PATCH] Add PCI device IDs for family 17h, model 70h Isaac Vaughn
2019-09-06 1:41 ` Ghannam, Yazen
2019-09-06 1:56 ` Isaac Vaughn
2019-09-06 9:12 ` Borislav Petkov
[not found] ` <20190906075729.9e2faf7147da62fc26006833@knights.ucf.edu>
2019-09-06 12:14 ` Borislav Petkov
2019-09-06 13:02 ` Guenter Roeck
2019-09-06 13:09 ` Boris Petkov [this message]
[not found] ` <B08C8E54-43FA-4E29-8D7D-5F9C4AF20CCF@Knights.ucf.edu>
2019-09-06 14:50 ` Borislav Petkov
2019-09-06 23:27 ` Isaac Vaughn
2019-09-06 16:11 ` Guenter Roeck
2019-09-06 16:22 ` Borislav Petkov
2019-09-06 23:21 Isaac Vaughn
2019-09-07 5:59 ` Borislav Petkov
2019-09-07 12:09 ` Isaac Vaughn
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=6B3FCC26-7A2F-438F-B442-EA665DDD0569@alien8.de \
--to=bp@alien8.de \
--cc=isaac.vaughn@Knights.ucf.edu \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=trivial@kernel.org \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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;
as well as URLs for NNTP newsgroup(s).