All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-mm@kvack.org, kexec@lists.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Uladzislau Rezki <urezki@gmail.com>,
	Christoph Hellwig <hch@lst.de>, Baoquan He <bhe@redhat.com>,
	x86@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore
Date: Thu, 7 Apr 2022 07:38:27 +0200	[thread overview]
Message-ID: <20220407053827.GB13500@lst.de> (raw)
In-Reply-To: <52f819991051f9b865e9ce25605509bfdbacadcd.1649277321.git.osandov@fb.com>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>


WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: kexec@lists.infradead.org
Subject: [PATCH v2] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore
Date: Thu, 7 Apr 2022 07:38:27 +0200	[thread overview]
Message-ID: <20220407053827.GB13500@lst.de> (raw)
In-Reply-To: <52f819991051f9b865e9ce25605509bfdbacadcd.1649277321.git.osandov@fb.com>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>


  reply	other threads:[~2022-04-07  5:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:36 [PATCH v2] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore Omar Sandoval
2022-04-06 20:36 ` Omar Sandoval
2022-04-07  5:38 ` Christoph Hellwig [this message]
2022-04-07  5:38   ` Christoph Hellwig
2022-04-07  8:11 ` Uladzislau Rezki
2022-04-07  8:11   ` Uladzislau Rezki
2022-04-07 14:36 ` Chris Down
2022-04-07 14:36   ` Chris Down
2022-04-08  3:02   ` Baoquan He
2022-04-08  3:02     ` Baoquan He
2022-04-13 16:24     ` Omar Sandoval
2022-04-13 16:24       ` Omar Sandoval
2022-04-14 10:32       ` Baoquan He
2022-04-14 10:32         ` Baoquan He

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=20220407053827.GB13500@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=kernel-team@fb.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=osandov@osandov.com \
    --cc=urezki@gmail.com \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.