On 8/23/19 2:26 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190822:
>
> The thermal tree gained a conflict against the jc_docs tree.
>
> The rdma tree gained a conflict against the rdma-fixes tree.
>
> The net-next tree gained conflicts against the pci tree.
>
> The crypto tree
Hi all,
Changes since 20190822:
The thermal tree gained a conflict against the jc_docs tree.
The rdma tree gained a conflict against the rdma-fixes tree.
The net-next tree gained conflicts against the pci tree.
The crypto tree gained a conflict against Linus' tree.
The drm tree gained a
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 20180822:
New tree: at91-fixes
The kbuild tree gained a build failure so I used the version from
next-20180822.
Non-merge commits (relative to Linus' tree):
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 20180822:
New tree: at91-fixes
The kbuild tree gained a build failure so I used the version from
next-20180822.
Non-merge commits (relative to Linus' tree):
Hi all,
Changes since 20170822:
The net-next tree still had its build failure for which I reverted
a commit. It also gained a conflict against the net tree.
The slave-dma tree lost its build failure.
Non-merge commits (relative to Linus' tree): 8264
8196 files changed, 453593 insertions(+),
Hi all,
Changes since 20170822:
The net-next tree still had its build failure for which I reverted
a commit. It also gained a conflict against the net tree.
The slave-dma tree lost its build failure.
Non-merge commits (relative to Linus' tree): 8264
8196 files changed, 453593 insertions(+),
Hi all,
Changes since 20160822:
The drm-intel tree gained a build failure so I used the veriosn from
next-20160822.
The kbuild tree still had its build warnings for PowerPC, for which I
reverted a commit.
The sound-asoc tree gained a build failure so I used the version from
next-20160822.
Hi all,
Changes since 20160822:
The drm-intel tree gained a build failure so I used the veriosn from
next-20160822.
The kbuild tree still had its build warnings for PowerPC, for which I
reverted a commit.
The sound-asoc tree gained a build failure so I used the version from
next-20160822.
On Tue, Sep 02, 2014 at 10:21:26PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 02, 2014 at 12:04:45PM -0700, Guenter Roeck wrote:
>
> > I provided qemu images and instructions as follows.
> > http://server.roeck-us.net/qemu/mipsel/ MIPS 32 bit, little
> > endian
> >
On Tue, Sep 02, 2014 at 12:04:45PM -0700, Guenter Roeck wrote:
> I provided qemu images and instructions as follows.
> http://server.roeck-us.net/qemu/mipsel/ MIPS 32 bit, little
> endian
> http://server.roeck-us.net/qemu/mips64el/ MIPS 64 bit, little
> endian
>
> Let
On Tue, Sep 02, 2014 at 11:55:53AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
> > On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
> > > On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
> > > > Yes, the problem is
On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
> On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
> > On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
> > > Yes, the problem is still seen in next-140829. See qemu test results at
> > >
On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
> On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
> > On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
> > > Yes, the problem is still seen in next-140829. See qemu test results at
> > >
On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
> On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
> > Yes, the problem is still seen in next-140829. See qemu test results at
> > http://server.roeck-us.net:8010/builders.
> >
> > I provided sparc64 images at
On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
Yes, the problem is still seen in next-140829. See qemu test results at
http://server.roeck-us.net:8010/builders.
I provided sparc64 images at
On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
Yes, the problem is still seen in next-140829. See qemu test results at
On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
Yes, the problem is still seen in next-140829. See qemu test results at
On Tue, Sep 02, 2014 at 11:55:53AM +0200, Peter Zijlstra wrote:
On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
Yes, the problem is still seen in
On Tue, Sep 02, 2014 at 12:04:45PM -0700, Guenter Roeck wrote:
I provided qemu images and instructions as follows.
http://server.roeck-us.net/qemu/mipsel/ MIPS 32 bit, little
endian
http://server.roeck-us.net/qemu/mips64el/ MIPS 64 bit, little
endian
Let me
On Tue, Sep 02, 2014 at 10:21:26PM +0200, Peter Zijlstra wrote:
On Tue, Sep 02, 2014 at 12:04:45PM -0700, Guenter Roeck wrote:
I provided qemu images and instructions as follows.
http://server.roeck-us.net/qemu/mipsel/ MIPS 32 bit, little
endian
On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
> Yes, the problem is still seen in next-140829. See qemu test results at
> http://server.roeck-us.net:8010/builders.
>
> I provided sparc64 images at http://server.roeck-us.net/qemu/sparc64/.
> The README file includes instructions
On 09/01/2014 08:58 AM, Peter Zijlstra wrote:
On Sun, Aug 24, 2014 at 09:57:41PM -0700, Guenter Roeck wrote:
On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
Hi all,
Changes since 20140822:
The mfd tree gained a build failure so I used the version from
next-20140822.
The
On Sun, Aug 24, 2014 at 09:57:41PM -0700, Guenter Roeck wrote:
> On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20140822:
> >
> > The mfd tree gained a build failure so I used the version from
> > next-20140822.
> >
> > The usb-gadget tree
On Sun, Aug 24, 2014 at 09:57:41PM -0700, Guenter Roeck wrote:
On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
Hi all,
Changes since 20140822:
The mfd tree gained a build failure so I used the version from
next-20140822.
The usb-gadget tree gained a conflict
On 09/01/2014 08:58 AM, Peter Zijlstra wrote:
On Sun, Aug 24, 2014 at 09:57:41PM -0700, Guenter Roeck wrote:
On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
Hi all,
Changes since 20140822:
The mfd tree gained a build failure so I used the version from
next-20140822.
The
On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
Yes, the problem is still seen in next-140829. See qemu test results at
http://server.roeck-us.net:8010/builders.
I provided sparc64 images at http://server.roeck-us.net/qemu/sparc64/.
The README file includes instructions on how
On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140822:
>
> The mfd tree gained a build failure so I used the version from
> next-20140822.
>
> The usb-gadget tree gained a conflict against the usb-gadget-fixes tree.
>
> The pwm tree gained a
On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
Hi all,
Changes since 20140822:
The mfd tree gained a build failure so I used the version from
next-20140822.
The usb-gadget tree gained a conflict against the usb-gadget-fixes tree.
The pwm tree gained a build failure
Hi all,
Changes since 20140822:
The mfd tree gained a build failure so I used the version from
next-20140822.
The usb-gadget tree gained a conflict against the usb-gadget-fixes tree.
The pwm tree gained a build failure for which I reverted a couple of
commits.
The staging tree still had its
Hi all,
Changes since 20140822:
The mfd tree gained a build failure so I used the version from
next-20140822.
The usb-gadget tree gained a conflict against the usb-gadget-fixes tree.
The pwm tree gained a build failure for which I reverted a couple of
commits.
The staging tree still had its
At Thu, 23 Aug 2012 09:56:34 -0700,
Randy Dunlap wrote:
>
> On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20120822:
> >
>
>
>
> on i386:
>
> CC sound/isa/cmi8328.o
> sound/isa/cmi8328.c: In function 'snd_cmi8328_remove':
>
On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120822:
>
on i386:
CC sound/isa/cmi8328.o
sound/isa/cmi8328.c: In function 'snd_cmi8328_remove':
sound/isa/cmi8328.c:416:24: error: 'cmi' undeclared (first use in this function)
sound/isa/cmi8328.c:416:24:
On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120822:
>
on i386:
CC drivers/staging/iio/gyro/adis16260_core.o
drivers/staging/iio/gyro/adis16260_core.c: In function 'adis16260_probe':
drivers/staging/iio/gyro/adis16260_core.c:655:7: warning: passing
On Thu, Aug 23, 2012 at 10:09 PM, Randy Dunlap wrote:
> On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20120822:
>>
>
>
> on i386:
>
> CC [M] drivers/bus/omap-ocp2scp.o
> drivers/bus/omap-ocp2scp.c:70:1: error: '__mod_of_device_table' aliased to
> undefined
On Thu, Aug 23, 2012 at 10:09 PM, Randy Dunlap rdun...@xenotime.net wrote:
On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
Hi all,
Changes since 20120822:
on i386:
CC [M] drivers/bus/omap-ocp2scp.o
drivers/bus/omap-ocp2scp.c:70:1: error: '__mod_of_device_table' aliased to
On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
Hi all,
Changes since 20120822:
on i386:
CC drivers/staging/iio/gyro/adis16260_core.o
drivers/staging/iio/gyro/adis16260_core.c: In function 'adis16260_probe':
drivers/staging/iio/gyro/adis16260_core.c:655:7: warning: passing
On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
Hi all,
Changes since 20120822:
on i386:
CC sound/isa/cmi8328.o
sound/isa/cmi8328.c: In function 'snd_cmi8328_remove':
sound/isa/cmi8328.c:416:24: error: 'cmi' undeclared (first use in this function)
sound/isa/cmi8328.c:416:24:
At Thu, 23 Aug 2012 09:56:34 -0700,
Randy Dunlap wrote:
On 08/22/2012 10:22 PM, Stephen Rothwell wrote:
Hi all,
Changes since 20120822:
on i386:
CC sound/isa/cmi8328.o
sound/isa/cmi8328.c: In function 'snd_cmi8328_remove':
sound/isa/cmi8328.c:416:24: error: 'cmi'
Hi all,
Changes since 20120822:
New tree: pstore
The tip tree gained a conflict against the rr tree.
The rcu tree gained a conflict against the tip tree.
The kvm tree gained a build failure so I used the version from
next-20120822.
The drivers-x86 tree still has its build failure so I used
Hi all,
Changes since 20120822:
New tree: pstore
The tip tree gained a conflict against the rr tree.
The rcu tree gained a conflict against the tip tree.
The kvm tree gained a build failure so I used the version from
next-20120822.
The drivers-x86 tree still has its build failure so I used
40 matches
Mail list logo
