From: Atish Patra <atishp@atishpatra.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Atish Patra <atish.patra@wdc.com>,
Conor.Dooley@microchip.com, Palmer Dabbelt <palmer@dabbelt.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MAINTAINERS section RISC-V/MICROCHIP POLARFIRE SOC SUPPORT with invalid file references
Date: Tue, 27 Apr 2021 23:31:17 -0700 [thread overview]
Message-ID: <CAOnJCUKrqOXGY7ePLEqxtAk39_fbhxt0wVhEtrv5m6X2wwuUpw@mail.gmail.com> (raw)
In-Reply-To: <CAKXUXMz51GMRM6s7YqGYgfZwRhW=y0aCALM-C3APU0=GjZ+X_g@mail.gmail.com>
On Tue, Apr 27, 2021 at 9:15 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> Dear Patish, dear Conor, dear Palmer,
>
> Commit df29598aaf5c ("MAINTAINERS: add microchip polarfire soc
> support") adds the new section RISC-V/MICROCHIP POLARFIRE SOC SUPPORT,
> but that section solely refers to files that do not exist in the
> repository.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F: drivers/soc/microchip/
> warning: no file matches F: include/soc/microchip/mpfs.h
>
> The patch series, [PATCH v4 0/5] Add Microchip PolarFire Soc Support,
> never adds those files, though. Are they coming through a different
> patch series into Linus' tree or do you intend to refer to other files
> instead?
>
The actual files are added as a part of the following series.
https://patchwork.kernel.org/project/linux-riscv/list/?series=467187
As the "Add Microchip PolarFire Soc Support" series added the basic SoC support,
we thought it is better to update the maintainers file in this series
to provide the information about
the maintainers for the PolarFire Soc.
Should we just remove the Files section or update the maintainers in
the SoC system controller series ?
>
> Lukas
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
--
Regards,
Atish
next prev parent reply other threads:[~2021-04-28 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 4:14 MAINTAINERS section RISC-V/MICROCHIP POLARFIRE SOC SUPPORT with invalid file references Lukas Bulwahn
2021-04-28 6:31 ` Atish Patra [this message]
2021-04-29 6:20 ` Palmer Dabbelt
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=CAOnJCUKrqOXGY7ePLEqxtAk39_fbhxt0wVhEtrv5m6X2wwuUpw@mail.gmail.com \
--to=atishp@atishpatra.org \
--cc=Conor.Dooley@microchip.com \
--cc=atish.patra@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas.bulwahn@gmail.com \
--cc=palmer@dabbelt.com \
/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;
as well as URLs for NNTP newsgroup(s).