From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Jens Wiklander <jens.wiklander@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "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: Wed, 22 Jan 2020 09:37:28 +0000 [thread overview]
Message-ID: <6862c452-4280-7999-a03f-1184e1a03015@arm.com> (raw)
In-Reply-To: <CAHUa44F1FU6iPqjkk_9ALS0YHc5AVtSzweEt-0RX919cUbU2eA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
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.
> Thanks,
> Jens
>
--
Regards,
Vincenzo
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 14291 bytes --]
next prev parent reply other threads:[~2020-01-22 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 12:28 [PATCH] drivers: optee: Fix compilation issue 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 [this message]
2020-01-23 10:15 ` Jens Wiklander
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=6862c452-4280-7999-a03f-1184e1a03015@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.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).