Re: [PATCH -next] virtio_net: Update the feature bit to comply with spec

2016-06-09 Thread David Miller
From: Aaron Conole Date: Thu, 9 Jun 2016 13:41:15 -0400 > A draft version of the MTU Advice feature bit was specified as 25. This > bit is not within the allowed range for network device feature bits, and > should be changed to be feature bit 3 to fully comply with the spec. > > Fixes 14de9d11

[PATCH -next] virtio_net: Update the feature bit to comply with spec

2016-06-09 Thread Aaron Conole
A draft version of the MTU Advice feature bit was specified as 25. This bit is not within the allowed range for network device feature bits, and should be changed to be feature bit 3 to fully comply with the spec. Fixes 14de9d114a82 ('virtio-net: Add initial MTU advice feature') Signed-off-by: Aa

Re: [PATCH v2 08/20] drm: msm: Rely on the default ->best_encoder() behavior where appropriate

2016-06-09 Thread Archit Taneja
Hi, On 06/07/2016 05:18 PM, Boris Brezillon wrote: For all outputs except DSI we 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() and let the core call drm_atomic_helper_best_encoder() for us. Works

Re: [PATCH v2 07/20] drm: mediatek: Rely on the default ->best_encoder() behavior

2016-06-09 Thread Matthias Brugger
On 07/06/16 13:48, Boris Brezillon wrote: We 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() implementation and let the core call drm_atomic_helper_best_encoder() for us. Signed-off-by: Boris Brezi