On Thu, 27 Aug 2020 10:02:57 PDT (-0700), Atish Patra wrote:
On Thu, 2020-08-27 at 10:37 +0200, Anders Roxell wrote:
On Thu, 27 Aug 2020 at 07:11, Stephen Rothwell
wrote:
> Hi all,
>
> News: There will be no linux-next releases next Monday or Tuesday.
>
> Changes since 20200826:
>
> The
On Thu, 2020-08-27 at 10:37 +0200, Anders Roxell wrote:
> On Thu, 27 Aug 2020 at 07:11, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > News: There will be no linux-next releases next Monday or Tuesday.
> >
> > Changes since 20200826:
> >
> > The net-next tree gained a conflict against the net
On Thu, 27 Aug 2020 at 07:11, Stephen Rothwell wrote:
>
> Hi all,
>
> News: There will be no linux-next releases next Monday or Tuesday.
>
> Changes since 20200826:
>
> The net-next tree gained a conflict against the net tree.
>
> Non-merge commits (relative to Linus' tree): 2901
> 3429 files
Hi all,
News: There will be no linux-next releases next Monday or Tuesday.
Changes since 20200826:
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 2901
3429 files changed, 100496 insertions(+), 37081 deletions(-)
On Fri, 30 Aug 2019 15:23:51 +0900
Masami Hiramatsu wrote:
> > Actually I wonder if X86_DECODER_SELFTEST is even still needed these
> > days, since objtool is enabled on default configs. Objtool already uses
> > the decoder to disassemble every instruction in the kernel (except for a
> > few
Hi Josh,
On Thu, 29 Aug 2019 12:59:31 -0500
Josh Poimboeuf wrote:
> On Thu, Aug 29, 2019 at 10:53:56AM +0900, Masami Hiramatsu wrote:
> > Hi Josh,
> >
> > On Wed, 28 Aug 2019 11:34:33 -0500
> > Josh Poimboeuf wrote:
> >
> > > On Wed, Aug 28, 2019 at 11:13:31AM -0500, Josh Poimboeuf wrote:
On Thu, Aug 29, 2019 at 10:53:56AM +0900, Masami Hiramatsu wrote:
> Hi Josh,
>
> On Wed, 28 Aug 2019 11:34:33 -0500
> Josh Poimboeuf wrote:
>
> > On Wed, Aug 28, 2019 at 11:13:31AM -0500, Josh Poimboeuf wrote:
> > > Turns out this patch does break something:
> > >
> > >
Hi Josh,
On Wed, 28 Aug 2019 11:34:33 -0500
Josh Poimboeuf wrote:
> On Wed, Aug 28, 2019 at 11:13:31AM -0500, Josh Poimboeuf wrote:
> > Turns out this patch does break something:
> >
> > arch/x86/xen/enlighten_pv.o: warning: objtool: xen_cpuid()+0x25: can't
> > find jump dest instruction at
On Wed, Aug 28, 2019 at 11:13:31AM -0500, Josh Poimboeuf wrote:
> Turns out this patch does break something:
>
> arch/x86/xen/enlighten_pv.o: warning: objtool: xen_cpuid()+0x25: can't find
> jump dest instruction at .text+0x9c
>
> I'll need to figure out a better way to whitelist that
>
On Wed, Aug 28, 2019 at 09:05:18AM -0700, Randy Dunlap wrote:
> On 8/28/19 8:51 AM, Josh Poimboeuf wrote:
> > On Tue, Aug 27, 2019 at 12:05:42PM -0700, Randy Dunlap wrote:
> >> On 8/27/19 8:59 AM, Josh Poimboeuf wrote:
> >>> On Tue, Aug 27, 2019 at 08:40:07AM -0700, Randy Dunlap wrote:
> On
On 8/28/19 8:51 AM, Josh Poimboeuf wrote:
> On Tue, Aug 27, 2019 at 12:05:42PM -0700, Randy Dunlap wrote:
>> On 8/27/19 8:59 AM, Josh Poimboeuf wrote:
>>> On Tue, Aug 27, 2019 at 08:40:07AM -0700, Randy Dunlap wrote:
On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> Hi all,
>
>
On Tue, Aug 27, 2019 at 12:05:42PM -0700, Randy Dunlap wrote:
> On 8/27/19 8:59 AM, Josh Poimboeuf wrote:
> > On Tue, Aug 27, 2019 at 08:40:07AM -0700, Randy Dunlap wrote:
> >> On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20190826:
> >>>
> >>
> >> on x86_64:
On (08/27/19 08:37), Randy Dunlap wrote:
> on x86_64:
>
> In file included from ../include/linux/mmzone.h:10:0,
> from ../include/linux/gfp.h:6,
> from ../include/linux/umh.h:4,
> from ../include/linux/kmod.h:9,
> from
On 8/27/19 10:09 AM, Brendan Higgins wrote:
On Tue, Aug 27, 2019 at 8:29 AM Randy Dunlap wrote:
On 8/27/19 2:05 AM, Stephen Rothwell wrote:
Hi all,
Changes since 20190826:
on i386:
# CONFIG_PRINTK is not set
../kunit/test.c: In function ‘kunit_vprintk_emit’:
../kunit/test.c:21:9:
On Tue, Aug 27, 2019 at 8:29 AM Randy Dunlap wrote:
>
> On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190826:
> >
>
> on i386:
> # CONFIG_PRINTK is not set
>
>
> ../kunit/test.c: In function ‘kunit_vprintk_emit’:
> ../kunit/test.c:21:9: error: implicit
On Tue, Aug 27, 2019 at 08:40:07AM -0700, Randy Dunlap wrote:
> On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190826:
> >
>
> on x86_64:
>
> arch/x86/kvm/vmx/vmx.o: warning: objtool: vmx_handle_exit_irqoff()+0x33:
> unreachable instruction
>
> > gcc
On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190826:
>
on x86_64:
arch/x86/kvm/vmx/vmx.o: warning: objtool: vmx_handle_exit_irqoff()+0x33:
unreachable instruction
> gcc --version
gcc (SUSE Linux) 7.4.0
want more info?
--
~Randy
On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190826:
>
on x86_64:
In file included from ../include/linux/mmzone.h:10:0,
from ../include/linux/gfp.h:6,
from ../include/linux/umh.h:4,
from ../include/linux/kmod.h:9,
On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190826:
>
on i386:
# CONFIG_PRINTK is not set
../kunit/test.c: In function ‘kunit_vprintk_emit’:
../kunit/test.c:21:9: error: implicit declaration of function ‘vprintk_emit’;
did you mean ‘vprintk’?
On 8/27/19 2:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190826:
>
on i386:
../arch/x86/kernel/cpu/mshyperv.c: In function ‘hv_setup_sched_clock’:
../arch/x86/kernel/cpu/mshyperv.c:349:2: error: ‘pv_ops’ undeclared (first use
in this function); did you mean ‘smp_ops’?
Hi all,
Changes since 20190826:
The vfs tree gained a conflict against the ceph tree.
The phy-next tree gained a build failure so I used the version from
next-20190826.
Non-merge commits (relative to Linus' tree): 8565
8749 files changed, 431821 insertions(+), 250001 deletions(-)
Hi all,
Changes since 20180824:
Dropped trees: xarray, ida (temporarily)
Non-merge commits (relative to Linus' tree): 427
585 files changed, 17988 insertions(+), 5276 deletions(-)
I have created today's linux-next
Hi all,
Changes since 20180824:
Dropped trees: xarray, ida (temporarily)
Non-merge commits (relative to Linus' tree): 427
585 files changed, 17988 insertions(+), 5276 deletions(-)
I have created today's linux-next
Hi all,
Changes since 20180824:
Dropped trees: xarray, ida (temporarily)
Non-merge commits (relative to Linus' tree): 427
585 files changed, 17988 insertions(+), 5276 deletions(-)
I have created today's linux-next
Hi all,
Changes since 20180824:
Dropped trees: xarray, ida (temporarily)
Non-merge commits (relative to Linus' tree): 427
585 files changed, 17988 insertions(+), 5276 deletions(-)
I have created today's linux-next
Hi all,
Changes since 20150826:
The i2c tree lost its build failure.
The slave-dma tree gained conflicts against the pm, mfd and rtc trees.
The block tree gained a conflict against Linus' tree.
The mmc-uh tree still had its build failure so I used the version from
next-20150825.
The tty tree
Hi all,
Changes since 20150826:
The i2c tree lost its build failure.
The slave-dma tree gained conflicts against the pm, mfd and rtc trees.
The block tree gained a conflict against Linus' tree.
The mmc-uh tree still had its build failure so I used the version from
next-20150825.
The tty tree
Hi Laura,
On Wed, 27 Aug 2014 17:56:13 -0700 Laura Abbott wrote:
>
> I sent fixes for this to Andrew yesterday, did those not get picked up
> or fix the problem?
Things do not migrate to mmotm (and hence linux-next) very quickly
(depending on Andrew's load). I don't remember seeing the fix
On 8/27/2014 5:48 PM, Stephen Rothwell wrote:
Hi all,
On Wed, 27 Aug 2014 16:58:09 -0700 Guenter Roeck wrote:
I see a large number of build failures with this kernel.
drivers/base/dma-mapping.c: In function 'dma_common_contiguous_remap':
drivers/base/dma-mapping.c:294:2: error: implicit
Hi all,
On Wed, 27 Aug 2014 16:58:09 -0700 Guenter Roeck wrote:
>
> I see a large number of build failures with this kernel.
>
> drivers/base/dma-mapping.c: In function 'dma_common_contiguous_remap':
> drivers/base/dma-mapping.c:294:2: error: implicit declaration of function
>
On Wed, Aug 27, 2014 at 04:10:21PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140826:
>
> The net tree lost its build failure.
>
> The usb.current tree gained a build failure for which I reverted a commit.
>
> The mfd tree lost its build failure.
>
> The percpu tree gained a
Hi all,
Changes since 20140826:
The net tree lost its build failure.
The usb.current tree gained a build failure for which I reverted a commit.
The mfd tree lost its build failure.
The percpu tree gained a build failure so I used the version from
next-20140826.
The staging tree still had its
Hi all,
Changes since 20140826:
The net tree lost its build failure.
The usb.current tree gained a build failure for which I reverted a commit.
The mfd tree lost its build failure.
The percpu tree gained a build failure so I used the version from
next-20140826.
The staging tree still had its
On Wed, Aug 27, 2014 at 04:10:21PM +1000, Stephen Rothwell wrote:
Hi all,
Changes since 20140826:
The net tree lost its build failure.
The usb.current tree gained a build failure for which I reverted a commit.
The mfd tree lost its build failure.
The percpu tree gained a build
Hi all,
On Wed, 27 Aug 2014 16:58:09 -0700 Guenter Roeck li...@roeck-us.net wrote:
I see a large number of build failures with this kernel.
drivers/base/dma-mapping.c: In function 'dma_common_contiguous_remap':
drivers/base/dma-mapping.c:294:2: error: implicit declaration of function
On 8/27/2014 5:48 PM, Stephen Rothwell wrote:
Hi all,
On Wed, 27 Aug 2014 16:58:09 -0700 Guenter Roeck li...@roeck-us.net wrote:
I see a large number of build failures with this kernel.
drivers/base/dma-mapping.c: In function 'dma_common_contiguous_remap':
drivers/base/dma-mapping.c:294:2:
Hi Laura,
On Wed, 27 Aug 2014 17:56:13 -0700 Laura Abbott lau...@codeaurora.org wrote:
I sent fixes for this to Andrew yesterday, did those not get picked up
or fix the problem?
Things do not migrate to mmotm (and hence linux-next) very quickly
(depending on Andrew's load). I don't remember
On Tue, 27 Aug 2013, Randy Dunlap wrote:
> On 08/27/13 03:30, Stephen Rothwell wrote:
> > Hi all,
> >
> > I should know better than to take time off around -rc7 :-)
> >
> > Changes since 20130822:
> >
>
> on i386:
>
> fs/built-in.o: In function `ceph_fallocate':
> file.c:(.text+0x20b171):
On 08/27/13 03:30, Stephen Rothwell wrote:
> Hi all,
>
> I should know better than to take time off around -rc7 :-)
>
> Changes since 20130822:
>
on i386:
fs/built-in.o: In function `ceph_fallocate':
file.c:(.text+0x20b171): undefined reference to `__divdi3'
--
~Randy
--
To unsubscribe
Hi all,
I should know better than to take time off around -rc7 :-)
Changes since 20130822:
The f2fs tree gained a build failure so I used the version from
next-20130822.
The libata tree gained a build failure so I used the version from
next-20130822.
The pm tree gained a conflict against the
Hi all,
I should know better than to take time off around -rc7 :-)
Changes since 20130822:
The f2fs tree gained a build failure so I used the version from
next-20130822.
The libata tree gained a build failure so I used the version from
next-20130822.
The pm tree gained a conflict against the
On 08/27/13 03:30, Stephen Rothwell wrote:
Hi all,
I should know better than to take time off around -rc7 :-)
Changes since 20130822:
on i386:
fs/built-in.o: In function `ceph_fallocate':
file.c:(.text+0x20b171): undefined reference to `__divdi3'
--
~Randy
--
To unsubscribe from this
On Tue, 27 Aug 2013, Randy Dunlap wrote:
On 08/27/13 03:30, Stephen Rothwell wrote:
Hi all,
I should know better than to take time off around -rc7 :-)
Changes since 20130822:
on i386:
fs/built-in.o: In function `ceph_fallocate':
file.c:(.text+0x20b171): undefined reference
43 matches
Mail list logo
