linux-kernel - Re: [PATCH 3/3] drm/scheduler: Clean up jobs when the scheduler is torn down.

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: <847159ff6d0c01cef2e6308848ea49a732248e42@linux.dev>
Date:   Wed, 19 Jul 2023 18:16:36 +0000
From:   "Konstantin Ryabitsev" <konstantin.ryabitsev@...ux.dev>
To:     "Luben Tuikov" <luben.tuikov@....com>,
        "Asahi Lina" <lina@...hilina.net>,
        "David Airlie" <airlied@...il.com>,
        "Daniel Vetter" <daniel@...ll.ch>,
        "Sumit Semwal" <sumit.semwal@...aro.org>,
        "Christian König" <christian.koenig@....com>
Cc:     "Faith Ekstrand" <faith.ekstrand@...labora.com>,
        linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
        asahi@...ts.linux.dev, "Alyssa Rosenzweig" <alyssa@...enzweig.io>,
        linux-media@...r.kernel.org
Subject: Re: [PATCH 3/3] drm/scheduler: Clean up jobs when the scheduler is
 torn down.

July 18, 2023 at 1:14 AM, "Luben Tuikov" <luben.tuikov@....com> wrote:
> > > Not sure about other drivers--they can speak for themselves and the CC list
> > >  should include them--please use "dim add-missing-cc" and make sure
> > >  that the Git commit description contains the Cc tags--then git send-email
> > >  will populate the SMTP CC. Feel free to add more Cc tags on top of that.
> >  
> >  I use `b4 prep -c` which I think does the same thing? I just ran it 
> >  again and it only added 'linaro-mm-sig@...ts.linaro.org', not sure why 
> >  that one wasn't there. Am I missing anything else?
> 
> Not sure about "b4 prep -c"--using "git send-email" instead, but what is
> important is to add the Cc: tags as part of the commit message. A "git log" of
> drm-misc-next shows the proper format. Then maintainers add Link:
> tag to the correct email thread, which is usually completely automated
> by "dim" or by "git am", or both.

It's useful to note here that this is not standard practice across the entirety of the Linux tree. In general, Cc: trailers are added to individual commits when get_maintainer.pl wouldn't otherwise include someone in the recipient list. The "dim" tool mentioned here is specific to the DRM subsystem (the "d" stands for "DRM"). Since both tools work on git series, you can use it alongside b4.

DRM folks, if get_maintainer.pl isn't finding someone who should be included on a series of patches, should the MAINTAINERS file be updated to make it easier to submit valid patches without needing to know of "dim"?

Regards,
-K