From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: jens.wiklander@linaro.org, tee-dev@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: optee: Fix compilation issue.
Date: Tue, 21 Jan 2020 18:18:36 +0100 [thread overview]
Message-ID: <20200121171836.GA674326@kroah.com> (raw)
In-Reply-To: <f4134c26-231f-968a-7fc3-0427af9a886e@arm.com>
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
next prev parent reply other threads:[~2020-01-21 17:18 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 [this message]
2020-01-22 8:03 ` Jens Wiklander
2020-01-22 9:37 ` Vincenzo Frascino
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=20200121171836.GA674326@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.