mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rdma: Add Jason as a co-maintainer
Date: Tue, 21 Nov 2017 08:37:26 +0200	[thread overview]
Message-ID: <20171121063726.GQ18825@mtr-leonro.local> (raw)
In-Reply-To: <20171121050456.GM18825@mtr-leonro.local>

[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]

On Tue, Nov 21, 2017 at 07:04:56AM +0200, Leon Romanovsky wrote:
> On Mon, Nov 20, 2017 at 11:06:31AM -0700, Jason Gunthorpe wrote:
> > On Mon, Nov 20, 2017 at 06:10:16PM +0200, Leon Romanovsky wrote:
> > > On Thu, Nov 16, 2017 at 01:44:00PM -0700, Jason Gunthorpe wrote:
> > > > As was discussed in September and October, add Jason along with
> > > > Doug to have a team maintainership model for the RDMA subystem.
> > > >
> > > > Mellanox Technologies will be funding Jason's independent work on
> > > > the maintainership.
> > > >
> > > > Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
> > > >  .mailmap    | 2 ++
> > > >  MAINTAINERS | 1 +
> > > >  2 files changed, 3 insertions(+)
> > > >
> > >
> > > Doug and Jason,
> > >
> > > Can you forward the current fixes to Linus?
> > >
> > > I have more fixes from Parav and fix to iWARP from Daniel, but I prefer
> > > to have proper RDMA branches before I'm posting them.
> >
> > I belive Doug has already sent the pull request for this merge window,
> > and the new shared tree location is fully up to date, and there are
> > no accepted but unset patches at this time?
>
> I still see for-rc points to old (4.14) code.
> https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=k.o/for-rc
>
> There is a need to advance -rc to be equal to -next during merge window,
> so we will be able to actually base our -rc/-next patches.

And for-next misses one patch, which I sent directly to Linus
https://patchwork.kernel.org/patch/10032391/
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/core/nldev.c?id=287683d027a3ff83feb6c7044430c79881664ecf
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=k.o/for-next

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-11-21  6:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 20:44 Jason Gunthorpe
2017-11-17  5:00 ` Leon Romanovsky
2017-11-17 17:54 ` Bart Van Assche
2017-11-17 18:14   ` Jason Gunthorpe
2017-11-17 19:45     ` Doug Ledford
2017-11-17 21:32       ` Jason Gunthorpe
2017-11-18  1:44         ` Doug Ledford
2017-11-18  7:26           ` Leon Romanovsky
2017-11-19  8:33   ` Amrani, Ram
2017-11-20 12:45 ` Sagi Grimberg
2017-11-20 16:10 ` Leon Romanovsky
2017-11-20 18:06   ` Jason Gunthorpe
2017-11-21  5:04     ` Leon Romanovsky
2017-11-21  6:37       ` 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=20171121063726.GQ18825@mtr-leonro.local \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®