On Fri, 25 Jul 2014, Martin Kepplinger wrote:
> Am 2014-07-25 01:20, schrieb Hugh Dickins:
> >
> > [PATCH] drm/i915: fix freeze with blank screen booting highmem
>
> yes! thanks Hugh. On top of linus' current tree, that finally fixes my
> problem! I hope it'll be included soon!
I'm glad to hear
On Fri, 25 Jul 2014, Martin Kepplinger wrote:
Am 2014-07-25 01:20, schrieb Hugh Dickins:
[PATCH] drm/i915: fix freeze with blank screen booting highmem
yes! thanks Hugh. On top of linus' current tree, that finally fixes my
problem! I hope it'll be included soon!
I'm glad to hear it,
Am 2014-07-25 01:20, schrieb Hugh Dickins:
> On Thu, 24 Jul 2014, Martin Kepplinger wrote:
>> Am 2014-06-30 12:39, schrieb Martin Kepplinger:
>>> back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>>> commit. why is this not revertable exactly? how can I show a complete
>>> list of
Am 2014-07-25 01:20, schrieb Hugh Dickins:
On Thu, 24 Jul 2014, Martin Kepplinger wrote:
Am 2014-06-30 12:39, schrieb Martin Kepplinger:
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this
On Thu, 24 Jul 2014, Martin Kepplinger wrote:
> Am 2014-06-30 12:39, schrieb Martin Kepplinger:
> > back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
> > commit. why is this not revertable exactly? how can I show a complete
> > list of commits this merge introduces?
> >
>
> It
Martin Kepplinger wrote:
Am 2014-06-30 12:39, schrieb Martin Kepplinger:
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?
It seems that _nobody_ is running a simple 32
Am 2014-06-30 12:39, schrieb Martin Kepplinger:
> back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
> commit. why is this not revertable exactly? how can I show a complete
> list of commits this merge introduces?
>
It seems that _nobody_ is running a simple 32 bit i915 (acer)
Am 2014-06-30 12:39, schrieb Martin Kepplinger:
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?
It seems that _nobody_ is running a simple 32 bit i915 (acer) laptop.
Martin Kepplinger wrote:
Am 2014-06-30 12:39, schrieb Martin Kepplinger:
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?
It seems that _nobody_ is running a simple 32
On Thu, 24 Jul 2014, Martin Kepplinger wrote:
Am 2014-06-30 12:39, schrieb Martin Kepplinger:
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?
It seems that
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
12 matches
Mail list logo