From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [resend PATCH] MAINTAINERS: Clarify UIO vs UACCESS maintainer
Date: Sat, 13 Oct 2018 05:07:27 +0100 [thread overview]
Message-ID: <20181013040727.GM32577@ZenIV.linux.org.uk> (raw)
In-Reply-To: <153902452503.3147008.1742604660028168607.stgit@dwillia2-desk3.amr.corp.intel.com>
On Mon, Oct 08, 2018 at 11:50:09AM -0700, Dan Williams wrote:
> The UIO file mask in MAINTAINERS was incorrectly directing UACCESS
> (include/linux/uio.h) patches to Greg.
>
> Tag Al as the UACCESS maintainer as Ingo and others have explicitly
> required his ack before taking architecture patches that touch
> lib/iov_iter.c.
>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Reported-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> I got a bounce last time I tried to send this, hopefully the situation
> has improved now.
>
> Al, let me know if you want this entry. Alternatively we can just do the
> UIO file mask fixup by itself.
Sure, no problem, except that UACCESS refers to different things.
I'd probably call it UIOVEC, if we want a name that does refer to the
same somewhere (*BSD). If anything, it's generalization of copyin/copyout
for non-userland destinations/sources; uaccess answer to (subset of) the
same problem would be set_fs()/get_fs() and the fewer we have left of that,
the better...
prev parent reply other threads:[~2018-10-13 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 18:50 [resend PATCH] MAINTAINERS: Clarify UIO vs UACCESS maintainer Dan Williams
2018-10-13 4:07 ` Al Viro [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=20181013040727.GM32577@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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