From: Jason Gunthorpe <jgg@mellanox.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
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:10:42 -0700 [thread overview]
Message-ID: <20180308151042.GA6773@mellanox.com> (raw)
In-Reply-To: <1520515725.3126.88.camel@redhat.com>
On Thu, Mar 08, 2018 at 08:28:45AM -0500, Doug Ledford wrote:
> Anyway, I've hand edited the mbox file and I pushed a rebased version of
> my wip branch. However, during the night Jason must have moved my
> wip/for-rc branch to the official for-rc because it's there now, so the
> only way to fix this (that I know of) in our official for-rc branch is a
> rebase :-(
Yes, to get it into for-next so we could send to linus soon
Jason
next prev parent reply other threads:[~2018-03-08 15:10 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 [this message]
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=20180308151042.GA6773@mellanox.com \
--to=jgg@mellanox.com \
--cc=dledford@redhat.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 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.