public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	linux-s390@vger.kernel.org, heiko.carstens@de.ibm.com
Subject: Re: [GIT PULL] s390 patches for 4.20 #2
Date: Fri, 9 Nov 2018 14:40:42 +0100	[thread overview]
Message-ID: <20181109144042.4546b7ce@mschwideX1> (raw)
In-Reply-To: <CAHk-=wj+HK7htwua62MnT9e_vsfgboiACR08MQDsXj9+4WQEBg@mail.gmail.com>

On Fri, 9 Nov 2018 06:39:07 -0600
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Fri, Nov 9, 2018 at 1:14 AM Martin Schwidefsky
> <schwidefsky@de.ibm.com> wrote:
> >
> > s390 updates for 4.20-rc2  
> 
> Pulled.
> 
> >  - A fix for the pgtable_bytes misaccounting on s390. The patch changes
> >    common code part in regard to page table folding and adds extra
> >    checks to mm_[inc|dec]_nr_[pmds|puds].  
> 
> Ugh. This is somewhat invasive, I worry  that some header include or
> architecture doesn't pick up on the subtle __PAGETABLE_XYZ_FOLDED
> things (if you don't get the includes, the mm_xyz_folded() maros will
> be mis-defined.
> 
> Has this been in linux-next or any other wide testing? The changes
> aren't _new_, but...

Just checked linux-next, the first version that picked up the patches
is 2018-11-19. The one dated 2018-10-19 does not have them.

Bad timing, no wider testing has been done. The bug itself shows up
as a false warning, nothing really breaks. I would understand if you
prefer not to have them in the official tree at this time.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

  reply	other threads:[~2018-11-09 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09  7:14 [GIT PULL] s390 patches for 4.20 #2 Martin Schwidefsky
2018-11-09 12:39 ` Linus Torvalds
2018-11-09 13:40   ` Martin Schwidefsky [this message]
2018-11-09 16:30 ` pr-tracker-bot

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=20181109144042.4546b7ce@mschwideX1 \
    --to=schwidefsky@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=torvalds@linux-foundation.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