linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
	ARM-SoC Maintainers <arm@kernel.org>, SoC Team <soc@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	tee-dev@lists.linaro.org
Subject: Re: [GIT PULL] tee subsystem pin_user_pages for v5.8
Date: Fri, 21 Aug 2020 14:18:53 -0700	[thread overview]
Message-ID: <CAOesGMjKq3ECJuaMANq=AyDMLXYvorafMYS3LDr9YMH6M9VdYA@mail.gmail.com> (raw)
In-Reply-To: <f7c8bb6e-e732-2565-8b50-20f5504701c9@nvidia.com>

On Fri, Aug 21, 2020 at 12:58 PM John Hubbard <jhubbard@nvidia.com> wrote:
>
> On 8/21/20 11:49 AM, Olof Johansson wrote:
> > On Tue, May 26, 2020 at 03:12:59PM +0200, Jens Wiklander wrote:
> >> Hello arm-soc maintainers,
> >>
> >> Please pull this small patch converting the tee subsystem to use
> >> pin_user_pages() instead of get_user_pages().
> >>
> >> Thanks,
> >> Jens
> >>
> >> The following changes since commit ae83d0b416db002fe95601e7f97f64b59514d936:
> >>
> >>    Linux 5.7-rc2 (2020-04-19 14:35:30 -0700)
> >>
> >> are available in the Git repository at:
> >>
> >>    git://git.linaro.org:/people/jens.wiklander/linux-tee.git tags/tee-pin-user-pages-for-5.8
> >>
> >> for you to fetch changes up to 37f6b4d5f47b600ec4ab6682c005a44a1bfca530:
> >>
> >>    tee: convert get_user_pages() --> pin_user_pages() (2020-05-26 10:42:41 +0200)
> >
> > Hi, I noticed this never got merged, but I don't see any follow-up here that
> > retracts it. Is it still pending merge such that I should queue it for v5.10?
> >
>
> I think so. I had marked it in my notes as "accepted, and the maintainer will
> eventually merge it", and I left it at that. It's still desirable.
>

Looks like it conflicts with some of the later work. Jens, given the
timelines here it's probably easiest all around if you rebase/respin
and send a fresh pull request. I could fix it up but you'd still need
to review that so the amount of work is probably less if you do it
directly.


-Olof

  reply	other threads:[~2020-08-21 21:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 13:12 [GIT PULL] tee subsystem pin_user_pages for v5.8 Jens Wiklander
2020-08-21 18:49 ` Olof Johansson
2020-08-21 19:58   ` John Hubbard
2020-08-21 21:18     ` Olof Johansson [this message]
2020-08-24  6:51       ` Jens Wiklander
2020-08-24  7:18         ` John Hubbard
2020-08-24  7:46           ` Jens Wiklander
2020-08-24 18:36             ` [PATCH v2] tee: convert convert get_user_pages() --> pin_user_pages() John Hubbard
2020-08-24 18:42               ` John Hubbard
2020-08-24 21:11             ` [PATCH v3] " John Hubbard
2020-08-25  8:32               ` Jens Wiklander
2020-08-25  8:54                 ` John Hubbard
2020-08-25  9:02                   ` Jens Wiklander

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='CAOesGMjKq3ECJuaMANq=AyDMLXYvorafMYS3LDr9YMH6M9VdYA@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=jens.wiklander@linaro.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=tee-dev@lists.linaro.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).