From: Leon Romanovsky <leon@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@mellanox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the mlx5-next tree
Date: Mon, 1 Jul 2024 10:08:32 +0300 [thread overview]
Message-ID: <20240701070832.GA13195@unreal> (raw)
In-Reply-To: <20240701153601.50d3f442@canb.auug.org.au>
On Mon, Jul 01, 2024 at 03:36:01PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the rdma tree as a different commit
> (but the same patch):
>
> 78a6cbd5145c ("RDMA/mlx5: Use sq timestamp as QP timestamp when RoCE is disabled")
>
> This is commit
>
> 0c5275bf75ec ("RDMA/mlx5: Use sq timestamp as QP timestamp when RoCE is disabled")
>
> in the rdma tree.
It is safe to drop the commit from mlx5-next, I dropped it now.
Thanks
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2024-07-01 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 5:36 linux-next: duplicate patch in the mlx5-next tree Stephen Rothwell
2024-07-01 7:08 ` Leon Romanovsky [this message]
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=20240701070832.GA13195@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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