From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] mm/hugetlb.c: fix printk format warning for 32-bit phys_addr_t
Date: Thu, 19 Mar 2020 18:06:38 -0700 [thread overview]
Message-ID: <933c893a29b6c5aa85758ca6a7e2d2c99170bc11.camel@perches.com> (raw)
In-Reply-To: <58454a65-5022-7517-df65-7bf504cd1432@infradead.org>
On Thu, 2020-03-19 at 18:03 -0700, Randy Dunlap wrote:
> On 3/18/20 7:37 PM, Joe Perches wrote:
> > On Wed, 2020-03-18 at 19:11 -0700, Randy Dunlap wrote:
> > > I'm fairly sure that the [begin, end) notation is done on purpose, meaning
> > >
> > > <begin> is included in the range and <end> is not included in the range.
> >
> > OK, that seems a pretty obscure and not obvious use of
> > interval notation, at least to me. (18 uses treewide ?)
> >
> > Maybe it could be documented somewhere?
>
> I thought about where to put that and came up empty.
No worries then, it's likely not _too_ obscure
to anyone that's sent a log for analysis.
prev parent reply other threads:[~2020-03-20 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 21:33 Randy Dunlap
2020-03-19 2:04 ` Joe Perches
2020-03-19 2:11 ` Randy Dunlap
2020-03-19 2:37 ` Joe Perches
2020-03-20 1:03 ` Randy Dunlap
2020-03-20 1:06 ` Joe Perches [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=933c893a29b6c5aa85758ca6a7e2d2c99170bc11.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.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