From: Joe Perches <joe@perches.com>
To: Christoph Hellwig <hch@lst.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfds: Fix NFSD_MDS_PR_KEY on 32-bit by adding ULL postfix
Date: Fri, 25 Mar 2016 11:25:17 -0700 [thread overview]
Message-ID: <1458930317.29362.3.camel@perches.com> (raw)
In-Reply-To: <20160325180422.GA15549@lst.de>
On Fri, 2016-03-25 at 19:04 +0100, Christoph Hellwig wrote:
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Outside of the known 64 bit only uses,
this shows a few oddities too:
$ git grep -P -w -i '0x[0-9a-f]{9,16}(?!ull|ll)'
next prev parent reply other threads:[~2016-03-25 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 10:47 [PATCH] nfds: Fix NFSD_MDS_PR_KEY on 32-bit by adding ULL postfix Geert Uytterhoeven
2016-03-25 18:04 ` Christoph Hellwig
2016-03-25 18:25 ` Joe Perches [this message]
2016-03-28 23:48 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2016-06-05 9:23 Geert Uytterhoeven
2016-06-05 10:21 ` Jeff Layton
2016-06-06 18:56 ` J. Bruce Fields
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=1458930317.29362.3.camel@perches.com \
--to=joe@perches.com \
--cc=bfields@fieldses.org \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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).