mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
	Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify entry for PSTORE FILESYSTEM
Date: Wed, 20 Oct 2021 13:51:34 +0200	[thread overview]
Message-ID: <Y9Y91R.5KFSRX6QS1RV1@ixit.cz> (raw)
In-Reply-To: <20211020104647.11556-1-lukas.bulwahn@gmail.com>

In Rob tree, there is already applied patch "dt-bindings: 
reserved-memory: ramoops: update ramoops.yaml references" which should 
fix it.
David

On Wed, Oct 20 2021 at 12:46:47 +0200, Lukas Bulwahn 
<lukas.bulwahn@gmail.com> wrote:
> Commit 89a5bf0f22fd ("dt-bindings: reserved-memory: ramoops: Convert 
> txt
> bindings to yaml") converts ramoops.txt to ramoops.yaml, but missed to
> adjust its reference in MAINTAINERS.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains 
> about
> a broken reference.
> 
> Repair this file reference in PSTORE FILESYSTEM.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on next-20211019
> 
> Please apply clean-up patch on top of commit above.
> 
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1ad9cbe46b53..cb84a0d46a24 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15336,7 +15336,7 @@ S:	Maintained
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git 
> for-next/pstore
>  F:	Documentation/admin-guide/ramoops.rst
>  F:	Documentation/admin-guide/pstore-blk.rst
> -F:	Documentation/devicetree/bindings/reserved-memory/ramoops.txt
> +F:	Documentation/devicetree/bindings/reserved-memory/ramoops.yaml
>  F:	drivers/acpi/apei/erst.c
>  F:	drivers/firmware/efi/efi-pstore.c
>  F:	fs/pstore/
> --
> 2.26.2
> 



      reply	other threads:[~2021-10-20 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 10:46 Lukas Bulwahn
2021-10-20 11:51 ` David Heidelberg [this message]

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=Y9Y91R.5KFSRX6QS1RV1@ixit.cz \
    --to=david@ixit.cz \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=devicetree@vger.kernel.org \
    --cc=keescook@chromium.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=robh@kernel.org \
    --cc=tony.luck@intel.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

all inboxes | Powered by JetHome®