[RFC PATCH] mconf: expand show_all_options to choices' checklist menus

Boolean choices' checklist menus are currently immune against the 'z' key that toggles visibility of all options. Expansion of the 'z' toggle could be of use when debugging problems with comlex choice menus. A new tag 'z' for dialog_items was introduced for

[RFC v2 0/1] Emacs-like isearch for mconf.

*** BLURB HERE *** Hello, this is v2 of the isearch implementation, I also added Documentation changes which probably have to be split, because the older symbol-search also was undokumented in mconf (I basically copied the relevant documentation from Documentation/kbuild/kconfig.txt. I could

Re: [RFC 0/1] mconf: Emacs-like isearch

Sam Ravnborg writes: >> >> I'd say it's not important to start isearch with CTRL-s, I am just so >> used to it. So, I am open for suggestions. > > Today we have first or one of the first letters as shortcut to menus. > How about considering everything typed as search inputs. > Search is then st

[RFC v3 0/1] Emacs-like isearch for mconf.

blems with mismatches and matches above the current position were fixed. Dirk Gouders (1): Emacs-like isearch for mconf. Documentation/kbuild/kconfig.txt | 18 +++- scripts/kconfig/lxdialog/dialog.h | 6 ++ scripts/kconfig/lxdialog/menubox.c | 171

[RFC v3 1/1] Emacs-like isearch for mconf.

# navigate to Device Drivers 3) ENTER# terminate isearch and enter submenu 4) \# start isearch 5) USB # navigate to USB support 6) ENTER# terminate isearch and enter submenu Signed-off-by: Dirk Gouders --- Documentation/kbuild

[RFC v4 0/1] i-search functionality for mconf

earch mode, for a detailed description see 1/1. As stated earlier, this is just a prototype, documentation is missing and the code is not ready for a real commit. Dirk Dirk Gouders (1): Isearch functionality for mconf scripts/kconfig/lxdialog/dialog.h | 3 + scripts/kconfig/lxdialog/menu

[RFC v4 1/1] i-search functionality for mconf

This patch prototypes isearch functionality for mconf based on an idea of Sam Ravnborg: * mconf now distinguishes if the focus is on the menu items or the buttons below it. * At startup focus is on the menu items and alphanumeric characters or space entered are used to form a string that is

Re: [RFC v4 0/1] i-search functionality for mconf

Sam Ravnborg writes: > Hi Dirk. > > On Fri, Jun 08, 2018 at 08:46:05PM +0200, Dirk Gouders wrote: >> Hello, >> >> this version is a prototype of the idea, Sam suggested -- I hope I >> undestood it correctly. >> >> This is a remarkable ch

[RFC v5 1/1] i-search navigation for mconf

# Enter the submenu Suggested-by: Sam Ravnborg Signed-off-by: Dirk Gouders --- scripts/kconfig/lxdialog/dialog.h | 3 + scripts/kconfig/lxdialog/menubox.c | 489 +++-- scripts/kconfig/lxdialog/util.c| 106 +++- scripts/kconfig/mconf.c

[RFC v5 0/1] i-search navigation for mconf

with mismatches and matches above the current position were fixed. Dirk Gouders (1): i-search navigation for mconf scripts/kconfig/lxdialog/dialog.h | 3 + scripts/kconfig/lxdialog/menubox.c | 489 +++-- scripts/kconfig/lxdialog/util.c| 106 +++- sc

BUG: amdgpu: NULL pointer dereference introduced in 5.9-rc1

Commit c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) introduced a NULL pointer dereference when booting with amdgpu.discovery=0. For amdgpu.discovery=0 that commit effectively removed the call of vega10_reg_base_init(adev), so I tested the correctness of the bisect session by rest

[PATCH 0/1] drm/amdgpu: fix NULL pointer dereference for Renoir

Alex Deucher writes: > On Wed, Sep 30, 2020 at 4:46 PM Dirk Gouders wrote: >> >> Commit c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) >> introduced a NULL pointer dereference when booting with >> amdgpu.discovery=0. >> >> For amdgpu.disc

[PATCH 1/1] drm/amdgpu: fix NULL pointer dereference for Renoir

that amdgpu_discovery_reg_base_init() failed. Fixes: c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) Signed-off-by: Dirk Gouders Cc: Hawking Zhang Cc: Evan Quan --- drivers/gpu/drm/amd/amdgpu/soc15.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a

Re: [PATCH 1/1] drm/amdgpu: fix NULL pointer dereference for Renoir

Dirk Gouders writes: > Commit c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) > introduced a NULL pointer dereference when booting with > amdgpu.discovery=0, because it removed the call of vega10_reg_base_init() > for that case. > > Fix this by calli

[PATCH] ./Makefile: consider PAGER for `make help'

`make help' outputs more than a screenfull of lines. In case a user has PAGER defined in his environment, she most likely wants it to be used in such situations. Signed-off-by: Dirk Gouders --- Makefile | 7 +++ 1 file changed, 7 insertions(+) diff --git a/Makefile b/Makefile

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Alex Deucher writes: > On Wed, Sep 23, 2020 at 3:45 PM Dirk Gouders wrote: >> >> Dirk Gouders writes: >> >> > Alex Deucher writes: >> > >> >> On Wed, Sep 23, 2020 at 8:54 AM Dirk Gouders wrote: >> >>> >> >>> D

WARN_ONCE triggered: tpm_tis: Add a check for invalid status

On my laptop the check introduced with 55707d531af62b (tpm_tis: Add a check for invalid status) triggered the warning (output below). So, my laptop seems to be a candidate for testing. Dirk [7.255467] [ cut here ] [7.255468] TPM returned invalid status [7.2554

Re: WARN_ONCE triggered: tpm_tis: Add a check for invalid status

James Bottomley writes: > On Wed, 2020-10-14 at 19:57 +0200, Dirk Gouders wrote: >> On my laptop the check introduced with 55707d531af62b (tpm_tis: Add a >> check for invalid status) triggered the warning (output below). >> >> So, my laptop seems to be a candidate

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Alex Deucher writes: > On Wed, Sep 23, 2020 at 8:54 AM Dirk Gouders wrote: >> >> Dirk Gouders writes: >> >> > Hi, >> > >> > I noticed a call trace (attached) when starting my machine (ThinkPad >> > L14). This machine is new and I

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Dirk Gouders writes: > Alex Deucher writes: > >> On Wed, Sep 23, 2020 at 8:54 AM Dirk Gouders wrote: >>> >>> Dirk Gouders writes: >>> >>> > Hi, >>> > >>> > I noticed a call trace (attached) when starting my machin

amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Hi, I noticed a call trace (attached) when starting my machine (ThinkPad L14). This machine is new and I am still working on it's configuration but visually noticeable is that scrolling in xterms with SHIFT-PgUp/PgDn is broken. Using the mouse wheel works. It seems the call trace has been intro

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Dirk Gouders writes: > Hi, > > I noticed a call trace (attached) when starting my machine (ThinkPad > L14). This machine is new and I am still working on it's > configuration but visually noticeable is that scrolling in xterms with > SHIFT-PgUp/PgDn is broken. Usin

<    1   2