[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181030053635.xwys3njelwa4j4vc@sirius.home.kraxel.org>
Date: Tue, 30 Oct 2018 06:36:35 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>
Cc: Souptick Joarder <jrdr.linux@...il.com>,
Sabyasachi Gupta <sabyasachi.linux@...il.com>,
airlied@...ux.ie, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
virtualization@...ts.linux-foundation.org,
Brajeswar Ghosh <brajeswar.linux@...il.com>
Subject: Re: [PATCH] gpu/drm/virtio/virtgpu_vq.c: Use kmem_cache_zalloc
On Tue, Oct 23, 2018 at 12:50:36PM +0300, Jani Nikula wrote:
> On Tue, 23 Oct 2018, Souptick Joarder <jrdr.linux@...il.com> wrote:
> > On Fri, Oct 19, 2018 at 9:30 PM Sabyasachi Gupta
> > <sabyasachi.linux@...il.com> wrote:
> >>
> >> Replaced kmem_cache_alloc + memset with kmem_cache_zalloc
> >
> > Put a new line gap in between these two lines and send v2.
>
> Nah, the maintainers can trivially add the newline while
> applying. Review is much more valuable than nitpicking on the commit
> message.
Queued (and added newline).
thanks,
Gerd
Powered by blists - more mailing lists