From: Leon Romanovsky <leonro@mellanox.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Doug Ledford <dledford@redhat.com>
Cc: Jason Gunthorpe <jgg@mellanox.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the rdma-fixes tree
Date: Thu, 8 Mar 2018 08:09:20 +0200 [thread overview]
Message-ID: <20180308060920.GQ15340@mtr-leonro.local> (raw)
In-Reply-To: <20180308164058.2ad5a158@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Thu, Mar 08, 2018 at 04:40:58PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> aa0de36a40f4 ("RDMA/mlx5: Fix integer overflow while resizing CQ")
>
> is missing a Signed-off-by from its author.
Doug, something went wrong with your scripts
In patchworks it is with SOB and lengthy commit message:
https://patchwork.kernel.org/patch/10264089/
In the tree, it is cut:
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=for-rc&id=aa0de36a40f446f5a21a7c1e677b98206e242edb
Thanks
>
> --
> Cheers,
> Stephen Rothwell
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-08 6:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 5:40 linux-next: Signed-off-by missing for commit in the rdma-fixes tree Stephen Rothwell
2018-03-08 6:09 ` Leon Romanovsky [this message]
2018-03-08 13:28 ` Doug Ledford
2018-03-08 13:38 ` Leon Romanovsky
2018-03-08 15:10 ` Jason Gunthorpe
2018-03-08 16:18 ` Jason Gunthorpe
2018-03-08 16:39 ` Joe Perches
2018-03-08 17:03 ` Jason Gunthorpe
2018-03-08 17:23 ` Joe Perches
2018-03-08 17:44 ` Jason Gunthorpe
2018-03-08 17:52 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2022-10-27 19:23 Stephen Rothwell
2022-10-28 15:54 ` Jason Gunthorpe
2023-01-17 21:04 Stephen Rothwell
2023-01-18 15:17 ` Jason Gunthorpe
2024-10-07 20:51 Stephen Rothwell
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=20180308060920.GQ15340@mtr-leonro.local \
--to=leonro@mellanox.com \
--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