linux-kernel - Re: [PATCH v1 1/1] ASoC: madera: Replace kernel.h with the necessary inclusions

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: <CAHp75VfkOndCsu9S3M-ftKAtVntsPkRKUuaOo2xOa2w5c3xZkg@mail.gmail.com>
Date:   Mon, 4 Jul 2022 17:51:44 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Richard Fitzgerald <rf@...nsource.cirrus.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        ALSA Development Mailing List <alsa-devel@...a-project.org>,
        patches@...nsource.cirrus.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Charles Keepax <ckeepax@...nsource.cirrus.com>,
        Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH v1 1/1] ASoC: madera: Replace kernel.h with the necessary inclusions

On Mon, Jul 4, 2022 at 5:35 PM Mark Brown <broonie@...nel.org> wrote:
> On Mon, Jul 04, 2022 at 05:30:41PM +0200, Andy Shevchenko wrote:
> > On Mon, Jul 4, 2022 at 12:45 PM Mark Brown <broonie@...nel.org> wrote:
>
> > > > +Cc: Liam, Mark
>
> > > If you needed to add me to the CC I've not seen the patch...
> > > for review.  People get busy, go on holiday, attend conferences and so
>
> > The question here is about MAINTAINERS. That's why you are in Cc list.
> > Do we have an issue in MAINTAINERS that causes you being not see the
> > patch?
>
> I have no idea, all that's showing up in my inbox is these content free
> pings.  You'd have to ask whoever didn't send the patch to me.

Let me rephrase my question (it's not so related to this patch).
How does the ASoC works in terms of MAINTAINERS records?

I found that there are files that are related to the sound/soc/* one
way or another, but listed only in a certain record of MAINTAINERS
without being listed as part of ASoC record. Does it mean I have to
always remember to add ASoC maintainers to each patch that touches one
of such files and doesn't provide them? OR do we need to fix
MAINTAINERS for such files by listing them in the ASoC record?


-- 
With Best Regards,
Andy Shevchenko