Re: linux-next: build failure after merge of the drm-misc tree

On Tue, Apr 2, 2019 at 3:57 PM Daniel Vetter wrote: > > On Tue, Apr 02, 2019 at 01:55:03PM +0800, Qiang Yu wrote: > > Thanks, patch is: > > Reviewed-by: Qiang Yu > > Good time to get started with committing patches? In general it's kinda > confusing if the maintainer r-bs a patch, but doesn't

Re: linux-next: build failure after merge of the drm-misc tree

On Tue, Apr 02, 2019 at 01:55:03PM +0800, Qiang Yu wrote: > Thanks, patch is: > Reviewed-by: Qiang Yu Good time to get started with committing patches? In general it's kinda confusing if the maintainer r-bs a patch, but doesn't say whether/when/how it gets merged. Big chance the patch will get

Re: linux-next: build failure after merge of the drm-misc tree

Thanks, patch is: Reviewed-by: Qiang Yu Regards, Qiang On Tue, Apr 2, 2019 at 7:50 AM Stephen Rothwell wrote: > > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/kernel.h:7, >

Re: linux-next: build failure after merge of the drm-misc tree

Hi Daniel/Stephen Thanks for the report and the hints how to move forward to fix it. > Sam, can you pls take a look at what komeda needs? you need to > manually merge together drm-misc-next and drm-next first I think. Merged the two tree and fixed build. Undid the merge and checked that the

Re: linux-next: build failure after merge of the drm-misc tree

On Fri, Feb 8, 2019 at 2:38 AM Stephen Rothwell wrote: > > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/gpu/drm/arm/display/komeda/komeda_drv.c:13: >

Re: linux-next: build failure after merge of the drm-misc tree

Hi Daniel, On Tue, 8 Jan 2019 09:37:22 +0100 Daniel Vetter wrote: > > > https://cgit.freedesktop.org/drm-tip/tree/fixups/drm-misc-next.patch?h=rerere-cache > > is the fixup you want. Should get baked into drm-next any moment, since > the first drm-misc-next pull is already out. I added that

Re: linux-next: build failure after merge of the drm-misc tree

On 1/8/19 3:37 AM, Daniel Vetter wrote: > On Tue, Jan 08, 2019 at 11:12:41AM +1100, Stephen Rothwell wrote: >> Hi all, >> >> After merging the drm-misc tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In

Re: linux-next: build failure after merge of the drm-misc tree

On Tue, Jan 08, 2019 at 11:12:41AM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In function > 'amdgpu_dm_mode_config_init': >

Re: linux-next: build failure after merge of the drm-misc tree

Hi Stephen, yeah, that is a known problem. I missed the change during rebase of the revert. Please see patch "2312f9842854 drm/v3d: fix broken build" which is already in drm-misc-next and fixes the issue. Christian. Am 06.12.18 um 03:32 schrieb Stephen Rothwell: > Hi all, > > After merging

Re: linux-next: build failure after merge of the drm-misc tree

On Mon, Jul 24, 2017 at 10:24:41AM +0200, Daniel Vetter wrote: > On Mon, Jul 24, 2017 at 2:03 AM, Stephen Rothwell > wrote: > > Hi Daniel, > > > > On Fri, 21 Jul 2017 09:24:49 +0200 Daniel Vetter > > wrote: > >> > >> How are we going to handle

Re: linux-next: build failure after merge of the drm-misc tree

On Mon, Jul 24, 2017 at 2:03 AM, Stephen Rothwell wrote: > Hi Daniel, > > On Fri, 21 Jul 2017 09:24:49 +0200 Daniel Vetter > wrote: >> >> How are we going to handle this now? The refactor is deeply burried in >> drm-misc, I guess you could

Re: linux-next: build failure after merge of the drm-misc tree

Hi Daniel, On Fri, 21 Jul 2017 09:24:49 +0200 Daniel Vetter wrote: > > How are we going to handle this now? The refactor is deeply burried in > drm-misc, I guess you could cherry-pick the relevant patches over. But > that'll probably lead to more conflicts because git

Re: linux-next: build failure after merge of the drm-misc tree

Hi, On 21-07-17 09:24, Daniel Vetter wrote: Hi Greg, How are we going to handle this now? The refactor is deeply burried in drm-misc, I guess you could cherry-pick the relevant patches over. But that'll probably lead to more conflicts because git will get confused. Or you could just delete

Re: linux-next: build failure after merge of the drm-misc tree

Hi Greg, How are we going to handle this now? The refactor is deeply burried in drm-misc, I guess you could cherry-pick the relevant patches over. But that'll probably lead to more conflicts because git will get confused. Or you could just delete the set_busid hook in -staging, which renders the

Re: linux-next: build failure after merge of the drm-misc tree

Hi Dave, The following is now applicable to the drm and staging.current trees ... On Wed, 19 Jul 2017 11:46:57 +1000 Stephen Rothwell wrote: > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > >

Re: linux-next: build failure after merge of the drm-misc tree

Hi all, On Fri, 21 Apr 2017 12:10:14 +1000 Stephen Rothwell wrote: > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in > initializer >

Re: linux-next: build failure after merge of the drm-misc tree

On Tue, May 2, 2017 at 10:55 AM, Arnd Bergmann wrote: > On Tue, May 2, 2017 at 10:41 AM, Stephen Rothwell > wrote: >> Hi Daniel, >> >> On Tue, 2 May 2017 10:25:18 +0200 Daniel Vetter wrote: >>> >>> Since this is an all-new driver it might

Re: linux-next: build failure after merge of the drm-misc tree

On Tue, May 2, 2017 at 10:41 AM, Stephen Rothwell wrote: > Hi Daniel, > > On Tue, 2 May 2017 10:25:18 +0200 Daniel Vetter wrote: >> >> Since this is an all-new driver it might be best to stagger the pull >> requests and merge the new tee subsystem (or

Re: linux-next: build failure after merge of the drm-misc tree

Hi Daniel, On Tue, 2 May 2017 10:25:18 +0200 Daniel Vetter wrote: > > Since this is an all-new driver it might be best to stagger the pull > requests and merge the new tee subsystem (or whatever it is) after drm? > > Not sure what to best do here ... This will merge via Dave,

Re: linux-next: build failure after merge of the drm-misc tree

On Mon, Apr 24, 2017 at 11:25:12AM +1000, Stephen Rothwell wrote: > Hi all, > > On Fri, 21 Apr 2017 12:10:14 +1000 Stephen Rothwell > wrote: > > > > After merging the drm-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > >

Re: linux-next: build failure after merge of the drm-misc tree

Hi all, On Fri, 21 Apr 2017 12:10:14 +1000 Stephen Rothwell wrote: > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in > initializer >

Re: linux-next: build failure after merge of the drm-misc tree

Thanks Stephen. Looks good to me. Logan On 20/04/17 08:10 PM, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in > initializer

Re: linux-next: build failure after merge of the drm-misc tree

Thanks for this. This and "drm/vmwgfx: merge fixup for set_config API change": Reviewed-by: Sinclair Yeh On Mon, Apr 03, 2017 at 01:31:29PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed

<    1   2