linux-kernel - Re: [PATCH] rdma: Add Jason as a co-maintainer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171121050456.GM18825@mtr-leonro.local>
Date:   Tue, 21 Nov 2017 07:04:56 +0200
From:   Leon Romanovsky <leon@...nel.org>
To:     Jason Gunthorpe <jgg@...lanox.com>
Cc:     Doug Ledford <dledford@...hat.com>, linux-rdma@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rdma: Add Jason as a co-maintainer

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@...lanox.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.

>
> 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@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)