From: Leon Romanovsky <leon@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: saeedm@nvidia.com, kvm@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, kevin.tian@intel.com, joao.m.martins@oracle.com,
yishaih@nvidia.com, maorg@nvidia.com, cohuck@redhat.com
Subject: Re: [GIT PULL] Please pull mlx5 vfio changes
Date: Thu, 8 Sep 2022 09:31:13 +0300 [thread overview]
Message-ID: <YxmMMR3u1VRedWdK@unreal> (raw)
In-Reply-To: <20220907132119.447b9219.alex.williamson@redhat.com>
On Wed, Sep 07, 2022 at 01:21:19PM -0600, Alex Williamson wrote:
> On Wed, 7 Sep 2022 12:43:44 +0300
> Leon Romanovsky <leon@kernel.org> wrote:
>
> > Hi Alex,
> >
> > This series is based on clean 6.0-rc4 as such it causes to two small merge
> > conficts whis vfio-next. One is in thrird patch where you should take whole
> > chunk for include/uapi/linux/vfio.h as is. Another is in vfio_main.c around
> > header includes, which you should take too.
>
> Is there any reason you can't provide a topic branch for the two
> net/mlx5 patches and the remainder are rebased and committed through
> the vfio tree?
You added your Acked-by to vfio/mlx5 patches and for me it is a sign to
prepare clean PR with whole series.
I reset mlx5-vfio topic to have only two net/mlx5 commits without
special tag.
https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git topic/mlx5-vfio
Everything else can go directly to your tree without my intervention.
Thanks
next prev parent reply other threads:[~2022-09-08 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:43 [GIT PULL] Please pull mlx5 vfio changes Leon Romanovsky
2022-09-07 19:21 ` Alex Williamson
2022-09-08 6:31 ` Leon Romanovsky [this message]
2022-09-08 16:53 ` Alex Williamson
2022-09-08 17:31 ` Yishai Hadas
2022-09-08 18:00 ` Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2022-05-10 13:12 Leon Romanovsky
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=YxmMMR3u1VRedWdK@unreal \
--to=leon@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=yishaih@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).