The pull request you sent on Fri, 9 Apr 2021 12:48:16 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/189fefc7a4f0401d0f799de96b772319a6541fc1
Thank you!
--
Deet-doot-dot, I am a bo
The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:
Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to bc04d93ea30a0a8eb2a2648
On Wed, Mar 31, 2021 at 04:05:12PM +0800, Xie Yongji wrote:
> Use vhost_dev->mutex to protect vhost device iotlb from
> concurrent access.
>
> Fixes: 4c8cf318("vhost: introduce vDPA-based backend")
> Cc: sta...@vger.kernel.org
> Signed-off-by: Xie Yongji
> Acked-by: Jason Wang
> Reviewed-by: Ste
On Fri, Apr 09, 2021 at 12:47:55PM +0800, Jason Wang wrote:
>
> 在 2021/4/8 下午11:59, Michael S. Tsirkin 写道:
> > On Thu, Apr 08, 2021 at 04:26:48PM +0800, Jason Wang wrote:
> > > This patch mandates 1.0 for vDPA devices. The goal is to have the
> > > semantic of normative statement in the virtio spe
On Sat, Apr 03, 2021 at 12:45:54PM +0300, Arseny Krasnov wrote:
On 31.03.2021 17:48, Stefan Hajnoczi wrote:
On Tue, Mar 30, 2021 at 05:24:19PM +0300, Arseny Krasnov wrote:
On 30.03.2021 16:57, Stefan Hajnoczi wrote:
On Tue, Mar 30, 2021 at 12:50:06PM +0300, Arseny Krasnov wrote:
On 30.03.202
On Fri, Apr 09, 2021 at 09:54:03AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 08.04.21 um 11:48 schrieb Daniel Vetter:
> > On Thu, Mar 18, 2021 at 11:29:15AM +0100, Thomas Zimmermann wrote:
> > > Platform devices might operate on firmware framebuffers, such as VESA or
> > > EFI. Before a native d
On Fri, Apr 09, 2021 at 09:06:56AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 08.04.21 um 11:48 schrieb Daniel Vetter:
> >
> > Maybe just me, but to avoid overstretching the attention spawn of doc
> > readers I'd avoid this example here. And maybe make the recommendation
> > stronger, e.g. "PCI
Hi
Am 08.04.21 um 11:48 schrieb Daniel Vetter:
On Thu, Mar 18, 2021 at 11:29:15AM +0100, Thomas Zimmermann wrote:
Platform devices might operate on firmware framebuffers, such as VESA or
EFI. Before a native driver for the graphics hardware can take over the
device, it has to remove any platfor
Hi
Am 08.04.21 um 11:50 schrieb Daniel Vetter:
On Thu, Mar 18, 2021 at 11:29:14AM +0100, Thomas Zimmermann wrote:
Fbdev's helpers for handling conflicting framebuffers are related to
framebuffer apertures, not console emulation. Therefore move them into a
drm_aperture.h, which will contain the
Hi
Am 08.04.21 um 11:48 schrieb Daniel Vetter:
Maybe just me, but to avoid overstretching the attention spawn of doc
readers I'd avoid this example here. And maybe make the recommendation
stronger, e.g. "PCI device drivers can avoid open-coding
remove_conflicting_framebuffers() by calling
drm_f
10 matches
Mail list logo
