linux-kernel - Re: [PATCH 03/22] keembay-ipc: Add Keem Bay IPC module

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: <20201202174200.GG63356@mtg-dev.jf.intel.com>
Date:   Wed, 2 Dec 2020 09:42:00 -0800
From:   mark gross <mgross@...ux.intel.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     mgross@...ux.intel.com, markgross@...nel.org, arnd@...db.de,
        bp@...e.de, damien.lemoal@....com, dragan.cvetic@...inx.com,
        corbet@....net, leonard.crestez@....com, palmerdabbelt@...gle.com,
        paul.walmsley@...ive.com, peng.fan@....com, robh+dt@...nel.org,
        shawnguo@...nel.org, linux-kernel@...r.kernel.org,
        Daniele Alessandrelli <daniele.alessandrelli@...el.com>
Subject: Re: [PATCH 03/22] keembay-ipc: Add Keem Bay IPC module

On Wed, Dec 02, 2020 at 07:16:20AM +0100, Greg KH wrote:
> On Tue, Dec 01, 2020 at 02:34:52PM -0800, mgross@...ux.intel.com wrote:
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -8955,6 +8955,14 @@ M:	Deepak Saxena <dsaxena@...xity.net>
> >  S:	Maintained
> >  F:	drivers/char/hw_random/ixp4xx-rng.c
> >  
> > +INTEL KEEM BAY IPC DRIVER
> > +M:	Daniele Alessandrelli <daniele.alessandrelli@...el.com>
> > +M:	Mark Gross <mgross@...ux.intel.com>
> > +S:	Maintained
> > +F:	Documentation/devicetree/bindings/soc/intel/intel,keembay-ipc.yaml
> > +F:	drivers/soc/intel/keembay-ipc.c
> > +F:	include/linux/soc/intel/keembay-ipc.h
> 
> Sad that Intel is not going to actually pay you all to do this
> maintenance work for a brand new subsystem you are wanting to add to the
> tree :(
I thought adding my name to these maintainer items would help with continuity
as the individual engineers tend to move on to other things over time.

While I'm paid for a number of things at intel this is one of them.  My role is
as stable as I choose it to be at the point I'm at in my Intel career and the
business unit I'm now part of.  We can leave my name off if that would be
better.

Even if I'm not a VPU IP domain expert like Daniele is I can still chase down
the experts as needed after Daniele grows into other things over time.

> 
> Does this mean you all will have to do it on your own time and not as
> part of your work at Intel?  If so, why not just use your personal email
> addresses instead to make it a bit more obvious?
nah, as I've been getting older I've been getting more stingy with my me time
with my non-tech hobbies.  When I do retire (or whatever) from Intel we'll need
to remove my name for the stuff I'll not be getting paid for any more.

--mark