public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Youling Tang <tangyouling@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: crash_dump.c: Simplify copy_oldmem_page()
Date: Tue, 9 Feb 2021 13:36:23 +0100	[thread overview]
Message-ID: <20210209123623.GC11264@alpha.franken.de> (raw)
In-Reply-To: <1612682649-3389-1-git-send-email-tangyouling@loongson.cn>

On Sun, Feb 07, 2021 at 03:24:09PM +0800, Youling Tang wrote:
> Replace kmap_atomic_pfn() with kmap_local_pfn() which is preemptible and
> can take page faults.
> 
> Remove the indirection of the dump page and the related cruft which is not
> longer required.
> 
> Remove unused or redundant header files.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Youling Tang <tangyouling@loongson.cn>
> ---
> 
> v2:
>  - Keep the crash_dump.h header file included to avoid the
>    "no previous prototype for function" warning.
> 
>  arch/mips/kernel/crash_dump.c | 41 ++++++-----------------------------------
>  1 file changed, 6 insertions(+), 35 deletions(-)

applied to mips-next.

Thomas.

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

      reply	other threads:[~2021-02-09 12:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07  7:24 [PATCH v2] MIPS: crash_dump.c: Simplify copy_oldmem_page() Youling Tang
2021-02-09 12:36 ` 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=20210209123623.GC11264@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tangyouling@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