Ping!

Can somebody please at least post a comment what is needed to get this upstream?

Thanks
David

On Wed, Apr 9, 2014 at 1:33 AM, Aaron Plattner <[email protected]> wrote:
> Keith, any news on this?  Did this miss 1.16?
>
>
> On 03/28/2014 12:43 PM, David Herrmann wrote:
>>
>> Any comments on that? Anything we can do to get that merged?
>>
>> Thanks
>> David
>>
>> On Fri, Mar 14, 2014 at 4:54 PM, Aaron Plattner <[email protected]>
>> wrote:
>>>
>>> Keith asked me to resend these.
>>>
>>> I rebased this on top of the systemd-logind work that Hans de Goede did
>>> and
>>> verified that it still works.
>>>
>>> Thierry Reding (5):
>>>    xfree86: Make driver matching consistent
>>>    xfree86: Store kernel driver name in platform device attribute
>>>    xfree86: Introduce OutputClass configuration
>>>    xfree86: Support driver loading via OutputClass
>>>    xfree86: Make error message more readable
>>>
>>>   hw/xfree86/common/xf86AutoConfig.c         |   2 +-
>>>   hw/xfree86/common/xf86pciBus.c             |  24 ++---
>>>   hw/xfree86/common/xf86pciBus.h             |   5 +-
>>>   hw/xfree86/common/xf86platformBus.c        |  85 ++++++++++++++-
>>>   hw/xfree86/man/xorg.conf.man               |  77 +++++++++++++
>>>   hw/xfree86/os-support/linux/lnx_platform.c |  17 ++-
>>>   hw/xfree86/parser/Makefile.am              |   1 +
>>>   hw/xfree86/parser/OutputClass.c            | 167
>>> +++++++++++++++++++++++++++++
>>>   hw/xfree86/parser/configProcs.h            |   5 +
>>>   hw/xfree86/parser/read.c                   |   6 ++
>>>   hw/xfree86/parser/write.c                  |   2 +
>>>   hw/xfree86/parser/xf86Parser.h             |   9 ++
>>>   include/hotplug.h                          |   2 +
>>>   13 files changed, 378 insertions(+), 24 deletions(-)
>>>   create mode 100644 hw/xfree86/parser/OutputClass.c
>>>
>>> --
>>> 1.9.0
_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to