soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	op-tee@lists.trustedfirmware.org,
	 Rui Miguel Silva <rui.silva@linaro.org>
Subject: Re: [GIT PULL] OP-TEE driver for v5.11
Date: Fri, 27 Nov 2020 08:14:59 +0100	[thread overview]
Message-ID: <CAHUa44Fnj4zQ_3O+kdzVopVAggUOdb34KGnA8+r=Rp-4+etWbw@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a2CDp0KwCZjffA78fXUqOfAkvUb8Q=R64830fvvn_WG2w@mail.gmail.com>

Hi Arnd,

On Thu, Nov 26, 2020 at 10:00 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> On Wed, Nov 25, 2020 at 1:01 PM Jens Wiklander
> <jens.wiklander@linaro.org> wrote:
> >
> > Hello arm-soc maintainers,
> >
> > Please pull this small patch which allows the OP-TEE driver to work with
> > ARMv7 based single CPU systems.
>
> Can you rebase that branch onto -rc1? I had started the arm/drivers
> branch early on top of that, so I'd prefer to avoid a backmerged.
>
> For the commit itself, shouldn't that be marked as a bugfix and get
> merged into v5.10 instead? If it should, you don't have to rebase
> since the arm/fixes branch is already ahead.

Yes it is a bit of a bugfix, so if you don't mind taking it as that
I'm sure that Rui would be happy to get it in this release.

>
> Also, it would be nice to Cc linux-arm-kernel on the pull request
> in addition to linux-kernel.

I'll keep that in mind the next time. Thanks for the feedback.

Cheers,
Jens

  reply	other threads:[~2020-11-27  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 12:01 [GIT PULL] OP-TEE driver for v5.11 Jens Wiklander
2020-11-26 21:00 ` Arnd Bergmann
2020-11-27  7:14   ` Jens Wiklander [this message]
2020-11-27  7:14     ` Jens Wiklander
2020-11-27 17:10 ` patchwork-bot+linux-soc
2020-11-27 17:10 ` patchwork-bot+linux-soc

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='CAHUa44Fnj4zQ_3O+kdzVopVAggUOdb34KGnA8+r=Rp-4+etWbw@mail.gmail.com' \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=rui.silva@linaro.org \
    --cc=soc@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).