Hi all,
Changes since 20190724:
New tree: fpga
The vfs-fixes tree prodices a BUG in my qemu tests, so I have reverted
a commit for today.
The jc_docs tree gained a conflict against Linus' tree.
The net-next tree gained conflicts against the net and jc_docs trees.
The leds tree gained a build
On 07/24/2018 11:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180724:
>
on i386:
net/ipv4/netfilter/nft_chain_nat_ipv4.o: In function `nft_nat_do_chain':
nft_chain_nat_ipv4.c:(.text+0x67): undefined reference to `nft_do_chain'
net/ipv4/netfilter/nft_chain_nat_ipv4.o: In function
On Wed, Jul 25, 2018 at 04:44:08PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180724:
>
> Dropped trees: xarray, ida (complex conflicts)
>
> The xarray tree still had its complex conflicts against the nvdimm tree
> so I have dropped it again for today (along with the ida tree t
Hi all,
Changes since 20180724:
Dropped trees: xarray, ida (complex conflicts)
The xarray tree still had its complex conflicts against the nvdimm tree
so I have dropped it again for today (along with the ida tree that is
built on top of it).
The akpm-current tree still had its build failure for
Hi all,
Changes since 20170724:
New tree: wberr
Non-merge commits (relative to Linus' tree): 2223
2355 files changed, 84862 insertions(+), 43462 deletions(-)
I have created today's linux-next tree at
git://git.kernel
On 07/24/16 23:17, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160724:
>
on i386, when CONFIG_FB is not enabled:
../drivers/gpu/drm/udl/udl_fb.c: In function 'udl_fb_open':
../drivers/gpu/drm/udl/udl_fb.c:206:23: error: 'struct fb_info' has no member
named 'fbdefio'
if (fb_defio &&
Hi all,
Changes since 20160724:
The powerpc tree still had its build failure for which I applied a fix patch.
The vfs tree gained conflicts against the f2fs and overlayfs trees.
The nvdimm tree gained a conflict against the kvm tree.
Non-merge commits (relative to Linus' tree): 11060
10157 fi
Hi all,
Changes since 20140724:
New tree: hch-vfs
The arm-soc tree gained a conflict against the arm tree.
The samsung tree gained a conflict against the arm tree.
The v4l-dvb tree gained a build failure so I used the version from
next-20140724.
The tip tree gained a conflict aginst the net-n
On Fri, Jul 26, 2013 at 01:25:21PM +0800, Shawn Guo wrote:
> On Fri, Jul 26, 2013 at 04:58:14AM +, Zhu Richard-R65037 wrote:
> > Hi Shawn:
> > yes, it is.
> >
> > BTW, Should I re-send the AHCI_IMX patch-set or send out one stand-alone
> > patch to fix this issue?
> >
>
> I think an increme
On Fri, Jul 26, 2013 at 11:32 AM, Sedat Dilek wrote:
> On Fri, Jul 26, 2013 at 11:16 AM, Daniel Vetter
> wrote:
>> On Fri, Jul 26, 2013 at 11:11 AM, Sedat Dilek wrote:
>>
>>> I have compared next-20130725 VS. next-20130726:
>>>
>>> $ head -2313 next-20130725-VS-next-20130726.diff | grep ^+ | gr
On Fri, Jul 26, 2013 at 11:16 AM, Daniel Vetter wrote:
> On Fri, Jul 26, 2013 at 11:11 AM, Sedat Dilek wrote:
>
>> I have compared next-20130725 VS. next-20130726:
>>
>> $ head -2313 next-20130725-VS-next-20130726.diff | grep ^+ | grep i915
>> + drm/i915: Colocate all GT access routines in t
On Fri, Jul 26, 2013 at 11:11 AM, Sedat Dilek wrote:
> I have compared next-20130725 VS. next-20130726:
>
> $ head -2313 next-20130725-VS-next-20130726.diff | grep ^+ | grep i915
> + drm/i915: Colocate all GT access routines in the same file
> + drm/i915: Use a private interface for reg
On Fri, Jul 26, 2013 at 11:02 AM, Sedat Dilek wrote:
> On Fri, Jul 26, 2013 at 10:52 AM, Daniel Vetter
> wrote:
>> On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson
>> wrote:
>>> On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote:
On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek
On Fri, Jul 26, 2013 at 10:52 AM, Daniel Vetter wrote:
> On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson
> wrote:
>> On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote:
>>> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek wrote:
>>> > ...
>>> > ... but does not start as well, so it seems t
On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson wrote:
> On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote:
>> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek wrote:
>> > ...
>> > ... but does not start as well, so it seems to be a kernel-issue as
>> > assumed (2nd confirmation).
>> >
>> >
On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote:
> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek wrote:
> > ...
> > ... but does not start as well, so it seems to be a kernel-issue as
> > assumed (2nd confirmation).
> >
> > X.log attached.
> >
>
> Now, really w/ promised attachment.
On Fri, Jul 26, 2013 at 9:26 AM, Chris Wilson wrote:
> On Fri, Jul 26, 2013 at 09:15:14AM +0200, Sedat Dilek wrote:
>> For example: I could start my X with even doing ugly hacks like this...
>>
>> [ intel-ddx (git) ]
>> ...
>> Bool intel_uxa_create_screen_resources(ScreenPtr screen)
>> ...
>> #if
On Fri, Jul 26, 2013 at 09:15:14AM +0200, Sedat Dilek wrote:
> For example: I could start my X with even doing ugly hacks like this...
>
> [ intel-ddx (git) ]
> ...
> Bool intel_uxa_create_screen_resources(ScreenPtr screen)
> ...
> #if 0
> if (drm_intel_gem_bo_map_gtt(bo))
> re
On Fri, Jul 26, 2013 at 1:25 AM, Chris Wilson wrote:
> On Fri, Jul 26, 2013 at 01:21:07AM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson
>> wrote:
>> > On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote:
>> >> What means the bang line?
>> >>
>> >> [54.56
On Fri, Jul 26, 2013 at 04:58:14AM +, Zhu Richard-R65037 wrote:
> Hi Shawn:
> yes, it is.
>
> BTW, Should I re-send the AHCI_IMX patch-set or send out one stand-alone
> patch to fix this issue?
>
I think an incremental fixing patch is good.
Shawn
--
To unsubscribe from this list: send the
PM
To: Zhu Richard-R65037
Cc: Randy Dunlap; Stephen Rothwell; linux-n...@vger.kernel.org;
linux-kernel@vger.kernel.org; linux-...@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 25 (ahci_imx.c)
On Fri, Jul 26, 2013 at 03:46:42AM +, Zhu Richard-R65037 wrote:
> -Original Message
l.org;
> linux-...@vger.kernel.org; Zhu Richard-R65037
> Subject: Re: linux-next: Tree for Jul 25 (ahci_imx.c)
>
> On 07/24/13 22:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20130724:
> >
>
> on i386:
>
> # CONFIG_MFD_SYSCON is not set
&g
ll
Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org;
linux-...@vger.kernel.org; Zhu Richard-R65037
Subject: Re: linux-next: Tree for Jul 25 (ahci_imx.c)
On 07/24/13 22:12, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130724:
>
on i386:
# CONFIG_MFD_SYSCON
On Fri, Jul 26, 2013 at 01:21:07AM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson
> wrote:
> > On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote:
> >> What means the bang line?
> >>
> >> [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0
> >> [
On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson wrote:
> On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote:
>> What means the bang line?
>>
>> [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0
>> [54.565] bang: 1159
>> [54.565]
>> Fatal server error:
>> [54.565]
On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote:
> What means the bang line?
>
> [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0
> [54.565] bang: 1159
> [54.565]
> Fatal server error:
> [54.565] failed to create screen resources
That means between the kern
On Thu, Jul 25, 2013 at 9:32 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 9:22 PM, Chris Wilson
> wrote:
>> On Thu, Jul 25, 2013 at 09:12:41PM +0200, Sedat Dilek wrote:
>>> New -3 dmesg.
>>
>> That puts the ball back in the ddx's court. Next debugging patch:
>>
>> diff --git a/src/intel_driv
On Thu, Jul 25, 2013 at 09:12:41PM +0200, Sedat Dilek wrote:
> New -3 dmesg.
That puts the ball back in the ddx's court. Next debugging patch:
diff --git a/src/intel_driver.c b/src/intel_driver.c
index f4d76bb..1f4f299 100644
--- a/src/intel_driver.c
+++ b/src/intel_driver.c
@@ -170,6 +170,7 @@ s
On Thu, Jul 25, 2013 at 08:50:59PM +0200, Sedat Dilek wrote:
> Against what tree is this applicable? It is definitely not drm-intel-nightly.
Applied cleanly to nightly here, but just in case here's a rebased version:
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
i
On Thu, Jul 25, 2013 at 8:45 PM, Chris Wilson wrote:
> On Thu, Jul 25, 2013 at 08:03:06PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 7:55 PM, Sedat Dilek wrote:
>> > F*ck. Wrong patch refreshed.
>> >
>>
>> New dmesg attached.
>
> Hmm, not seeing any difference, so let's add a couple mor
On Thu, Jul 25, 2013 at 08:03:06PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 7:55 PM, Sedat Dilek wrote:
> > F*ck. Wrong patch refreshed.
> >
>
> New dmesg attached.
Hmm, not seeing any difference, so let's add a couple more lines just to
be sure:
(apologies I didn't stash the previou
On Thu, Jul 25, 2013 at 07:52:22PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson
> wrote:
> > On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote:
> >> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson
> >> wrote:
> >> > Basically boils down to either an object a
On Thu, Jul 25, 2013 at 7:52 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson
> wrote:
>> On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote:
>>> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson
>>> wrote:
>>> > Basically boils down to either an object allocation fa
On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson wrote:
> On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson
>> wrote:
>> > Basically boils down to either an object allocation failure or mmaping
>> > failure. I think dmesg with drm.debug=7
On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson
> wrote:
> > Basically boils down to either an object allocation failure or mmaping
> > failure. I think dmesg with drm.debug=7 is the next step.
>
> Attached! Thanks for taking care.
Hm
On Thu, Jul 25, 2013 at 06:35:10PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 6:31 PM, Chris Wilson
> wrote:
> > On Thu, Jul 25, 2013 at 06:11:18PM +0200, Sedat Dilek wrote:
> >> Might be OT, but I cannot use my X graphics stack containing
> >> libdrm-2.4.46, mesa-9.1.5 and intel-ddx 2.2
On Thu, Jul 25, 2013 at 06:11:18PM +0200, Sedat Dilek wrote:
> Might be OT, but I cannot use my X graphics stack containing
> libdrm-2.4.46, mesa-9.1.5 and intel-ddx 2.21.12-git (tried also
> v2.21.11).
> Switching back to the one from Ubuntu/precise lets my X start.
>
>
> [40.379] (II) AIGLX
On Thu, Jul 25, 2013 at 5:34 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 5:05 PM, Daniel Vetter wrote:
>> On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote:
>>> On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
> On
On Thu, Jul 25, 2013 at 5:05 PM, Daniel Vetter wrote:
> On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
>>> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
>
On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
>> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
>>> On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
>>> > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote:
> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
>> > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
>> >> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula
>> >>
On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
> > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
> >> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula
> >> wrote:
> >> > On Thu, 25 Jul 2013, Sedat Dilek wrote:
> >>
On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote:
> On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula
>> wrote:
>> > On Thu, 25 Jul 2013, Sedat Dilek wrote:
>> >> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek
>> >> wrote:
>> >>> O
On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula
> wrote:
> > On Thu, 25 Jul 2013, Sedat Dilek wrote:
> >> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek
> >> wrote:
> >>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula
> >>> wrote:
> >>
On Thu, 25 Jul 2013, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek wrote:
>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula
>> wrote:
>>> On Thu, 25 Jul 2013, Sedat Dilek wrote:
On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell
wrote:
> Hi all,
>
> Ch
Hi all,
Changes since 20130724:
Removed tree:
arm-dt (at maintainer's request)
The wireless-next tree lost its build failure and gained a conflict
against Linus' tree.
The tty tree lost its build failure.
The staging tree gained a build failure for which I disabled a driver.
-
46 matches
Mail list logo
