From: Arnd Bergmann <arnd@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: SoC Team <soc@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>, DTML <devicetree@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Jamie Iles <jamie@jamieiles.com>
Subject: Re: [PATCH 0/4] Remove PicoXcell
Date: Fri, 8 Jan 2021 16:36:28 +0100 [thread overview]
Message-ID: <CAK8P3a2Ed5C+Ym3ANBSSgGKVHrhVZJ3-pJAhn_PATRz7f61Adw@mail.gmail.com> (raw)
In-Reply-To: <20210104162843.GA1875909@robh.at.kernel.org>
On Mon, Jan 4, 2021 at 5:28 PM Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Dec 10, 2020 at 02:03:11PM -0600, Rob Herring wrote:
> > PicoXcell has had nothing but treewide cleanups for at least the last 8
> > years and no signs of activity. The most recent activity is a yocto vendor
> > kernel based on v3.0 in 2015.
> >
> > These patches can go via the respective maintainers' trees.
>
> Arnd, Olof,
>
> Can you apply patches 1 and 2. The others have been applied.
Done now. I've created a new top-level branch, as there are some other
platforms that I think can be removed.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: DTML <devicetree@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>, Jamie Iles <jamie@jamieiles.com>,
"David S. Miller" <davem@davemloft.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] Remove PicoXcell
Date: Fri, 8 Jan 2021 16:36:28 +0100 [thread overview]
Message-ID: <CAK8P3a2Ed5C+Ym3ANBSSgGKVHrhVZJ3-pJAhn_PATRz7f61Adw@mail.gmail.com> (raw)
Message-ID: <20210108153628.9pQeycIg7MC8wRXA7_gkr5y08L6w_CQHWne3awku6sI@z> (raw)
In-Reply-To: <20210104162843.GA1875909@robh.at.kernel.org>
On Mon, Jan 4, 2021 at 5:28 PM Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Dec 10, 2020 at 02:03:11PM -0600, Rob Herring wrote:
> > PicoXcell has had nothing but treewide cleanups for at least the last 8
> > years and no signs of activity. The most recent activity is a yocto vendor
> > kernel based on v3.0 in 2015.
> >
> > These patches can go via the respective maintainers' trees.
>
> Arnd, Olof,
>
> Can you apply patches 1 and 2. The others have been applied.
Done now. I've created a new top-level branch, as there are some other
platforms that I think can be removed.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-08 15:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 20:03 [PATCH 0/4] Remove PicoXcell Rob Herring
2020-12-10 20:03 ` Rob Herring
2020-12-10 20:03 ` [PATCH 1/4] ARM: dts: Remove PicoXcell platforms Rob Herring
2020-12-10 20:03 ` Rob Herring
2020-12-10 20:03 ` [PATCH 2/4] ARM: Remove PicoXcell platform support Rob Herring
2020-12-10 20:03 ` Rob Herring
2020-12-10 20:03 ` [PATCH 3/4] crypto: Remove PicoXcell driver Rob Herring
2020-12-10 20:03 ` Rob Herring
2020-12-10 20:28 ` Ard Biesheuvel
2020-12-10 20:28 ` Ard Biesheuvel
2021-01-02 22:04 ` Herbert Xu
2021-01-02 22:04 ` Herbert Xu
2020-12-10 20:03 ` [PATCH 4/4] dt-bindings: Remove PicoXcell bindings Rob Herring
2020-12-10 20:03 ` Rob Herring
2020-12-14 14:34 ` Rob Herring
2020-12-14 14:34 ` Rob Herring
2021-07-17 21:26 ` Geert Uytterhoeven
2021-07-17 21:26 ` Geert Uytterhoeven
2021-07-17 21:26 ` Geert Uytterhoeven
2020-12-13 16:25 ` [PATCH 0/4] Remove PicoXcell Jamie Iles
2020-12-13 16:25 ` Jamie Iles
2021-01-04 16:28 ` Rob Herring
2021-01-04 16:28 ` Rob Herring
2021-01-08 15:36 ` Arnd Bergmann [this message]
2021-01-08 15:36 ` Arnd Bergmann
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=CAK8P3a2Ed5C+Ym3ANBSSgGKVHrhVZJ3-pJAhn_PATRz7f61Adw@mail.gmail.com \
--to=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=soc@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.