On Tue, Sep 18, 2018 at 05:19:14PM +0800, Zong Li wrote:
> Only RV64 supports swiotlb.
>
> Signed-off-by: Zong Li
Reviewed-by: Christoph Hellwig
On Tue, Sep 18, 2018 at 05:19:13PM +0800, Zong Li wrote:
> Only RV64 supports 128 integer size.
>
> Signed-off-by: Zong Li
This looks fine. Just curious, what do we even need 128-bit integers
for on riscv64? Did you see any issues if you drop it entirely?
Hello,
syzbot found the following crash on:
HEAD commit:a0cb0cabe4bb Add linux-next specific files for 20180920
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=164d651140
kernel config: https://syzkaller.appspot.com/x/.config?x=786006c5dafbadf6
syz fix: mm: shmem: Correctly annotate new inodes for lockdep
>> > On Thu, 20 Sep 2018 14:04:05 -0700 syzbot
>> > wrote:
>> >
>> > > Hello,
>> > >
>> > > syzbot found the following crash on:
>> > >
>> > > HEAD commi
Hi Pavel,
On Fri, Sep 21, 2018 at 12:04:49AM +0200, Pavel Machek wrote:
> Hi!
>
> > > > +#ifdef CONFIG_ATA_LEDS
> > > > + /* register LED triggers for all ports */
> > > > + for (i = 0; i < host->n_ports; i++) {
> > > > + if (unlikely(!host->ports[i]->ledtrig))
> > > > +
Hi Amelie,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on ljones-mfd/for-mfd-next]
[also build test WARNING on v4.19-rc4 next-20180920]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Hi,
21. September 2018 03:45, "Paul Gortmaker"
schrieb:
> I came across this older netbook over the xmas holidays, and noticed the
> acerhdf driver wouldn't load. Turns out the BIOS string was too new,
> and not listed in the driver. There were module params for overrides,
> but I found their u
Am Freitag, 21. September 2018, 03:42:25 CEST schrieb Joel Stanley:
> On Thu, 20 Sep 2018 at 16:40, Richard Weinberger wrote:
> >
> > Am Donnerstag, 20. September 2018, 04:30:41 CEST schrieb Joel Stanley:
> > > On Mon, 17 Sep 2018 at 07:30, Richard Weinberger wrote:
> > > >
> > > > This reverts c
> >
> > Make sense. I actually booted up kernel on qemu-palmetto (ast2400) but I'm
> > doubting if test is valid because it depends on how qemu emulates the
> > hardware. It would be great if someone can help to verify the patch on
> > physical ast2400.
>
> I gave this a spin on the ast2400. It
From: Zhimin Gu
Convert the hard code into PAGE_SIZE for better scalability.
No functional change.
Cc: "Rafael J. Wysocki"
Signed-off-by: Zhimin Gu
Acked-by: Pavel Machek
Signed-off-by: Chen Yu
---
arch/x86/power/hibernate_asm_32.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
Hi Gautham,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.19-rc4 next-20180919]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/
From: Zhimin Gu
After all the pages are restored to previous address, the page
table switches back to current swapper_pg_dir. However the
swapper_pg_dir currently in used might not be consistent with
previous page table, which might cause issue after resume.
Fix this issue by switching to origin
From: Zhimin Gu
Update the in_suspend variable to reflect the actual hibernation
status. Back-port from 64bit system.
Cc: "Rafael J. Wysocki"
Signed-off-by: Zhimin Gu
Acked-by: Pavel Machek
Signed-off-by: Chen Yu
---
arch/x86/power/hibernate_asm_32.S | 3 +++
1 file changed, 3 insertions(+)
From: Zhimin Gu
This is to reuse the temp_pgt for both 32bit and 64bit
system.
No functional change.
Cc: "Rafael J. Wysocki"
Signed-off-by: Zhimin Gu
Acked-by: Pavel Machek
Signed-off-by: Chen Yu
---
arch/x86/power/hibernate_32.c | 2 ++
arch/x86/power/hibernate_asm_32.S | 3 +--
2 fil
From: Zhimin Gu
Set up the temporary text mapping for the final jump address
so that the system could jump to the right address after all
the pages have been copied back to their original address -
otherwise the final mapping for the jump address is invalid.
Analogous changes were made for 64-bi
From: Zhimin Gu
On 64bit system, code should be executed in a safe page
during page restoring, as the page where instruction is
running during resume might be scribbled and causes issues.
Although on 32 bit, we only suspend resuming by same kernel
that did the suspend, we'd like to remove that r
From: Zhimin Gu
As 32bit system is not using 4-level page, rename it
to temp_pgt so that it can be reused for both 32bit
and 64bit hibernation.
No functional change.
Cc: "Rafael J. Wysocki"
Signed-off-by: Zhimin Gu
Acked-by: Pavel Machek
Signed-off-by: Chen Yu
---
arch/x86/include/asm/susp
From: Zhimin Gu
Enable CONFIG_ARCH_HIBERNATION_HEADER for 32bit system so that
1. arch_hibernation_header_save/restore() are invoked across
hibernation on 32bit system.
2. The checksum handling as well as 'magic' number checking
for 32bit system are enabled.
Controlled by CONFIG_X86_64 in
From: Zhimin Gu
Reduce the hibernation code duplication between x86-32 and x86-64
by extracting the common code into hibernate.c.
Currently only pfn_is_nosave() is the activated common
function in hibernate.c
No functional change.
Acked-by: Pavel Machek
Cc: "Rafael J. Wysocki"
Cc: Thomas Gle
From: Zhimin Gu
swsusp_arch_suspend() is callable non-leaf function which doesn't
honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
Also it's not annotated as ELF callable function which can confuse tooling.
Create a stack frame for it when CONFIG_FRAME_POINTER is enabled and
giv
From: Zhimin Gu
On 32bit systems, nosave_regions(non RAM areas) located between
max_low_pfn and max_pfn are not excluded from hibernation snapshot
currently, which may result in a machine check exception when
trying to access these unsafe regions during hibernation:
[ 612.800453] Disabling lock
Currently if get_e820_md5() fails, then it will hibernate nevertheless.
Actually the error code should be propagated to upper caller so that
the hibernation could be aware of the result and terminates the process
if md5 digest fails.
Suggested-by: Thomas Gleixner
Acked-by: Pavel Machek
Reviewed-
Currently there are mainly three bugs in 32bits system when doing
hibernation:
1. The page copy code is not running in safe page, which might
cause hang during resume.
2. There's no text mapping for the final jump address
of the original kernel, which might cause the system jumping
into il
Hello Jiri,
On 14.09.2018 12:37, Alexey Budankov wrote:
> On 14.09.2018 11:28, Jiri Olsa wrote:
>> On Fri, Sep 14, 2018 at 10:26:53AM +0200, Jiri Olsa wrote:
>>
>> SNIP
>>
> The threaded monitoring currently can't monitor backward maps
> and there are probably more limitations which I have
1)when the nbuckets of cache device is smaller than 1024, make cache device
will trigger BUG_ON in kernel, add a condition to avoid this.
2)split original if condition code into separate ones to make it clearly to
debug.
Signed-off-by: Dongbo Cao
---
drivers/md/bcache/super.c | 87
Hi all,
Changes since 20180920:
Dropped trees: xarray, ida (temporarily)
The vfs tree lost its build failure.
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 5045
5593 files changed, 255228 insertions(+), 112500 dele
Hi Loic/Bjorn,
Can we consider this series for v4.20?
I am interested in for patch "rpmsg: virtio: allocate buffer
from parent". This patch allows me to used VirtIO
RPMSG driver inside Guest/VM.
Regards,
Anup
From: Yue Wang
The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
PCI core. This patch adds documentation for the DT bindings in Meson PCIe
controller.
Signed-off-by: Yue Wang
Signed-off-by: Hanjie Lin
Reviewed-by: Rob Herring
---
.../devicetree/bindings/pci/amlogic,
This is v3 post RESEND: [2]
- add Rob's Reviewed-by to patch 1/2
- add more to&cc list suggested by get_maintainer.pl
The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
PCI core. This patchset add the driver and dt-bindings of the controller.
Till patch v2, we have a de
From: Yue Wang
The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
PCI core. This patch adds the driver support for Meson PCIe controller.
Signed-off-by: Yue Wang
Signed-off-by: Hanjie Lin
---
drivers/pci/controller/dwc/Kconfig | 12 +
drivers/pci/controller/dwc/Ma
Remove fixed clock and source SoC clock for UART6 for
HiSilicon Hi3670 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
b/arch/arm64/boot
Add devicetree bindings for HiSilicon Hi3670 clock controller.
Signed-off-by: Manivannan Sadhasivam
---
.../bindings/clock/hi3670-clock.txt | 43 +++
include/dt-bindings/clock/hi3670-clock.h | 348 ++
2 files changed, 391 insertions(+)
create mode 100644 Document
This patchset adds clock support for Hi3670 SoC from HiSilicon utilizing
the HiSi common clock code. While adding clock support, let's remove the
fixed clock for UART and source SoC clock on HiKey970 board.
This patchset has been verified on HiKey970 board.
Thanks,
Mani
Manivannan Sadhasivam (4)
Add clock driver for HiSilicon Hi3670 SoC utilizing HiSilicon's
common clk code.
Signed-off-by: Manivannan Sadhasivam
---
drivers/clk/hisilicon/Kconfig |7 +
drivers/clk/hisilicon/Makefile |1 +
drivers/clk/hisilicon/clk-hi3670.c | 1016
3 files chan
Add clock nodes for HiSilicon Hi3670 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 43 +++
1 file changed, 43 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
b/arch/arm64/boot/dts/hisilicon/hi3670.dtsi
index c
> +/*
> + * Nag about hardware bugs, hopefully to have vendors fix them, but at least
> + * to collect a list of dependencies for the VF INTx pin quirk below.
> + */
> +static const struct pci_device_id known_bogus_vf_intx_pin[] = {
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x270c) },
> + {}
>
On 9/20/2018 7:19 PM, Matthias Kaehlcke wrote:
If the existing users populate a custom property with the BD address
in the bootloader you could roll out a bootloader change. You'd have
to make sure that bootloader and kernel match. The bootloader could
still populate the custom property to be com
On Thu, Sep 20, 2018 at 10:52 AM Palmer Dabbelt wrote:
>
> On Fri, 14 Sep 2018 07:37:20 PDT (-0700), ren_...@c-sky.com wrote:
> > On Wed, Sep 12, 2018 at 04:30:36PM +0200, Arnd Bergmann wrote:
> >> On Wed, Sep 12, 2018 at 3:25 PM Guo Ren wrote:
> I don't want to hijack this thread, but in RISC-V
On 21/09/2018 04:08, peng.h...@zte.com.cn wrote:
>>> Unqueued, sorry. The hypercall test from kvm-unit-tests fails. A
>>> VMCALL on the "edge" of canonical address space, i.e. at 0x7ffd,
>>> raises a general protection fault before this patch and a double fault
>>> afterwards.
>> Peng Hao
G'day Song,
One more comment below.
On 20/09/2018 9:46 PM, Peter Meerwald-Stadler wrote:
On Thu, 20 Sep 2018, Song Qiang wrote:
PNI RM3100 magnetometer is a high resolution, large signal immunity
magnetometer, composed of 3 single sensors and a processing chip.
PNI is currently not in the vend
On Thu, Sep 20, 2018 at 6:46 PM, zhong jiang wrote:
> debugfs_remove_recursive has taken the null pointer into account.
> just remove the null check before debugfs_remove_recursive.
>
> Acked-by: Masami Hiramatsu
> Signed-off-by: zhong jiang
Acked-by: Kees Cook
-Kees
> ---
> kernel/fail_fun
PERHATIAN;
Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kota
From: Can Guo
Update the compatible string for UFS QMP PHY on SDM845.
Signed-off-by: Can Guo
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/phy/qcom-qm
From: Can Guo
Add core reset support string for UFS.
Signed-off-by: Amit Nischal
Signed-off-by: Can Guo
---
Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt
b/Documentati
From: Can Guo
Add UFS PHY support to make SDM845 UFS work with common PHY framework.
Signed-off-by: Can Guo
Reviewed-by: Evan Green
Reviewed-by: Vivek Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 172 +++-
drivers/phy/qualcomm/phy-qcom-qmp.h | 15
2
From: Can Guo
All PHYs should be powered on before register configuration starts. And
only PCIe PHYs need an extra power control before deasserts reset state.
Signed-off-by: Can Guo
Reviewed-by: Manu Gautam
Reviewed-by: Vivek Gautam
Reviewed-by: Evan Green
---
drivers/phy/qualcomm/phy-qcom-
From: Can Guo
Move MSM8996 specific PHY vreg list struct name to a genernal one as it is
used by all PHYs. Add a specific field to handle dual lane situation.
Signed-off-by: Can Guo
Reviewed-by: Evan Green
Reviewed-by: Manu Gautam
Reviewed-by: Vivek Gautam
---
drivers/phy/qualcomm/phy-qcom-
On Thu, Sep 20, 2018 at 03:34:35PM -0700, Matthias Kaehlcke wrote:
> +EXPORT_SYMBOL(fwnode_get_bd_address);
EXPORT_SYMBOL_GPL()? That matches the majority in this file.
thanks,
greg k-h
On Tue, 2018-09-18 at 21:37 -0700, Manivannan Sadhasivam wrote:
> On Wed, Sep 19, 2018 at 10:54:10AM +0800, Sean Wang wrote:
> > On Tue, 2018-09-18 at 15:07 -0700, Linus Walleij wrote:
> > > On Sat, Sep 8, 2018 at 4:07 AM wrote:
> > >
> > > > v2 and changes since v1:
> > >
> > > I had trouble ap
> On Sep 20, 2018, at 8:45 PM, Andy Lutomirski wrote:
>
>
>
>> On Sep 19, 2018, at 10:05 AM, Sebastian Andrzej Siewior
>> wrote:
>>
>> On 2018-09-12 08:47:19 [-0700], Andy Lutomirski wrote:
--- a/arch/x86/kernel/fpu/core.c
+++ b/arch/x86/kernel/fpu/core.c
@@ -101,14 +101,14
From: Mars Cheng
Add NO_EINT_SUPPORT back to pinctrl-mtk-common-v2.h as the alias of
EINT_NA to indicate that some pin not capable of being controlled as eint
and that is required by pinctrl-paris based driver as old
pinctrl-mtk-common.h already had.
Signed-off-by: Mars Cheng
Signed-off-by: Sea
From: Sean Wang
EINT_NA is an u16 number, so it should be U16_MAX instead of -1
to fix up drivers/pinctrl/mediatek/pinctrl-paris.c:732 mtk_gpio_to_irq()
warn: impossible condition (desc->eint.eint_n == -1) => (0-u16max == (-1))
Also happens in
drivers/pinctrl/mediatek/pinctrl-paris.c:749 mtk_gpi
From: ZH Chen
Add MT6765 pinctrl driver based on MediaTek pinctrl-paris core.
Signed-off-by: Mars Cheng
Signed-off-by: ZH Chen
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/Kconfig |7 +
drivers/pinctrl/mediatek/Makefile |1 +
drivers/pinctrl/mediatek
From: Mars Cheng
Just add eint support to MT6765 pinctrl driver as usual as
happens on the other SoCs.
Signed-off-by: Mars Cheng
Signed-off-by: Sean Wang
---
drivers/pinctrl/mediatek/pinctrl-mt6765.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/pinctrl/mediatek/pinctrl-
> On Sep 19, 2018, at 10:05 AM, Sebastian Andrzej Siewior
> wrote:
>
> On 2018-09-12 08:47:19 [-0700], Andy Lutomirski wrote:
>>> --- a/arch/x86/kernel/fpu/core.c
>>> +++ b/arch/x86/kernel/fpu/core.c
>>> @@ -101,14 +101,14 @@ void __kernel_fpu_begin(void)
>>>
>>> kernel_fpu_disable();
>>>
Hello Rafael,
On Thu, Sep 20, 2018 at 1:06 PM Rafael J. Wysocki wrote:
>
> On Thu, Sep 20, 2018 at 7:43 AM Silesh C V wrote:
> >
> > Similar to bus_find_device_by_name, but finds the device having a
> > specific of_node.
>
> First, what do you need it for? Please describe your use case in the
On Fri, 21 Sep 2018 at 06:39, Tao Ren wrote:
>
> On 9/20/18, 8:46 AM, "Linus Walleij" wrote:
>
> > Actually this is much more intuitive too, it is the typical way to handle
> > a down-counting timer. Good catch!
> > Reviewed-by: Linus Walleij
>
> Thank you Linus for the quick review!
>
> > Sorry
Hi Jacek and Pavel,
On 11 September 2018 at 10:47, Baolin Wang wrote:
> This patch adds one new led trigger that LED device can configure
> the software or hardware pattern and trigger it.
>
> Consumers can write 'pattern' file to enable the software pattern
> which alters the brightness for the
/Keith-Busch/mm-faster-get-user-pages/20180920-184931
config: arm-oxnas_v6_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x
Hi Keith,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc4 next-20180920]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Friday, September 21, 2018 1:48 AM, Rik van Riel wrote:
> On Thu, 2018-09-20 at 03:14 +0100, Edward Cree wrote:
>
> > I think there are important differences between code to be run by
> > CPUs
> > and a Code to be run by humans. And when the author goes on a
> > victory
> > lap on Twitter and
On Thu, Sep 20, 2018 at 4:42 PM Tycho Andersen wrote:
>
> On Wed, Sep 19, 2018 at 12:58:20PM -0700, Andy Lutomirski wrote:
> > On Wed, Sep 19, 2018 at 7:38 AM, Tycho Andersen wrote:
> > > On Wed, Sep 19, 2018 at 07:19:56AM -0700, Andy Lutomirski wrote:
> > >>
> > >>
> > >> > On Sep 19, 2018, at 2
On 20/09/2018 9:13 PM, Song Qiang wrote:
PNI RM3100 magnetometer is a high resolution, large signal immunity
magnetometer, composed of 3 single sensors and a processing chip.
PNI is currently not in the vendors list, so this is also adding it.
In the subject: Isn't the RM3100 a 3axis mag.
The
On 09/12/18 at 08:31am, Ingo Molnar wrote:
> Would you like to work on this? These would be really nice additions, once
> the code is cleaned
> up to be maintainable and the pending bug fixes you have are merged.
>
> In terms of patch logistics I'd suggest this ordering:
>
> - documentation fi
--
Greetings,
I wish to seek your assistance for the transfer of US$35M depository
made by a politician for an investment programme that has
remained dormant for years now.I shall provide you with more details
and relevant documents that will help you understand the transaction.
Mr. Hama Dial
On Thu, Sep 20, 2018 at 6:39 PM, John Johansen
wrote:
> On 09/20/2018 06:10 PM, Casey Schaufler wrote:
>> On 9/20/2018 5:45 PM, Kees Cook wrote:
>>> On Thu, Sep 20, 2018 at 5:25 PM, Casey Schaufler
>>> wrote:
On 9/20/2018 9:23 AM, Kees Cook wrote:
> config LSM_ORDER
> string
On 9/20/18 5:36 PM, Linus Walleij wrote:
What I mean is that $SUBJECT patch might not hurt Qualcomms
GPIOs (not crash the platform) if and only if it is augmented to not
try to get the initial direction from lines masked off in .valid_mask
if .need_valid_mask is true.
Whether it makes sense sema
fixes following Smatch static check warning:
./drivers/pinctrl/sunxi/pinctrl-sunxi.c:1112 sunxi_pinctrl_build_state()
warn: passing devm_ allocated variable to kfree. 'pctrl->functions'
As we will be calling krealloc() on pointer 'pctrl->functions', which means
kfree() will be called in there,
The patch
regulator: da905{2,5}: Remove unnecessary array check
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 h
The patch
spi: pic32: Use proper enum in dmaengine_prep_slave_rg
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and s
debugfs_remove_recursive has taken the null pointer into account.
just remove the null check before debugfs_remove_recursive.
Acked-by: Masami Hiramatsu
Signed-off-by: zhong jiang
---
kernel/fail_function.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/fail_functi
This patch seems reasonable, but you emailed the wrong people :)
On Thu, Sep 20, 2018 at 5:15 PM Jason A. Donenfeld wrote:
>
> It turns out that KASAN in general will bloat stack frames in unexpected
> ways, not just KASAN_EXTRA. So, this patch trivially changes that
> default to be associated wi
Hi Guys,
Could you have a chance to review this patchset?
Thanks!
On Mon, Sep 17, 2018 at 09:44:49AM +0900, Minchan Kim wrote:
> To use bit 5 in page table as L_PTE_SPECIAL, we need a room for that.
> It seems we don't need 4 bits for the memory type with ARMv6+.
> If it's true, let's reorder bi
This driver has two module parameters that allow an override of the
checks for matching model and BIOS version. However, both parameters
expect you to choose an entry from the existing list of supported
systems, encoded within the driver itself.
Without the source, such as in a binary distributio
I came across this older netbook over the xmas holidays, and noticed the
acerhdf driver wouldn't load. Turns out the BIOS string was too new,
and not listed in the driver. There were module params for overrides,
but I found their use isn't quite clear without reading the source.
Here I clarify s
On Thu, 2018-09-20 at 03:14 +0100, Edward Cree wrote:
> I think there are important differences between code to be run by
> CPUs
> and a Code to be run by humans. And when the author goes on a
> victory
> lap on Twitter and declares the Code to be "a political document",
> is
> it any surprise
Just like we avoid specifying actual block devices like sda for fdisk
and dd examples, we should not specify specific thermal zones here.
On the platform I was testing on, zone0 was acpitz, and zone1 was for
this acerhdf driver. Make the printk such that it won't work with a
blind cut-and-paste,
unsubscribe linux-kernel
--
Best regards
Kassey
To fix:
acerhdf: unknown (unsupported) BIOS version Gateway /LT31 /v1.3307 ,
please report, aborting!
As can be seen in the context, the BIOS registers haven't changed in
the previous versions, so the assumption is they won't have changed
in this last update for this somewhat older platform
Hi Jiri
Can you pick up the patch?
Thanks
zhong jiang
On 2018/9/13 15:41, zhong jiang wrote:
> Fix the following compile warning:
>
> drivers/hid/hid-logitech-hidpp.c: In function 'hi_res_scroll_enable':
> drivers/hid/hid-logitech-hidpp.c:2714:54: warning: 'multiplier' may be used
> uninitializ
Normally, a module parameter for a BIOS check override implies "pretend
you support this version" (and the user will enter their local version).
However, this driver uses the model/BIOS module parameters in a way that
is "pretend my system is the supported model XYZ with BIOS version ABC."
which i
Hi Tejun
Thanks for your kindly response.
On 09/21/2018 04:53 AM, Tejun Heo wrote:
> Hello,
>
> On Thu, Sep 20, 2018 at 06:18:21PM +0800, Jianchao Wang wrote:
>> -static inline void percpu_ref_get_many(struct percpu_ref *ref, unsigned
>> long nr)
>> +static inline void __percpu_ref_get_many(str
There is a table of Vendor/Model/Version {control data} in this driver,
but outside of the initial probe, the V/M/V is never used again, and
neither are any of the entries for platforms other than the one which
matches the running target.
By simply storing the {control data} for the matched platfo
These three functions are only called from the probe code which is
already marked __init and hence these can be __init as well.
Cc: Peter Feuerer
Cc: Darren Hart
Cc: Andy Shevchenko
Signed-off-by: Paul Gortmaker
---
drivers/platform/x86/acerhdf.c | 6 +++---
1 file changed, 3 insertions(+), 3
On Thu, Sep 20, 2018 at 08:13:52PM +0100, Craig wrote:
> On 20 September 2018 17:58:47 BST, Sebastian Reichel
> wrote:
> >[Dropped a couple of people from CC, added Baolin]
> >
> >Hi Craig, Baolin and Rob,
> >
> >On Thu, Sep 20, 2018 at 03:32:29PM +0100, Craig wrote:
> >> On 16 September 2018 13:
Hi,
On Fri, Sep 21, 2018 at 04:08:28AM +0800, Baolin Wang wrote:
> Hi Sebastian,
>
> On 21 September 2018 at 00:58, Sebastian Reichel
> wrote:
> > [Dropped a couple of people from CC, added Baolin]
> >
> > Hi Craig, Baolin and Rob,
> >
> > On Thu, Sep 20, 2018 at 03:32:29PM +0100, Craig wrote:
>
On Thu, 20 Sep 2018 at 16:40, Richard Weinberger wrote:
>
> Am Donnerstag, 20. September 2018, 04:30:41 CEST schrieb Joel Stanley:
> > On Mon, 17 Sep 2018 at 07:30, Richard Weinberger wrote:
> > >
> > > This reverts commit 11a6fc3dc743e22fb50f2196ec55bee5140d3c52.
> > > UBIFS wants to assert that
On Wed, Sep 19, 2018 at 09:22:39PM +0200, Tomasz Duszynski wrote:
> Comments inline.
>
> On Sat, Sep 15, 2018 at 01:42:14PM -0400, ryang wrote:
> > Add device tree support for ROHM BH1750 series ambient light sensors.
> >
> > Signed-off-by: ryang
> > ---
> > drivers/iio/light/bh1750.c | 10 +
On 2018/9/20 22:43, Stephen Hemminger wrote:
> On Thu, 20 Sep 2018 20:33:01 +0800
> YueHaibing wrote:
>
>> The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
>> which is a typedef for an enum type, so make sure the implementation in
>> this driver has returns 'netdev_tx_t' valu
From: Uwe Kleine-König Sent: 2018年9月20日 20:11
> Back in 2015 when irda was dropped from the driver imx1 was broken.
> This change reintroduces the support for the third interrupt of the UART.
>
> Fixes: afe9cbb1a6ad ("serial: imx: drop support for IRDA")
> Signed-off-by: Uwe Kleine-König
> ---
>
Changes Makefile so 'make drivers/dio/' won't compile this driver
unless CONFIG_DIO is enabled.
Previously, it would compile independently of .config file.
Signed-off-by: Leonardo Brás
---
drivers/dio/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dio/Makefi
From: Masayoshi Mizuma
Physical package id 0 is not always exists. We should use
boot_cpu_data.logical_proc_id directly as the pkg id here.
Signed-off-by: Masayoshi Mizuma
---
arch/x86/events/intel/uncore_snbep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/even
On 9/19/18 6:08 AM, Oscar Salvador wrote:
> From: Oscar Salvador
>
> This patch, as the previous one, gets rid of the wrong if statements.
> While at it, I realized that the comments are sometimes very confusing,
> to say the least, and wrong.
> For example:
>
> ---
> zone_last = ZONE_MOVABLE;
>
Clang generates a warning when it sees a logical not followed by a
conditional operator like ==, >, or < because it thinks that the logical
not should be applied to the whole statement:
drivers/staging/rtl8188eu/core/rtw_ieee80211.c:293:8: warning: logical
not is only applied to the left hand side
On Wed, Sep 19, 2018 at 11:24 PM Veerabhadrarao Badiganti
wrote:
>
> From: Vijay Viswanath
>
> The load a particular sdhc controller should request from a regulator
> is device specific and hence each device should individually vote for
> the required load.
>
> Signed-off-by: Vijay Viswanath
> S
On 9/19/18 6:08 AM, Oscar Salvador wrote:
> From: Oscar Salvador
>
> While looking at node_states_check_changes_online, I stumbled
> upon some confusing things.
>
> Right after entering the function, we find this:
>
> if (N_MEMORY == N_NORMAL_MEMORY)
> zone_last = ZONE_MOVABLE;
>
> T
On 9/20/2018 3:59 PM, Dan Williams wrote:
On Thu, Sep 20, 2018 at 3:31 PM Alexander Duyck
wrote:
This patch is meant to force the device registration for nvdimm devices to
be closer to the actual device. This is achieved by using either the NUMA
node ID of the region, or of the parent. By doin
It turns out that KASAN in general will bloat stack frames in unexpected
ways, not just KASAN_EXTRA. So, this patch trivially changes that
default to be associated with KASAN instead of KASAN_EXTRA.
Signed-off-by: Jason A. Donenfeld
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1
On Thu, Sep 20, 2018 at 05:10:18PM -0400, Liang, Kan wrote:
>
>
> On 9/20/2018 4:55 PM, Thomas Gleixner wrote:
> > On Mon, 10 Sep 2018, Masayoshi Mizuma wrote:
> >
> > CC+ Kan
> >
> > > From: Masayoshi Mizuma
> > >
> > > Physical package id 0 is not always exists. We should use
> > > boot_cpu
Clang warns that the address of a pointer will always evaluated as true
in a boolean context:
drivers/regulator/da9052-regulator.c:423:22: warning: address of array
'pdata->regulators' will always evaluate to 'true'
[-Wpointer-bool-conversion]
if (pdata && pdata->regulators) {
1 - 100 of 673 matches
Mail list logo
