From: Javier Martinez Canillas <javierm@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms
Date: Fri, 4 Jun 2021 15:29:48 +0200 [thread overview]
Message-ID: <fa85dc40-0972-98e4-f7a4-1aa1e1a6a482@redhat.com> (raw)
In-Reply-To: <YLoakvzpKwL4gVFQ@smile.fi.intel.com>
On 6/4/21 2:20 PM, Andy Shevchenko wrote:
> On Fri, Jun 04, 2021 at 11:41:29AM +0200, Javier Martinez Canillas wrote:
>> On 6/3/21 10:27 PM, Borislav Petkov wrote:
>>> On Tue, Jun 01, 2021 at 04:59:10PM +0200, Javier Martinez Canillas wrote:
[snip]
>
> For myself I wrote a script to try being smart [1]. At least it works for me in
> 99% of the cases. Otherwise I add manually --cc or other related options.
>
> [1]: https://github.com/andy-shev/home-bin-tools/blob/master/ge2maintainer.sh
>
Thanks a lot for the pointer. I'll take a look!
> Feel free to modify (patches also are warmly welcome!).
>
Best regards,
--
Javier Martinez Canillas
Software Engineer
New Platform Technologies Enablement team
RHEL Engineering
prev parent reply other threads:[~2021-06-04 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 14:59 [PATCH v2 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms Javier Martinez Canillas
2021-06-01 14:59 ` [PATCH v2 1/2] drivers/firmware: move x86 Generic System Framebuffers support Javier Martinez Canillas
2021-06-04 13:22 ` Greg Kroah-Hartman
2021-06-03 20:27 ` [PATCH v2 0/2] allow simple{fb,drm} drivers to be used on non-x86 EFI platforms Borislav Petkov
2021-06-04 9:41 ` [PATCH v2 0/2] allow simple{fb, drm} " Javier Martinez Canillas
2021-06-04 12:20 ` [PATCH v2 0/2] allow simple{fb,drm} " Andy Shevchenko
2021-06-04 13:29 ` Javier Martinez Canillas [this message]
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=fa85dc40-0972-98e4-f7a4-1aa1e1a6a482@redhat.com \
--to=javierm@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dri-devel@lists.freedesktop.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).