From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: linux-next: build warning after merge of the dma-mapping tree
Date: Wed, 2 Sep 2020 17:25:59 +0200 [thread overview]
Message-ID: <20200902152559.GA2053@lst.de> (raw)
In-Reply-To: <20200902100317.142db5be@canb.auug.org.au>
Adding Santosh,
I'm trying to understand the code that Jim changed for the range
dma offsets. Do I miss something or can the whole DMA offset case
for keystone only happen when CONFIG_LPAE is enabled? Which means
we could ifdef out this section to avoid the warning?
next prev parent reply other threads:[~2020-09-02 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 0:03 linux-next: build warning after merge of the dma-mapping tree Stephen Rothwell
2020-09-02 15:25 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 11:48 Stephen Rothwell
2022-07-27 18:32 ` Logan Gunthorpe
2022-07-28 2:23 ` Akira Yokosawa
2022-07-28 8:57 ` Bagas Sanjaya
2021-08-18 22:54 Stephen Rothwell
2021-08-19 7:02 ` Christoph Hellwig
2021-08-13 7:11 Stephen Rothwell
2021-09-03 6:45 ` Stephen Rothwell
2021-09-06 12:41 ` Christoph Hellwig
2018-10-01 22:35 Stephen Rothwell
2018-10-02 14:22 ` Christoph Hellwig
2017-09-03 22:34 Stephen Rothwell
2017-09-04 5:51 ` Christoph Hellwig
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=20200902152559.GA2053@lst.de \
--to=hch@lst.de \
--cc=james.quinlan@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ssantosh@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.