Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-16 Thread Miroslav Benes
On Wed, 15 Jul 2020, Josh Poimboeuf wrote: > On Wed, Jul 15, 2020 at 03:41:55PM +0200, Petr Mladek wrote: > > On Wed 2020-07-15 14:10:54, Petr Mladek wrote: > > > On Wed 2020-07-15 13:11:14, Miroslav Benes wrote: > > > > Petr, would you agree to revert -flive-patching. > > > > > > Yes, I agree. >

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-15 Thread Josh Poimboeuf
On Wed, Jul 15, 2020 at 03:41:55PM +0200, Petr Mladek wrote: > On Wed 2020-07-15 14:10:54, Petr Mladek wrote: > > On Wed 2020-07-15 13:11:14, Miroslav Benes wrote: > > > Petr, would you agree to revert -flive-patching. > > > > Yes, I agree. > > Or better to say that I will not block it. > > I se

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-15 Thread Petr Mladek
On Wed 2020-07-15 14:10:54, Petr Mladek wrote: > On Wed 2020-07-15 13:11:14, Miroslav Benes wrote: > > Petr, would you agree to revert -flive-patching. > > Yes, I agree. Or better to say that I will not block it. I see that it causes maintenance burden. There are questions about reliability and

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-15 Thread Petr Mladek
On Wed 2020-07-15 13:11:14, Miroslav Benes wrote: > Petr, would you agree to revert -flive-patching. Yes, I agree. Best Regards, Petr

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-15 Thread Miroslav Benes
On Tue, 14 Jul 2020, Josh Poimboeuf wrote: > On Tue, Jul 14, 2020 at 12:56:21PM +0200, Miroslav Benes wrote: > > On Thu, 2 Jul 2020, Josh Poimboeuf wrote: > > > > > On Tue, Jun 23, 2020 at 08:06:07AM -0700, Randy Dunlap wrote: > > > > On 6/22/20 11:28 PM, Stephen Rothwell wrote: > > > > > Hi all,

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-14 Thread Josh Poimboeuf
On Tue, Jul 14, 2020 at 12:56:21PM +0200, Miroslav Benes wrote: > On Thu, 2 Jul 2020, Josh Poimboeuf wrote: > > > On Tue, Jun 23, 2020 at 08:06:07AM -0700, Randy Dunlap wrote: > > > On 6/22/20 11:28 PM, Stephen Rothwell wrote: > > > > Hi all, > > > > > > > > Changes since 20200622: > > > > > > >

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-14 Thread Miroslav Benes
On Thu, 2 Jul 2020, Josh Poimboeuf wrote: > On Tue, Jun 23, 2020 at 08:06:07AM -0700, Randy Dunlap wrote: > > On 6/22/20 11:28 PM, Stephen Rothwell wrote: > > > Hi all, > > > > > > Changes since 20200622: > > > > > > > on x86_64: > > > > arch/x86/kernel/cpu/mce/core.o: warning: objtool: mce_ti

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-07-02 Thread Josh Poimboeuf
On Tue, Jun 23, 2020 at 08:06:07AM -0700, Randy Dunlap wrote: > On 6/22/20 11:28 PM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20200622: > > > > on x86_64: > > arch/x86/kernel/cpu/mce/core.o: warning: objtool: mce_timed_out()+0x24: > unreachable instruction > kernel/exit.o: war

Re: linux-next: Tree for Jun 23 (objtool (2))

2020-06-23 Thread Randy Dunlap
On 6/22/20 11:28 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20200622: > on x86_64: arch/x86/kernel/cpu/mce/core.o: warning: objtool: mce_timed_out()+0x24: unreachable instruction kernel/exit.o: warning: objtool: __x64_sys_exit_group()+0x14: unreachable instruction Full randconfi

linux-next: Tree for Jun 23

2020-06-22 Thread Stephen Rothwell
Hi all, Changes since 20200622: My fixes tree contains: 466d58f824f1 ("device_cgroup: Fix RCU list debugging warning") 9bd7b7c45d71 ("sched: Fix RANDSTRUCT build fail") The printk tree still had its build failure so I used the version from next-20200618. The hid tree still had its build fa

linux-next: Tree for Jun 23

2017-06-23 Thread Stephen Rothwell
Hi all, Changes since 20170622: Removed tree: dma-mapping Renamed tree: dma-mapping-hch to dma-mapping The net-next tree gained a conflict against the net tree. The sound-asoc tree gained a conflict against the pm tree. The block tree gained a conflict against Linus' tree. The devicetree tree

linux-next: Tree for Jun 23

2016-06-23 Thread Stephen Rothwell
Hi all, Changes since 20160622: The pci tree gained a conflict against Linus' tree. The sunxi tree gained a conflict against the drm-misc tree. The audit tree gained a conflict against the security tree. Non-merge commits (relative to Linus' tree): 5152 4945 files changed, 228135 insertions(+

Re: linux-next: Tree for Jun 23

2015-06-23 Thread Eric W. Biederman
Greg Kroah-Hartman writes: > On Tue, Jun 23, 2015 at 05:53:58AM -0500, Eric W. Biederman wrote: >> >> Stephen could you please drop the kdbus tree? > > What? No, that's not how this works. That's not how any of this > works. That is exactly how this works. Unless there was a change in policy

Re: linux-next: Tree for Jun 23

2015-06-23 Thread Greg Kroah-Hartman
On Tue, Jun 23, 2015 at 05:53:58AM -0500, Eric W. Biederman wrote: > > Stephen could you please drop the kdbus tree? What? No, that's not how this works. That's not how any of this works. > There was some significant work that was identified last merge window > that has not yet been done, and

Re: linux-next: Tree for Jun 23

2015-06-23 Thread Eric W. Biederman
Stephen could you please drop the kdbus tree? There was some significant work that was identified last merge window that has not yet been done, and who knows when it will be done. Certainly the recent sd-bus API announcement strongly suggests that there are no plans to perform such work. Having

linux-next: Tree for Jun 23

2015-06-23 Thread Stephen Rothwell
Hi all, Changes since 20150622: The drm-exynos tree gained a build failure so I used the version from next-20150622. Non-merge commits (relative to Linus' tree): 11719 9842 files changed, 1023630 insertions(+), 237137 deletions(-) ---

linux-next: Tree for Jun 23

2014-06-22 Thread Stephen Rothwell
Hi all, The powerpc allyesconfig is again broken more than usual. Changes since 20140620: The mvebu tree gained a conflict against Linus' tree. The crypto tree gained a build failure so I used the version from next-20140620. The staging tree still had its build failure for which I disabled a d