linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Paul Cercueil <paul@crapouillou.net>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v4 2/2] MIPS: ingenic: Enable JZ4780_NEMC manually
Date: Tue, 28 Jul 2020 13:37:02 +0200	[thread overview]
Message-ID: <20200728113702.GB13443@alpha.franken.de> (raw)
In-Reply-To: <20200728111935.GA26683@kozik-lap>

On Tue, Jul 28, 2020 at 01:19:35PM +0200, Krzysztof Kozlowski wrote:
> On Tue, Jul 28, 2020 at 01:12:11PM +0200, Paul Cercueil wrote:
> > Hi Krzysztof,
> > 
> > Le mar. 28 juil. 2020 à 12:45, Krzysztof Kozlowski <krzk@kernel.org> a écrit
> > :
> > > The CONFIG_JZ4780_NEMC was previously a default on MIPS but now it has
> > > to be enabled manually.
> > > 
> > > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > 
> > I think you should swap the two so that there are no problems when
> > bisecting.
> 
> Good point. I was thinking that it will go via some of MIPS trees and
> the patch #1 will just wait a cycle.  However with acks, I can take it
> through drivers/memory tree.

I've acked the 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:[~2020-07-28 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 10:45 [PATCH v4 1/2] memory: jz4780-nemc: Do not build by default Krzysztof Kozlowski
2020-07-28 10:45 ` [PATCH v4 2/2] MIPS: ingenic: Enable JZ4780_NEMC manually Krzysztof Kozlowski
2020-07-28 11:12   ` Paul Cercueil
2020-07-28 11:19     ` Krzysztof Kozlowski
2020-07-28 11:37       ` Thomas Bogendoerfer [this message]
2020-07-28 12:00         ` Krzysztof Kozlowski
2020-07-28 12:33           ` Thomas Bogendoerfer
2020-07-28 12:51           ` Paul Cercueil
2020-07-28 12:53             ` Krzysztof Kozlowski
2020-07-28 20:51               ` Thomas Bogendoerfer
2020-07-28 11:36   ` 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=20200728113702.GB13443@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=arnd@arndb.de \
    --cc=hns@goldelico.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    /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).