diff options
| author |   Buland Singh <bsingh@redhat.com> | 2018-12-20 17:35:24 +0530 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-01-22 13:34:35 +0100 |
| commit | 24d48a61f2666630da130cc2ec2e526eacf229e3 (patch) | |
| tree | 7f06805a46c4e74d56f3f73089c4ccbede67dfb8 /scripts | |
| parent | slimbus: core: add missing spin_lock_init on txn_lock (diff) | |
| download | linux-dev-24d48a61f2666630da130cc2ec2e526eacf229e3.tar.xz linux-dev-24d48a61f2666630da130cc2ec2e526eacf229e3.zip | |
hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable
Commit '3d035f580699 ("drivers/char/hpet.c: allow user controlled mmap for
user processes")' introduced a new kernel command line parameter hpet_mmap,
that is required to expose the memory map of the HPET registers to
user-space. Unfortunately the kernel command line parameter 'hpet_mmap' is
broken and never takes effect due to missing '=' character in the __setup()
code of hpet_mmap_enable.
Before this patch:
dmesg output with the kernel command line parameter hpet_mmap=1
[ 0.204152] HPET mmap disabled
dmesg output with the kernel command line parameter hpet_mmap=0
[ 0.204192] HPET mmap disabled
After this patch:
dmesg output with the kernel command line parameter hpet_mmap=1
[ 0.203945] HPET mmap enabled
dmesg output with the kernel command line parameter hpet_mmap=0
[ 0.204652] HPET mmap disabled
Fixes: 3d035f580699 ("drivers/char/hpet.c: allow user controlled mmap for user processes")
Signed-off-by: Buland Singh <bsingh@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions