public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@mellanox.com>
To: Leon Romanovsky <leon@kernel.org>
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: Mon, 20 Nov 2017 11:06:31 -0700	[thread overview]
Message-ID: <20171120180631.GE626@mellanox.com> (raw)
In-Reply-To: <20171120161016.GL18825@mtr-leonro.local>

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?

Do you see otherwise?

We are now doing patches for rc.

The iWarp security fix from Daniel is definitely rc material.

Can you split that 33 patch series into things you think are rc
material?

Jason

  reply	other threads:[~2017-11-20 18:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 20:44 [PATCH] rdma: Add Jason as a co-maintainer Jason Gunthorpe
2017-11-17  5:00 ` Leon Romanovsky
2017-11-20 12:45 ` Sagi Grimberg
     [not found] ` <20171116204400.GA28216-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-17 17:54   ` Bart Van Assche
     [not found]     ` <1510941272.2846.46.camel-Sjgp3cTcYWE@public.gmane.org>
2017-11-17 18:14       ` Jason Gunthorpe
     [not found]         ` <20171117181410.GL4276-uk2M96/98Pc@public.gmane.org>
2017-11-17 19:45           ` Doug Ledford
     [not found]             ` <1510947901.3973.26.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-17 21:32               ` Jason Gunthorpe
     [not found]                 ` <20171117213227.GQ4276-uk2M96/98Pc@public.gmane.org>
2017-11-18  1:44                   ` Doug Ledford
2017-11-18  7:26                     ` Leon Romanovsky
2017-11-19  8:33       ` Amrani, Ram
2017-11-20 16:10   ` Leon Romanovsky
2017-11-20 18:06     ` Jason Gunthorpe [this message]
     [not found]       ` <20171120180631.GE626-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-21  5:04         ` Leon Romanovsky
     [not found]           ` <20171121050456.GM18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-21  6:37             ` Leon Romanovsky

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=20171120180631.GE626@mellanox.com \
    --to=jgg@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --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