mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"tee-dev @ lists . linaro . org" <tee-dev@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: optee: Fix compilation issue.
Date: Thu, 23 Jan 2020 11:15:49 +0100	[thread overview]
Message-ID: <20200123101548.GB10320@jax> (raw)
In-Reply-To: <6862c452-4280-7999-a03f-1184e1a03015@arm.com>

On Wed, Jan 22, 2020 at 09:37:28AM +0000, Vincenzo Frascino wrote:
> Hi Jens,
> 
> On 22/01/2020 08:03, Jens Wiklander wrote:
> > Hi Vincenzo,
> > 
> > On Tue, Jan 21, 2020 at 6:18 PM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> >>
> >> On Tue, Jan 21, 2020 at 03:27:47PM +0000, Vincenzo Frascino wrote:
> >>> Hi Greg,
> >>>
> >>> On 21/01/2020 15:20, Greg Kroah-Hartman wrote:
> >>>> On Tue, Jan 21, 2020 at 02:23:02PM +0000, Vincenzo Frascino wrote:
> >>>>> Hi Greg,
> >>>>>
> >>>>> I sent the fix below few days ago to the optee maintaners but I did not get any
> >>>>> answer. Could you please pick it up?
> >>>>
> >>>>      $ ./scripts/get_maintainer.pl --file drivers/tee/optee/Kconfig
> >>>>     Jens Wiklander <jens.wiklander@linaro.org> (maintainer:OP-TEE DRIVER)
> >>>>     tee-dev@lists.linaro.org (open list:OP-TEE DRIVER)
> >>>>     linux-kernel@vger.kernel.org (open list)
> >>>>
> >>>> This should go through Jens, why me?
> >>>>
> >>>
> >>> I added Jens and tee-dev list in copy already but as I was mentioning in my
> >>> previous email I did not get any answer. I thought that since it is a small fix
> >>> you could help. Sorry if I made a mistake.
> >>
> >> Give people time to catch up on email, especially for obscure issues
> >> like this.
> >>
> >> thanks,
> >>
> >> greg k-h
> > 
> > I'll pick up this patch.
> > 
> 
> Thanks for this, since it might break the build in some cases, do you think it
> there any chance it can end up in 5.5? I know it might be late.

I've just sent a pull request with this commit to arm-soc. It's their
decision if it's passed on for 5.5 or if it's too late.

Cheers,
Jens

  reply	other threads:[~2020-01-23 10:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 12:28 Vincenzo Frascino
2020-01-21 14:23 ` Vincenzo Frascino
2020-01-21 15:20   ` Greg Kroah-Hartman
2020-01-21 15:27     ` Vincenzo Frascino
2020-01-21 17:18       ` Greg Kroah-Hartman
2020-01-22  8:03         ` Jens Wiklander
2020-01-22  9:37           ` Vincenzo Frascino
2020-01-23 10:15             ` Jens Wiklander [this message]
2020-01-22  9:36         ` Vincenzo Frascino

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=20200123101548.GB10320@jax \
    --to=jens.wiklander@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tee-dev@lists.linaro.org \
    --cc=vincenzo.frascino@arm.com \
    /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

all inboxes | Powered by JetHome®