From: Richard Weinberger <richard@nod.at>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: benjamin.romer@unisys.com, david.kershner@unisys.com,
devel@driverdev.osuosl.org, sparmaintainer@unisys.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: unisys: Disable driver for UML
Date: Sun, 10 May 2015 23:02:24 +0200 [thread overview]
Message-ID: <554FC760.1010509@nod.at> (raw)
In-Reply-To: <20150510130206.GA15463@kroah.com>
Am 10.05.2015 um 15:02 schrieb Greg KH:
> On Mon, May 04, 2015 at 09:02:10PM +0200, Richard Weinberger wrote:
>> UML has no io memory nor cpuid.
>> Let's disable this driver for UML.
>
> Doesn't apply to my tree :(
I'm sorry Greg, looks like my -next tree needs updating.
Will resend soon.
Thanks,
//richard
prev parent reply other threads:[~2015-05-10 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 19:02 [PATCH] staging: unisys: Disable driver for UML Richard Weinberger
2015-05-10 13:02 ` Greg KH
2015-05-10 21:02 ` Richard Weinberger [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=554FC760.1010509@nod.at \
--to=richard@nod.at \
--cc=benjamin.romer@unisys.com \
--cc=david.kershner@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparmaintainer@unisys.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