search for: 87h9k4kzcv

...based on the current linux-next. I think that clearing __GFP_HIGHMEM is bogus in the current code because all code paths either use GFP_KERNEL or GFP_ATOMIC and those do not fall back to the highmem zone but I have kept it because clearing the flag cannot be harmful. [1] http://lkml.kernel.org/r/87h9k4kzcv.fsf%40yhuang-dev.intel.com drivers/virtio/virtio_ring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index 14e7ce9b3e96..734de927c89d 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring.c @@...

...based on the current linux-next. I think that clearing __GFP_HIGHMEM is bogus in the current code because all code paths either use GFP_KERNEL or GFP_ATOMIC and those do not fall back to the highmem zone but I have kept it because clearing the flag cannot be harmful. [1] http://lkml.kernel.org/r/87h9k4kzcv.fsf%40yhuang-dev.intel.com drivers/virtio/virtio_ring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index 14e7ce9b3e96..734de927c89d 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring.c @@...

...gt; > I think that clearing __GFP_HIGHMEM is bogus in the current code because > all code paths either use GFP_KERNEL or GFP_ATOMIC and those do not fall > back to the highmem zone but I have kept it because clearing the flag > cannot be harmful. > > [1] http://lkml.kernel.org/r/87h9k4kzcv.fsf%40yhuang-dev.intel.com > > drivers/virtio/virtio_ring.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Thanks for cleaning this up: Acked-by: Will Deacon <will.deacon at arm.com> Will > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c &gt...