linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Rob Herring <robh@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] gpio: xlp: Remove Netlogic XLP variants
Date: Wed, 1 Dec 2021 17:49:49 +0100	[thread overview]
Message-ID: <CAMRc=MeK-q6sb093Jz8mtVrAQfe6G_NXry+tq86GQ1CVGRvyng@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+4a3FTW1yrM_PjX3_eDwb=Y6GV7PgpxyFiDVARTg5_Ug@mail.gmail.com>

On Wed, Dec 1, 2021 at 4:01 PM Rob Herring <robh@kernel.org> wrote:
>
> On Wed, Dec 1, 2021 at 2:25 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> >
> > On Tue, Nov 30, 2021 at 8:58 PM Rob Herring <robh@kernel.org> wrote:
> > >
> > > Netlogic XLP was removed in commit 95b8a5e0111a ("MIPS: Remove NETLOGIC
> > > support"). With those gone, the single platform left to support is
> > > Cavium ThunderX2. Remove all the Netlogic variants and DT support.
> > >
> > > For simplicity, the existing kconfig name is retained.
> > >
> > > Cc: Linus Walleij <linus.walleij@linaro.org>
> > > Cc: Bartosz Golaszewski <brgl@bgdev.pl>
> > > Cc: linux-gpio@vger.kernel.org
> > > Signed-off-by: Rob Herring <robh@kernel.org>
> > > ---
> > > v2:
> > >  - Fix !OF and ACPI build errors
> > >
> >
> > Rob,
> >
> > This doesn't apply on top of v5.16-rc1. Anything I'm missing?
>
> It should, that's exactly what it is based on. You dropped v1 that you
> already applied?
>
> Rob

Ah right, didn't see that. Can you send a follow-up that applies on
top of my for-next branch?

Bart

      reply	other threads:[~2021-12-01 16:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 19:58 [PATCH v2] gpio: xlp: Remove Netlogic XLP variants Rob Herring
2021-12-01  8:25 ` Bartosz Golaszewski
2021-12-01 15:01   ` Rob Herring
2021-12-01 16:49     ` Bartosz Golaszewski [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='CAMRc=MeK-q6sb093Jz8mtVrAQfe6G_NXry+tq86GQ1CVGRvyng@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sfr@canb.auug.org.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).