From: Aaron Conole
Date: Fri, 3 Jun 2016 16:57:12 -0400
> This commit adds the feature bit and associated mtu device entry for the
> virtio network device. When a virtio device comes up, it checks the
> feature bit for the VIRTIO_NET_F_MTU feature. If such feature bit is
> enabled, the driver
On 2016年06月02日 22:31, Boris Brezillon wrote:
All outputss have a 1:1 relationship between connectors and encoders
and the driver is relying on the atomic helpers: we can drop the custom
->best_encoder() implementations and let the core call
drm_atomic_helper_best_encoder() for us.
Good, All co
On Thu, Jun 02, 2016 at 11:57:02PM +0200, Daniel Vetter wrote:
> drm_encoder_find is an idr lookup. That should be plenty fast,
> especially for modeset code. Usually what's too expensive even for
> modeset code is linear list walks. But Chris just submitted patches to
> convert most of them into s
On Mon, 2016-06-06 at 17:59 +0200, Peter Zijlstra wrote:
> On Fri, Jun 03, 2016 at 02:33:47PM +1000, Benjamin Herrenschmidt wrote:
> >
> > - For the above, can you show (or describe) where the qspinlock
> > improves things compared to our current locks.
> So currently PPC has a fairly straight
On Fri, Jun 03, 2016 at 02:33:47PM +1000, Benjamin Herrenschmidt wrote:
> - For the above, can you show (or describe) where the qspinlock
> improves things compared to our current locks.
So currently PPC has a fairly straight forward test-and-set spinlock
IIRC. You have this because LPAR/virt
From: Gustavo Padovan
Replace the legacy drm_send_vblank_event() with the new helper function.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/virtio/virtgpu_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c
b/drivers/gpu
It's queued in my tree and will be merged shortly.
Thanks!
On Mon, Jun 06, 2016 at 09:55:59AM +0300, Mike Rapoport wrote:
> Ping?
>
> On Tue, May 24, 2016 at 03:41:33PM +0300, Mike Rapoport wrote:
> > Michael,
> >
> > Any updates on this?
> >
> > On Wed, May 04, 2016 at 01:15:50PM +0300, Mike R