All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jason Gunthorpe <jgg@nvidia.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 rdma tree
Date: Thu, 6 Nov 2025 10:07:11 +0200	[thread overview]
Message-ID: <20251106080711.GA15456@unreal> (raw)
In-Reply-To: <20251106082318.05ae9256@canb.auug.org.au>

On Thu, Nov 06, 2025 at 08:23:18AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
> 
>   b549c24d549d ("RDMA/irdma: Fix vf_id size to u16 to avoid overflow")

Dropped this commit from our -next tree.

> 
> This is commit
> 
>   320258783765 ("RDMA/irdma: Fix vf_id size to u16 to avoid overflow")
> 
> in Linus' tree.

Thanks 

> 
> -- 
> Cheers,
> Stephen Rothwell



      reply	other threads:[~2025-11-06  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 21:23 linux-next: duplicate patch in the rdma tree Stephen Rothwell
2025-11-06  8:07 ` 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=20251106080711.GA15456@unreal \
    --to=leonro@nvidia.com \
    --cc=jgg@nvidia.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 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.