[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4itKNqVbisM7aAZKZ02QRwfvy9XBHZYWTjqJqcGEZVguw@mail.gmail.com>
Date: Fri, 13 Oct 2017 08:25:59 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Stefan Hajnoczi <stefanha@...il.com>
Cc: Pankaj Gupta <pagupta@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
KVM list <kvm@...r.kernel.org>,
Qemu Developers <qemu-devel@...gnu.org>,
linux-nvdimm <linux-nvdimm@...1.01.org>,
Linux MM <linux-mm@...ck.org>, Jan Kara <jack@...e.cz>,
Stefan Hajnoczi <stefanha@...hat.com>,
Rik van Riel <riel@...hat.com>,
Haozhong Zhang <haozhong.zhang@...el.com>,
Nitesh Narayan Lal <nilal@...hat.com>,
Kevin Wolf <kwolf@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"Zwisler, Ross" <ross.zwisler@...el.com>,
David Hildenbrand <david@...hat.com>,
Xiao Guangrong <xiaoguangrong.eric@...il.com>
Subject: Re: [RFC 2/2] KVM: add virtio-pmem driver
On Fri, Oct 13, 2017 at 2:44 AM, Stefan Hajnoczi <stefanha@...il.com> wrote:
> On Thu, Oct 12, 2017 at 09:20:26PM +0530, Pankaj Gupta wrote:
[..]
>> +#ifndef REQ_FLUSH
>> +#define REQ_FLUSH REQ_PREFLUSH
>> +#endif
>
> Is this out-of-tree kernel module compatibility stuff that can be
> removed?
Yes, this was copied from the pmem driver where it can also be
removed, it was used to workaround a merge order problem in linux-next
when these definitions were changed several kernel releases back.
Powered by blists - more mailing lists