linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Paul Burton <paul.burton@mips.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] mips: sgi-ip27: switch from DISCONTIGMEM to SPARSEMEM
Date: Mon, 16 Sep 2019 12:07:10 +0200	[thread overview]
Message-ID: <20190916100710.GA5838@alpha.franken.de> (raw)
In-Reply-To: <20190916095233.GB5196@rapoport-lnx>

On Mon, Sep 16, 2019 at 12:52:35PM +0300, Mike Rapoport wrote:
> On Mon, Sep 16, 2019 at 11:07:05AM +0200, Thomas Bogendoerfer wrote:
> > Patch is good. I've compared bootlogs and output is the same
> > regarding memblock/memory debug messages.
> 
> Can I add your co-developed+signed-off then?

yes :-)

Thomas.

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

      reply	other threads:[~2019-09-16 10:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05  5:47 [PATCH] mips: sgi-ip27: switch from DISCONTIGMEM to SPARSEMEM Mike Rapoport
2019-09-05 13:21 ` Thomas Bogendoerfer
2019-09-05 13:32   ` Mike Rapoport
2019-09-05 13:48     ` Thomas Bogendoerfer
2019-09-05 15:47       ` Mike Rapoport
2019-09-05 21:38         ` Thomas Bogendoerfer
2019-09-06 13:02           ` Mike Rapoport
2019-09-09 16:22             ` Thomas Bogendoerfer
2019-09-10 11:32               ` Mike Rapoport
2019-09-10 12:44                 ` Thomas Bogendoerfer
2019-09-11 14:09                 ` Thomas Bogendoerfer
2019-09-11 14:57                   ` Mike Rapoport
2019-09-12 10:58                   ` Mike Rapoport
2019-09-12 13:55                     ` Thomas Bogendoerfer
2019-09-12 14:09                       ` Thomas Bogendoerfer
2019-09-12 15:58                         ` Mike Rapoport
2019-09-14 10:41                         ` Mike Rapoport
2019-09-16  9:07                           ` Thomas Bogendoerfer
2019-09-16  9:52                             ` Mike Rapoport
2019-09-16 10:07                               ` Thomas Bogendoerfer [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=20190916100710.GA5838@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul.burton@mips.com \
    --cc=rppt@kernel.org \
    --cc=rppt@linux.ibm.com \
    /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).