From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] rdma: Add Jason as a co-maintainer
Date: Tue, 21 Nov 2017 07:04:56 +0200 [thread overview]
Message-ID: <20171121050456.GM18825@mtr-leonro.local> (raw)
In-Reply-To: <20171120180631.GE626-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
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-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> > > .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.
>
> Do you see otherwise?
>
> We are now doing patches for rc.
>
> The iWarp security fix from Daniel is definitely rc material.
There is no need to wait for -rc1 to send bug fixes and Linus accepts and
welcomes bug fixes during merge window, see the pull requests from Dave
and others.
>
> Can you split that 33 patch series into things you think are rc
> material?
I'll take a look, but most probably I'll skip the split exercise.
This patch set was tested as one series and separation will require
two addition passes for the verification: one for-rc and another for
for-next.
Thanks
>
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-21 5:04 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
[not found] ` <20171120180631.GE626-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-21 5:04 ` Leon Romanovsky [this message]
[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=20171121050456.GM18825@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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