From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm@vger.kernel.org, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, elic@nvidia.com
Subject: [GIT PULL] vdpa: bugfix
Date: Mon, 27 Mar 2023 09:19:47 -0400 [thread overview]
Message-ID: <20230327091947-mutt-send-email-mst@kernel.org> (raw)
The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:
Linux 6.3-rc3 (2023-03-19 13:27:55 -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 8fc9ce051f22581f60325fd87a0fd0f37a7b70c3:
vdpa/mlx5: Remove debugfs file after device unregister (2023-03-21 16:39:02 -0400)
----------------------------------------------------------------
vdpa: bugfix
An error handling fix in mlx5.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Eli Cohen (1):
vdpa/mlx5: Remove debugfs file after device unregister
drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
elic@nvidia.com, mst@redhat.com
Subject: [GIT PULL] vdpa: bugfix
Date: Mon, 27 Mar 2023 09:19:47 -0400 [thread overview]
Message-ID: <20230327091947-mutt-send-email-mst@kernel.org> (raw)
The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:
Linux 6.3-rc3 (2023-03-19 13:27:55 -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 8fc9ce051f22581f60325fd87a0fd0f37a7b70c3:
vdpa/mlx5: Remove debugfs file after device unregister (2023-03-21 16:39:02 -0400)
----------------------------------------------------------------
vdpa: bugfix
An error handling fix in mlx5.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Eli Cohen (1):
vdpa/mlx5: Remove debugfs file after device unregister
drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2023-03-27 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 13:19 Michael S. Tsirkin [this message]
2023-03-27 13:19 ` [GIT PULL] vdpa: bugfix Michael S. Tsirkin
2023-03-27 13:30 ` Michael S. Tsirkin
2023-03-27 13:30 ` Michael S. Tsirkin
2023-03-27 13:32 ` Michael S. Tsirkin
2023-03-27 13:32 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2021-02-01 23:25 Michael S. Tsirkin
2021-02-01 23:25 ` Michael S. Tsirkin
2021-02-02 18:48 ` pr-tracker-bot
2021-02-02 18:48 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230327091947-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=elic@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.