On Mon, Dec 17, 2018 at 6:45 AM Paul Gortmaker
wrote:
>
> [Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.]
> On 29/12/2017 (Fri 13:18) Paul Gortmaker wrote:
>
> > [Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.]
> >
[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On
29/12/2017 (Fri 13:18) Paul Gortmaker wrote:
> [Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.]
> On 29/12/2017 (Fri 10:47) Josh Poimboeuf wrote:
>
> > This seem
On Fri, Dec 29, 2017 at 01:18:30PM -0500, Paul Gortmaker wrote:
> [Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.]
> On 29/12/2017 (Fri 10:47) Josh Poimboeuf wrote:
>
> > This seems to be related to a kconfig quirk where only silentoldconfig
> >
On Fri, Dec 29, 2017 at 01:18:30PM -0500, Paul Gortmaker wrote:
> [Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.]
> On 29/12/2017 (Fri 10:47) Josh Poimboeuf wrote:
>
> > This seems to be related to a kconfig quirk where only silentoldconfig
> >
[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On
29/12/2017 (Fri 10:47) Josh Poimboeuf wrote:
> This seems to be related to a kconfig quirk where only silentoldconfig
> updates the include/config/auto.conf file. The other config targets
> (oldconfig, defco
[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On
29/12/2017 (Fri 10:47) Josh Poimboeuf wrote:
> This seems to be related to a kconfig quirk where only silentoldconfig
> updates the include/config/auto.conf file. The other config targets
> (oldconfig, defco
On Thu, Dec 28, 2017 at 09:13:24PM -0500, Paul Gortmaker wrote:
> > > There is a regression new to 4.15 that happens in a rather common
> > > workflow which results in the frustrating situation where the user has
> > > clearly disabled UNWINDER_ORC in their ".config" file, and yet they
> > > still
On Thu, Dec 28, 2017 at 09:13:24PM -0500, Paul Gortmaker wrote:
> > > There is a regression new to 4.15 that happens in a rather common
> > > workflow which results in the frustrating situation where the user has
> > > clearly disabled UNWINDER_ORC in their ".config" file, and yet they
> > > still
[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On
28/12/2017 (Thu 11:29) Randy Dunlap wrote:
> On 12/25/2017 08:30 PM, Paul Gortmaker wrote:
> > There is a regression new to 4.15 that happens in a rather common
> > workflow which results in the frustr
[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On
28/12/2017 (Thu 11:29) Randy Dunlap wrote:
> On 12/25/2017 08:30 PM, Paul Gortmaker wrote:
> > There is a regression new to 4.15 that happens in a rather common
> > workflow which results in the frustr
On 12/25/2017 08:30 PM, Paul Gortmaker wrote:
> There is a regression new to 4.15 that happens in a rather common
> workflow which results in the frustrating situation where the user has
> clearly disabled UNWINDER_ORC in their ".config" file, and yet they
> still get the immediate false error
On 12/25/2017 08:30 PM, Paul Gortmaker wrote:
> There is a regression new to 4.15 that happens in a rather common
> workflow which results in the frustrating situation where the user has
> clearly disabled UNWINDER_ORC in their ".config" file, and yet they
> still get the immediate false error
There is a regression new to 4.15 that happens in a rather common
workflow which results in the frustrating situation where the user has
clearly disabled UNWINDER_ORC in their ".config" file, and yet they
still get the immediate false error saying they need libelf-dev since
"CONFIG_UNWINDER_ORC=y"
There is a regression new to 4.15 that happens in a rather common
workflow which results in the frustrating situation where the user has
clearly disabled UNWINDER_ORC in their ".config" file, and yet they
still get the immediate false error saying they need libelf-dev since
"CONFIG_UNWINDER_ORC=y"
14 matches
Mail list logo
