linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org
Cc: Arnd Bergmann <arnd@kernel.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	linux-mips@vger.kernel.org,
	"Matthew Wilcox \(Oracle\)" <willy@infradead.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Matteo Croce <mcroce@linux.microsoft.com>,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] Fix struct page layout on 32-bit systems
Date: Sat, 10 Apr 2021 21:52:44 +0100	[thread overview]
Message-ID: <20210410205246.507048-1-willy@infradead.org> (raw)

I'd really appreciate people testing this, particularly on
arm32/mips32/ppc32 systems with a 64-bit dma_addr_t.

Matthew Wilcox (Oracle) (1):
  mm: Fix struct page layout on 32-bit systems

 include/linux/mm_types.h | 38 ++++++++++++++++++++++++++------------
 1 file changed, 26 insertions(+), 12 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-04-10 20:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 20:52 Matthew Wilcox (Oracle) [this message]
2021-04-10 20:52 ` [PATCH 1/1] mm: Fix struct page layout on 32-bit systems Matthew Wilcox (Oracle)
2021-04-11  9:43   ` Jesper Dangaard Brouer
2021-04-11 10:33     ` Matthew Wilcox
2021-04-12  1:15       ` Matthew Wilcox
2021-04-14  8:10         ` Jesper Dangaard Brouer
2021-04-14 11:50           ` Matthew Wilcox
2021-04-14 11:56             ` Ilias Apalodimas
2021-04-14 15:52             ` David Laight
2021-04-14 19:13             ` Jesper Dangaard Brouer
2021-04-14 21:35               ` Matthew Wilcox
2021-04-14 21:56                 ` David Laight
2021-04-15 18:08                   ` Jesper Dangaard Brouer
2021-04-15 18:21                     ` Matthew Wilcox
2021-04-15 21:11                       ` David Laight
2021-04-15 22:22                         ` Matthew Wilcox
2021-04-16  7:32                           ` David Laight
2021-04-16 11:05                             ` Matthew Wilcox
2021-04-16 15:27                     ` Matthew Wilcox
2021-04-16 17:08                       ` Jesper Dangaard Brouer
2021-04-17  3:19                         ` Matthew Wilcox
2021-04-17 10:31                       ` Arnd Bergmann
2021-04-17 13:56                         ` Matthew Wilcox
2021-04-17 17:30                           ` Arnd Bergmann
2021-04-17 10:59                       ` David Laight
2021-04-19  6:34                       ` Christoph Hellwig
2021-04-19  7:15                         ` Ilias Apalodimas
2021-04-12 18:23     ` Matthew Wilcox
2021-04-13  8:21       ` David Laight

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=20210410205246.507048-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=arnd@kernel.org \
    --cc=brouer@redhat.com \
    --cc=grygorii.strashko@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=ivan.khoronzhuk@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mcroce@linux.microsoft.com \
    --cc=netdev@vger.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 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).