linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Arnd Bergmann <arnd@arndb.de>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] MIPS: TXx9: Convert SPI platform data to software nodes
Date: Wed, 8 Dec 2021 23:07:59 +0100	[thread overview]
Message-ID: <20211208220759.GA6406@alpha.franken.de> (raw)
In-Reply-To: <YbDtiC5CJJGSL/9C@smile.fi.intel.com>

On Wed, Dec 08, 2021 at 07:38:16PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 29, 2021 at 01:30:17PM +0100, Geert Uytterhoeven wrote:
> > On Mon, Nov 29, 2021 at 1:21 PM Thomas Bogendoerfer
> > <tsbogend@alpha.franken.de> wrote:
> > > On Fri, Nov 26, 2021 at 01:16:22PM +0100, Geert Uytterhoeven wrote:
> 
> ...
> 
> > > are you ok with completly removing rbtx4938 support ? Can I rbtx4939
> > > board support, too ?
> > 
> > Fine for me, I only have rbtx4927.
> 
> Is there any news? I still see my patch well applied against latest Linux Next.
> If the removal is going to be postponed, consider applying this patch then. So
> we may move forward.

https://lore.kernel.org/all/20211130164558.85584-1-tsbogend@alpha.franken.de/

The second patch in that series touches drivers/mtd so I'm waiting for
a Acked-by. But I could apply the first patch...

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2021-12-08 22:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 10:23 [PATCH v1 1/1] MIPS: TXx9: Convert SPI platform data to software nodes Andy Shevchenko
2021-11-26 10:58 ` Arnd Bergmann
2021-11-26 12:16   ` Geert Uytterhoeven
2021-11-26 14:41     ` Andy Shevchenko
2021-11-26 17:37       ` Thomas Bogendoerfer
2021-11-29 11:28         ` Andy Shevchenko
2021-11-29 12:02           ` Thomas Bogendoerfer
2021-11-29 12:20     ` Thomas Bogendoerfer
2021-11-29 12:30       ` Geert Uytterhoeven
2021-11-29 13:05         ` Thomas Bogendoerfer
2021-11-29 19:01           ` Geert Uytterhoeven
2022-01-18 19:59             ` Maciej W. Rozycki
2022-01-18 20:37               ` Geert Uytterhoeven
2021-12-08 17:38         ` Andy Shevchenko
2021-12-08 22:07           ` Thomas Bogendoerfer [this message]
2021-12-09 10:12             ` Andy Shevchenko
2021-12-09 10:51               ` Thomas Bogendoerfer

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=20211208220759.GA6406@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.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 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).