From: Kim Phillips <kim.phillips@linaro.org>
To: gregkh@linuxfoundation.org
Cc: B08248@freescale.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: driver core patches
Date: Tue, 3 Dec 2013 12:32:53 +0000 [thread overview]
Message-ID: <20131203123253.9fd9b92ff0170b214e69f18b@linaro.org> (raw)
In-Reply-To: <20131106021247.GB6687@kroah.com>
On Tue, 5 Nov 2013 18:12:47 -0800
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org> wrote:
> On Tue, Nov 05, 2013 at 10:53:36PM +0000, Stuart Yoder wrote:
> > Hi Greg,
> >
> > Any feedback on the driver core patches in Kim Phillips patch series
> > from mid-October?
> >
> > The 3rd patch of the series has some open issues related to vfio-pci,
> > but the first two are driver core related and am wondering if they
> > are acceptable.
>
> As I saw there was lots of discussion, and some rework needed, I haven't
> paid any attention to them, expecting to see another set show up.
the first two patches didn't receive any feedback, whilst the 3rd broke
vfio-pci userspace i/f compatibility, so I'm going to assume that 1 and
2 are acceptable and work to enable rebinding platform devices, and
that vfio-pci can transition over later.
> Also, it's way past the merge window, and I can't do anything with any
> new patches until after 3.13-rc1 is out, combined with a
> travel-schedule-from-hell, and I really am not going to want to review
> these types of patches for a number of weeks.
>
> So take the time, fix them up, and send them after 3.13-rc2 is out or so
> and I should have a chance to look at them then. Hopefully I'll hate
> them less by then, but I'm not guaranteeing anything...
ok, 3.13-rc2 is out, so I'm going to repost 1 & 2 now.
fwiw, I'm omitting the fourth patch to reduce confusion because it
depends on Antonios Motakis' vfio-platform WIP patchseries.
Kim
prev parent reply other threads:[~2013-12-03 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 22:53 Stuart Yoder
2013-11-06 2:12 ` gregkh
2013-12-03 12:32 ` Kim Phillips [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=20131203123253.9fd9b92ff0170b214e69f18b@linaro.org \
--to=kim.phillips@linaro.org \
--cc=B08248@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--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®