From: Joe Perches <joe@perches.com>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andy Whitcroft <apw@canonical.com>,
Doug Ledford <dledford@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the rdma-fixes tree
Date: Thu, 08 Mar 2018 09:52:10 -0800 [thread overview]
Message-ID: <1520531530.11634.18.camel@perches.com> (raw)
In-Reply-To: <20180308174444.GG6773@mellanox.com>
On Thu, 2018-03-08 at 10:44 -0700, Jason Gunthorpe wrote:
> I only ask becuase I keep seeing these reports from Stephen and
> usuaully by the time it gets to him it requires a disruptive rebase to
> fix..
If it's a part of a series, it will always require a rebase.
Generally, I think it's a small and relatively unlikely
problem for checkpatch to bother with as there's already
a reporting mechanism in-place.
next prev parent reply other threads:[~2018-03-08 17:52 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
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 [this message]
-- 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=1520531530.11634.18.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leonro@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