From: Anatolij Gustschin <agust@denx.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] powerpc: Update MPC5XXX MAINTAINERS entry
Date: Sat, 29 Feb 2020 19:08:30 +0100 [thread overview]
Message-ID: <20200229190830.52eebda0@crub> (raw)
In-Reply-To: <20200224233146.23734-6-mpe@ellerman.id.au>
On Tue, 25 Feb 2020 10:31:44 +1100
Michael Ellerman mpe@ellerman.id.au wrote:
>It's several years since the last commit from Anatolij, so mark
>MPC5XXX as "Odd Fixes" rather than "Maintained".
>
>Also the git link no longer works so remove it.
>
>Cc: Anatolij Gustschin <agust@denx.de>
>Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Acked-by: Anatolij Gustschin <agust@denx.de>
next prev parent reply other threads:[~2020-02-29 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 23:31 [PATCH 1/8] powerpc: Update MAINTAINERS Michael Ellerman
2020-02-24 23:31 ` [PATCH 2/8] powerpc: Update wiki link in MAINTAINERS Michael Ellerman
2020-02-24 23:31 ` [PATCH 3/8] powerpc: Remove PA SEMI MAINTAINERS entries Michael Ellerman
2020-02-25 0:27 ` Olof Johansson
2020-02-24 23:31 ` [PATCH 4/8] powerpc: Mark 4xx as Orphan in MAINTAINERS Michael Ellerman
2020-02-24 23:42 ` Alistair Popple
2020-02-24 23:31 ` [PATCH 5/8] powerpc: Drop XILINX MAINTAINERS entry Michael Ellerman
2020-02-25 0:39 ` Grant Likely
2020-02-24 23:31 ` [PATCH 6/8] powerpc: Update MPC5XXX " Michael Ellerman
2020-02-29 18:08 ` Anatolij Gustschin [this message]
2020-02-24 23:31 ` [PATCH 7/8] powerpc: Update powermac " Michael Ellerman
2020-02-24 23:31 ` [PATCH 8/8] powerpc: Update 83xx/85xx " Michael Ellerman
2020-02-29 22:56 ` Scott Wood
2020-02-25 9:25 ` [PATCH 9/8] powerpc: Switch 8xx MAINTAINERS entry to Christophe Michael Ellerman
2020-04-01 12:53 ` [PATCH 1/8] powerpc: Update MAINTAINERS Michael Ellerman
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=20200229190830.52eebda0@crub \
--to=agust@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).