From: Christoph Hellwig <hch@lst.de>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, hch@lst.de, cl@linux.com,
John.p.donnelly@oracle.com, kexec@lists.infradead.org,
42.hyeyoo@gmail.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, David.Laight@ACULAB.COM,
david@redhat.com, x86@kernel.org, bp@alien8.de
Subject: Re: [PATCH v4 2/3] dma/pool: create dma atomic pool only if dma zone has managed pages
Date: Thu, 23 Dec 2021 11:21:14 +0100 [thread overview]
Message-ID: <20211223102114.GA14064@lst.de> (raw)
In-Reply-To: <20211223094435.248523-3-bhe@redhat.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: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, hch@lst.de, cl@linux.com,
John.p.donnelly@oracle.com, kexec@lists.infradead.org,
42.hyeyoo@gmail.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, David.Laight@ACULAB.COM,
david@redhat.com, x86@kernel.org, bp@alien8.de
Subject: Re: [PATCH v4 2/3] dma/pool: create dma atomic pool only if dma zone has managed pages
Date: Thu, 23 Dec 2021 11:21:14 +0100 [thread overview]
Message-ID: <20211223102114.GA14064@lst.de> (raw)
In-Reply-To: <20211223094435.248523-3-bhe@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2021-12-23 10:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 9:44 [PATCH v4 0/3] Handle warning of allocation failure on DMA zone w/o managed pages Baoquan He
2021-12-23 9:44 ` Baoquan He
2021-12-23 9:44 ` [PATCH v4 1/3] mm_zone: add function to check if managed dma zone exists Baoquan He
2021-12-23 9:44 ` Baoquan He
2021-12-23 15:00 ` john.p.donnelly
2021-12-23 15:00 ` john.p.donnelly
2021-12-23 9:44 ` [PATCH v4 2/3] dma/pool: create dma atomic pool only if dma zone has managed pages Baoquan He
2021-12-23 9:44 ` Baoquan He
2021-12-23 10:21 ` Christoph Hellwig [this message]
2021-12-23 10:21 ` Christoph Hellwig
2021-12-23 15:01 ` john.p.donnelly
2021-12-23 15:01 ` john.p.donnelly
2022-01-03 9:34 ` David Hildenbrand
2022-01-03 9:34 ` David Hildenbrand
2021-12-23 9:44 ` [PATCH v4 3/3] mm/page_alloc.c: do not warn allocation failure on zone DMA if no " Baoquan He
2021-12-23 9:44 ` Baoquan He
2021-12-23 15:01 ` john.p.donnelly
2021-12-23 15:01 ` john.p.donnelly
2021-12-25 5:53 ` Hyeonggon Yoo
2021-12-25 5:53 ` Hyeonggon Yoo
2021-12-27 8:32 ` Baoquan He
2021-12-27 8:32 ` Baoquan He
2021-12-28 5:06 ` Hyeonggon Yoo
2021-12-28 5:06 ` Hyeonggon Yoo
2022-01-12 16:25 ` [PATCH v4 0/3] Handle warning of allocation failure on DMA zone w/o " john.p.donnelly
2022-01-12 16:25 ` john.p.donnelly
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=20211223102114.GA14064@lst.de \
--to=hch@lst.de \
--cc=42.hyeyoo@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=John.p.donnelly@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=cl@linux.com \
--cc=david@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--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.