From: Tom Rini <trini@konsulko.com>
To: Moritz Fischer <moritzf@google.com>
Cc: u-boot@lists.denx.de, sjg@chromium.org, kettenis@openbsd.org
Subject: Re: [PATCH] MAINTAINERS: Fix ARCH_APPLE file paths
Date: Wed, 13 Dec 2023 18:05:59 -0500 [thread overview]
Message-ID: <20231213230559.GP2513409@bill-the-cat> (raw)
In-Reply-To: <20231122162115.508690-1-moritzf@google.com>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
On Wed, Nov 22, 2023 at 04:21:14PM +0000, Moritz Fischer wrote:
> Fixes a filepath in MAINTAINERS file that wasn't updated when
> renaming the files to match the new SoC name.
>
> Fixes: a4bd5e4120d6 ('arm: apple: Change SoC name from "m1" into "apple"')
> Signed-off-by: Moritz Fischer <moritzf@google.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-12-13 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 16:21 [PATCH] MAINTAINERS: Fix ARCH_APPLE file paths Moritz Fischer
2023-12-13 23:05 ` Tom Rini [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=20231213230559.GP2513409@bill-the-cat \
--to=trini@konsulko.com \
--cc=kettenis@openbsd.org \
--cc=moritzf@google.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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