linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Hongchen Zhang <zhanghongchen@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: fix pmd_mkinvalid
Date: Thu, 7 Jul 2022 11:22:06 +0200	[thread overview]
Message-ID: <20220707092206.GA9894@alpha.franken.de> (raw)
In-Reply-To: <1657181495-33004-1-git-send-email-zhanghongchen@loongson.cn>

On Thu, Jul 07, 2022 at 04:11:35PM +0800, Hongchen Zhang wrote:
> When a pmd entry is invalidated by pmd_mkinvalid,pmd_present should
> return true.
> So introduce a _PMD_PRESENT_INVALID_SHIFT bit to check if a pmd is
> present but invalidated by pmd_mkinvalid.

What problem are you trying to fix ? What are the symptoms ?

> Reported-by: kernel test robot <lkp@intel.com>

the test robot showed problems with your last version of the patch,
which hasn't been integrated into at least the MIPS tree, so no
need to that.

Thomas.

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

  reply	other threads:[~2022-07-07 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  8:11 [PATCH] MIPS: fix pmd_mkinvalid Hongchen Zhang
2022-07-07  9:22 ` Thomas Bogendoerfer [this message]
2022-07-07 11:12   ` Hongchen Zhang
2022-07-12 10:01     ` Hongchen Zhang
2022-07-12 11:19       ` Thomas Bogendoerfer
2022-07-12 12:08         ` Hongchen Zhang
  -- strict thread matches above, loose matches on Subject: below --
2022-07-06  9:07 Hongchen Zhang
2022-07-06 19:23 ` kernel test robot
2022-05-31  4:36 Hongchen Zhang
2022-05-31 15:40 ` Jiaxun Yang
2022-06-01  0:55   ` Hongchen Zhang

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=20220707092206.GA9894@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=zhanghongchen@loongson.cn \
    /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).