public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the arc-current tree
Date: Tue, 1 Sep 2020 21:36:56 +1000	[thread overview]
Message-ID: <20200901213656.4d216c83@canb.auug.org.au> (raw)
In-Reply-To: <20200901091308.GD424181@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

Hi Mike,

On Tue, 1 Sep 2020 12:13:08 +0300 Mike Rapoport <rppt@linux.ibm.com> wrote:
>
> On Tue, Sep 01, 2020 at 06:49:28PM +1000, Stephen Rothwell wrote:
> > 
> > In commit
> > 
> >   7000c9462d1b ("arc: fix memory initialization for systems with two memory banks")
> > 
> > Fixes tag
> > 
> >   Fixes: 51930df5801e ("mm: free_area_init: allow defining max_zone_pfn in descend ing order")  
> 
> It's line rewrapping:                                                               ^

Yeah, wrapped and then unwrapped with an extra space :-(

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-09-01 11:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01  8:49 linux-next: Fixes tag needs some work in the arc-current tree Stephen Rothwell
2020-09-01  9:13 ` Mike Rapoport
2020-09-01 11:36   ` Stephen Rothwell [this message]
2020-09-01 18:25     ` Vineet Gupta
  -- strict thread matches above, loose matches on Subject: below --
2022-04-18 20:40 Stephen Rothwell
2022-04-19 16:47 ` Vineet Gupta
2019-01-17 20:56 Stephen Rothwell
2019-01-17 20:32 Stephen Rothwell
2019-01-17 20:52 ` Vineet Gupta

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=20200901213656.4d216c83@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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