From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: don't open-code u64_to_user_ptr
Date: Tue, 21 May 2024 09:24:10 -0700 [thread overview]
Message-ID: <ZkzKqqBK9LcS3UuR@infradead.org> (raw)
In-Reply-To: <20240521150222.GO25518@frogsfrogsfrogs>
On Tue, May 21, 2024 at 08:02:22AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Don't open-code what the kernel already provides.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
I was actually looking for this in a few places and didn't find it
before suggesting the u64 as pointer API, but I couldn't find it.
prev parent reply other threads:[~2024-05-21 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 15:02 [PATCH] xfs: don't open-code u64_to_user_ptr Darrick J. Wong
2024-05-21 16:24 ` Christoph Hellwig [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=ZkzKqqBK9LcS3UuR@infradead.org \
--to=hch@infradead.org \
--cc=chandanbabu@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@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