From: Jeff Epler <jepler@unpythonic.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: incompatible pci sysfs change since 3.12 (5136b2da770d)
Date: Thu, 30 Oct 2014 13:09:34 -0500 [thread overview]
Message-ID: <20141030180934.GC59253@unpythonic.net> (raw)
In-Reply-To: <20141030163053.GB22250@kroah.com>
On Thu, Oct 30, 2014 at 09:30:53AM -0700, Greg Kroah-Hartman wrote:
> I've now sent a patch that should fix this. If you could verify it, I'd
> appreciate it.
Will test. Thank you. The patch sure looks plausible.
Jeff
prev parent reply other threads:[~2014-10-30 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 0:22 incompatible pci sysfs change since 3.12 (5136b2da770d) Jeff Epler
2014-10-30 0:36 ` Greg Kroah-Hartman
2014-10-30 1:16 ` Jeff Epler
2014-10-30 16:30 ` Greg Kroah-Hartman
2014-10-30 18:09 ` Jeff Epler [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=20141030180934.GC59253@unpythonic.net \
--to=jepler@unpythonic.net \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).