From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jean-Christophe Plagniol-Villard
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>,
Tomi Valkeinen <tomi.valkeinen-l0cyMroinI0@public.gmane.org>,
linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] efifb: show framebuffer layout as device attributes
Date: Tue, 4 Oct 2016 22:27:21 +0100 [thread overview]
Message-ID: <20161004212721.GS16071@codeblueprint.co.uk> (raw)
In-Reply-To: <20161004133520.ecyfshyalxjl5eap-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, 04 Oct, at 09:35:21AM, Peter Jones wrote:
>
> Usually I just funnel anything EFI related through mfleming, since he's
> already doing regular pushes upstream and it's part of his workflow.
> Matt, does that work for you in this case?
I'm happy for this to go through the EFI tree, sure.
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jean-Christophe Plagniol-Villard
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>,
Tomi Valkeinen <tomi.valkeinen-l0cyMroinI0@public.gmane.org>,
linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] efifb: show framebuffer layout as device attributes
Date: Tue, 04 Oct 2016 21:27:21 +0000 [thread overview]
Message-ID: <20161004212721.GS16071@codeblueprint.co.uk> (raw)
In-Reply-To: <20161004133520.ecyfshyalxjl5eap-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, 04 Oct, at 09:35:21AM, Peter Jones wrote:
>
> Usually I just funnel anything EFI related through mfleming, since he's
> already doing regular pushes upstream and it's part of his workflow.
> Matt, does that work for you in this case?
I'm happy for this to go through the EFI tree, sure.
next prev parent reply other threads:[~2016-10-04 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 17:09 [PATCH] efifb: show framebuffer layout as device attributes Peter Jones
2016-10-03 17:09 ` Peter Jones
[not found] ` <20161003170923.15025-1-pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-04 13:31 ` Ard Biesheuvel
2016-10-04 13:31 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-tW51s7ajiAZWWYyN3b_H3qXbXDpGV4Oowf5AiFzmSSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-04 13:35 ` Peter Jones
2016-10-04 13:35 ` Peter Jones
[not found] ` <20161004133520.ecyfshyalxjl5eap-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-04 21:27 ` Matt Fleming [this message]
2016-10-04 21:27 ` Matt Fleming
[not found] ` <20161004212721.GS16071-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-10-05 18:05 ` Ard Biesheuvel
2016-10-05 18:05 ` Ard Biesheuvel
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=20161004212721.GS16071@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org \
--cc=tomi.valkeinen-l0cyMroinI0@public.gmane.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 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.