Hi all,
Changes since 20200820:
My fixes tree is empty again.
The dma-mapping tree lost its qemu test boot failure.
The bpf-next tree gained a build failure for which I disabled BPF_PRELOAD.
The pinctrl-intel tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1973
3350
Hi all,
Changes since 20190820:
The security tree gained conflicts against Linus' tree.
The integrity tree gained a conflict against the security tree.
The iommu tree gained a conflict against the drm-misc tree.
The irqchip tree gained a conflict against the pci tree.
The gpio tree gained a c
Hi all,
Please do not add any v4.20 material to your linux-next included
branches until after v4.19-rc1 has been released.
Changes since 20180820:
The xarray tree gained a conflict against the nvdimm tree.
Non-merge commits (relative to Linus' tree): 2411
2504 files changed, 95839 insertions(+
Hi all,
Changes since 20150820:
The powerpc tree gained a build failure for which I reverted a commit.
The btrfs tree gained a build failure so I used teh version from
next-20150820.
The nfs tree still had its build failure for which I disabled a staging
driver.
The net-next tree lost its buil
On Fri, Aug 23, 2013 at 10:34 AM, Chris Wilson wrote:
> On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
>> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
>> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
>> > wrote:
>> >> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter
>> >
On Fri, Aug 23, 2013 at 10:34 AM, Chris Wilson wrote:
> On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
>> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
>> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
>> > wrote:
>> >> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter
>> >
On Fri, Aug 23, 2013 at 10:34 AM, Chris Wilson wrote:
> On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
>> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
>> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
>> > wrote:
>> >> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter
>> >
On Fri, Aug 23, 2013 at 10:04:37AM +0200, Sedat Dilek wrote:
> On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
> > On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter
> > wrote:
> >> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter
> >> wrote:
> >>> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek
On Fri, Aug 23, 2013 at 9:55 AM, Sedat Dilek wrote:
> On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter wrote:
>> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter
>> wrote:
>>> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek wrote:
dmesg (a lot of traces) and kernel-config attached.
UXA
On Thu, Aug 22, 2013 at 1:32 PM, Daniel Vetter wrote:
> On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter wrote:
>> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek wrote:
>>> dmesg (a lot of traces) and kernel-config attached.
>>>
>>> UXA causes still screen corruption.
>>
>> Hm, was only a slim chanc
On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter wrote:
> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek wrote:
>> dmesg (a lot of traces) and kernel-config attached.
>>
>> UXA causes still screen corruption.
>
> Hm, was only a slim chance that this patch would fix anything - I
> think you'd always s
On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek wrote:
> dmesg (a lot of traces) and kernel-config attached.
>
> UXA causes still screen corruption.
Hm, was only a slim chance that this patch would fix anything - I
think you'd always see an oops when you'd hit this bug instead of just
a bit of corru
On Thu, Aug 22, 2013 at 08:32:47AM +0200, Sedat Dilek wrote:
> It's independent of the applied patch.
> My problem goes away with SNA but still exists with UXA.
>
> As said in my previous analysis... switching back to Ubuntu's graphics
> did not show the symptoms, too.
>
> It's interesting to see
On Wed, Aug 21, 2013 at 11:20 PM, Daniel Vetter wrote:
> On Wed, Aug 21, 2013 at 08:11:27PM +0200, Sedat Dilek wrote:
>> On Wed, Aug 21, 2013 at 3:44 PM, Daniel Vetter wrote:
>> > On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
>> >> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
On Wed, Aug 21, 2013 at 08:11:27PM +0200, Sedat Dilek wrote:
> On Wed, Aug 21, 2013 at 3:44 PM, Daniel Vetter wrote:
> > On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
> >> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
> >> wrote:
> >> > Hi all,
> >> >
> >> > There will be no
On Wed, Aug 21, 2013 at 3:44 PM, Daniel Vetter wrote:
> On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
>> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > There will be no linux-next trees on Aug 23 or 26.
>> >
>> > Changes since 20130820:
>> >
>>
On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > There will be no linux-next trees on Aug 23 or 26.
> >
> > Changes since 20130820:
> >
> > New tree: aio-direct
> >
> > Removed tree: xilinx (at maintaine
On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell
wrote:
> Hi all,
>
> There will be no linux-next trees on Aug 23 or 26.
>
> Changes since 20130820:
>
> New tree: aio-direct
>
> Removed tree: xilinx (at maintainer's request)
>
> The xfs tree still had its build failure for which I reverted a co
Hi all,
There will be no linux-next trees on Aug 23 or 26.
Changes since 20130820:
New tree: aio-direct
Removed tree: xilinx (at maintainer's request)
The xfs tree still had its build failure for which I reverted a commit.
The trivial tree gained conflicts against the crypto, net-next and
wir
19 matches
Mail list logo
