On Tue, Apr 11, 2023 at 08:47:10PM +0200, Daniel Vetter wrote:
> On Tue, Apr 11, 2023 at 12:37:23PM -0600, Jeffrey Hugo wrote:
> > On 4/11/2023 12:21 PM, Daniel Vetter wrote:
> > > On Tue, Apr 11, 2023 at 11:18:29AM -0600, Jeffrey Hugo wrote:
> > > > On 4/11/2023 10:31 AM, Daniel Vetter wrote:
> >
On Tue, Apr 11, 2023 at 12:37:23PM -0600, Jeffrey Hugo wrote:
> On 4/11/2023 12:21 PM, Daniel Vetter wrote:
> > On Tue, Apr 11, 2023 at 11:18:29AM -0600, Jeffrey Hugo wrote:
> > > On 4/11/2023 10:31 AM, Daniel Vetter wrote:
> > > > On Tue, Apr 11, 2023 at 09:29:27AM -0600, Jeffrey Hugo wrote:
> > >
On 4/11/2023 12:21 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 11:18:29AM -0600, Jeffrey Hugo wrote:
On 4/11/2023 10:31 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 09:29:27AM -0600, Jeffrey Hugo wrote:
On 4/11/2023 9:26 AM, Jeffrey Hugo wrote:
On 4/11/2023 9:13 AM, Greg KH wrote:
O
On Tue, Apr 11, 2023 at 11:18:29AM -0600, Jeffrey Hugo wrote:
> On 4/11/2023 10:31 AM, Daniel Vetter wrote:
> > On Tue, Apr 11, 2023 at 09:29:27AM -0600, Jeffrey Hugo wrote:
> > > On 4/11/2023 9:26 AM, Jeffrey Hugo wrote:
> > > > On 4/11/2023 9:13 AM, Greg KH wrote:
> > > > > On Tue, Apr 11, 2023 a
On 4/11/2023 10:31 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 09:29:27AM -0600, Jeffrey Hugo wrote:
On 4/11/2023 9:26 AM, Jeffrey Hugo wrote:
On 4/11/2023 9:13 AM, Greg KH wrote:
On Tue, Apr 11, 2023 at 09:08:39AM -0600, Jeffrey Hugo wrote:
On 4/11/2023 9:01 AM, Daniel Vetter wrote:
On
On Tue, Apr 11, 2023 at 09:29:27AM -0600, Jeffrey Hugo wrote:
> On 4/11/2023 9:26 AM, Jeffrey Hugo wrote:
> > On 4/11/2023 9:13 AM, Greg KH wrote:
> > > On Tue, Apr 11, 2023 at 09:08:39AM -0600, Jeffrey Hugo wrote:
> > > > On 4/11/2023 9:01 AM, Daniel Vetter wrote:
> > > > > On Tue, Apr 11, 2023 at
On 4/11/2023 9:26 AM, Jeffrey Hugo wrote:
On 4/11/2023 9:13 AM, Greg KH wrote:
On Tue, Apr 11, 2023 at 09:08:39AM -0600, Jeffrey Hugo wrote:
On 4/11/2023 9:01 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 12:40:28PM +0200, Greg KH wrote:
On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vet
On 4/11/2023 9:13 AM, Greg KH wrote:
On Tue, Apr 11, 2023 at 09:08:39AM -0600, Jeffrey Hugo wrote:
On 4/11/2023 9:01 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 12:40:28PM +0200, Greg KH wrote:
On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 02:38:1
On Tue, Apr 11, 2023 at 09:08:39AM -0600, Jeffrey Hugo wrote:
> On 4/11/2023 9:01 AM, Daniel Vetter wrote:
> > On Tue, Apr 11, 2023 at 12:40:28PM +0200, Greg KH wrote:
> > > On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vetter wrote:
> > > > On Tue, Apr 11, 2023 at 02:38:12PM +1000, Stephen Roth
On 4/11/2023 9:01 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 12:40:28PM +0200, Greg KH wrote:
On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vetter wrote:
On Tue, Apr 11, 2023 at 02:38:12PM +1000, Stephen Rothwell wrote:
Hi all,
After merging the driver-core tree, today's linux-next b
On Tue, Apr 11, 2023 at 12:40:28PM +0200, Greg KH wrote:
> On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vetter wrote:
> > On Tue, Apr 11, 2023 at 02:38:12PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > After merging the driver-core tree, today's linux-next build (x86_64
> > > allmo
On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vetter wrote:
> On Tue, Apr 11, 2023 at 02:38:12PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the driver-core tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from include/lin
On Tue, Apr 11, 2023 at 02:38:12PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the driver-core tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/linux/linkage.h:7,
> from include/linux/kernel.h:17,
>
Hi all,
After merging the driver-core tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/linkage.h:7,
from include/linux/kernel.h:17,
from drivers/accel/qaic/mhi_qaic_ctrl.c:4:
drivers/accel/qaic/mhi_qaic_ct
Hi all,
After merging the driver-core tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpu/drm/../../accel/drm_accel.c: In function 'accel_sysfs_init':
drivers/gpu/drm/../../accel/drm_accel.c:41:30: error: assignment to 'char *
(*)(const struct device *, umode_t *)'
Hi,
On Tue, Aug 10, 2021 at 5:13 AM Geert Uytterhoeven wrote:
>
> On Fri, Jul 23, 2021 at 7:35 AM Uwe Kleine-König
> wrote:
> > On Fri, Jul 23, 2021 at 03:09:44PM +1000, Stephen Rothwell wrote:
> > > After merging the driver-core tree, today's linux-next build (arm
> > > multi_v7_defconfig) fail
On Fri, Jul 23, 2021 at 7:35 AM Uwe Kleine-König
wrote:
> On Fri, Jul 23, 2021 at 03:09:44PM +1000, Stephen Rothwell wrote:
> > After merging the driver-core tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > drivers/gpu/drm/drm_dp_aux_bus.c:106:13: error: initia
Hello Stephen,
On Fri, Jul 23, 2021 at 03:09:44PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the driver-core tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpu/drm/drm_dp_aux_bus.c:106:13: error: initialization of 'void
> (*)(struct devic
Hi all,
After merging the driver-core tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpu/drm/drm_dp_aux_bus.c:106:13: error: initialization of 'void
(*)(struct device *)' from incompatible pointer type 'int (*)(struct device *)'
[-Werror=incompatible-pointer-t
19 matches
Mail list logo