With dell_micmute_led_set() moved to drivers/platform/x86/dell-laptop.c,
all remnants of the mic mute LED handling code can be removed from
drivers/leds/dell-led.c, restoring it back to the state it was in before
commit db6d8cc00773 ("dell-led: add mic mute led interface").
Signed-off-by: Michał K
As dell_micmute_led_set() no longer uses the dell_wmi_perform_query()
method, which was removed in commit 0c41a08e131d ("dell-led: use
dell_smbios_send_request() for performing SMBIOS calls"), the
DELL_APP_GUID check is redundant and thus can be safely removed.
Signed-off-by: Michał Kępień
Tested
Fix coding style issues in dell-wmi-led to make sure the module gets a
clean start in the x86 platform driver subsystem.
Signed-off-by: Michał Kępień
---
drivers/platform/x86/dell-wmi-led.c | 66 +++--
1 file changed, 26 insertions(+), 40 deletions(-)
diff --git
The dell-led driver handles a specific WMI GUID present on some Dell
laptops and as such it belongs in the x86 platform driver subsystem.
Source code is moved along with the relevant Kconfig and Makefile
entries, with some minor modifications:
- Kconfig option is renamed from CONFIG_LEDS_DELL_NE
On (Thu) 16 Feb 2017 [23:11:26], Joe Perches wrote:
> To enable eventual removal of pr_warning
>
> This makes pr_warn use consistent for drivers/char
>
> Prior to this patch, there were 1 use of pr_warning and
> 40 uses of pr_warn in drivers/char
>
> Signed-off-by: Joe Perches
Reviewed-by: Ami
The scheduler clock framework may not use the correct timeout for the clock
wrap. This happens when a new clock driver calls sched_clock_register()
after the kernel called sched_clock_postinit(). In this case the clock wrap
timeout is too long thus sched_clock_poll() is called too late and the cloc
On 17 February 2017 at 06:38, Viresh Kumar wrote:
> On 09-02-17, 09:11, Viresh Kumar wrote:
>> The first 5 patches update the PM domain and QoS frameworks to support
>> that and the last one presents the front end interface to it.
>
> @Kevin and Ulf,
>
> Is there something wrong with this series?
On Thu, 16 Feb 2017 23:11:22 -0800
Joe Perches wrote:
> To enable eventual removal of pr_warning
>
> This makes pr_warn use consistent for arch/x86
>
> Prior to this patch, there were 46 uses of pr_warning and
> 122 uses of pr_warn in arch/x86
>
> Miscellanea:
>
> o Coalesce a few formats and
On Fri, Feb 17, 2017 at 9:11 AM, Joe Perches wrote:
> To enable eventual removal of pr_warning
>
> This makes pr_warn use consistent for drivers/platform
>
> Prior to this patch, there were 7 uses of pr_warning and
> 108 uses of pr_warn in drivers/platform
Acked-by: Andy Shevchenko
>
> Signed-o
On Fri, Feb 17, 2017 at 5:33 AM, Darren Hart wrote:
> On Tue, Feb 14, 2017 at 07:46:12PM +0530, Ritesh Raj Sarraf wrote:
>> Lenovo Yoga (many variants: Yoga, Yoga2 Pro, Yoga2 13, Yoga3 Pro, Yoga 3
>> 14 etc) has multiple modles that are a hybrid laptop, working in laptop
>> mode as well as tablet
Hi Linus,
Here's one mmc fix intended for v4.10 rc9 (or final if no new rc).
Based on v4.10-rc8.
Details are as usual found in the signed tag. Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc:
Linux 4.10-rc8 (2017-02-1
Reduce special casing of xen_cpuid() and disable DCA feature for pv
domains as it isn't supported under Xen.
Juergen Gross (2):
x86/xen: don't indicate DCA support in pv domains
x86/xen: use capabilities instead of fake cpuid values
arch/x86/xen/enlighten.c | 14 ++
1 file change
Xen doesn't support DCA (direct cache access) for pv domains. Clear
the corresponding capability indicator.
Signed-off-by: Juergen Gross
---
arch/x86/xen/enlighten.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 51ef952..83399ce
When running as pv domain xen_cpuid() is being used instead of
native_cpuid(). In xen_cpuid() the aperf/mperf feature is indicated
as not being present by special casing the related cpuid leaf.
Instead of delivering fake cpuid values clear the cpu capability bit
for aperf/mperf instead.
Signed-of
On 四, 2月 16, 2017 at 02:31:38下午 +0100, Arnd Bergmann wrote:
> On Tuesday, February 14, 2017 5:19:11 PM CET Chunyan Zhang wrote:
> > static const struct of_device_id serial_ids[] = {
> > - {.compatible = "sprd,sc9836-uart",},
> > + {.compatible = "sprd,sc-uart",},
> > {}
>
> W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
WIth the 4.10-rc8 kernel, I keep getting the following (non-fatal) error on
every boot.
With previous kernels, the mcelog daemon used to register errors occasionally.
But the errors messages weren't recurrent on every boot.
Filing it here, i
Hi, Hugh,
Hugh Dickins writes:
> On Thu, 16 Feb 2017, Tim Chen wrote:
>>
>> > I do not understand your zest for putting wrappers around every little
>> > thing, making it all harder to follow than it need be. Here's the patch
>> > I've been running with (but you have a leak somewhere, and I do
Hi Sudeep,
On 二, 2月 14, 2017 at 04:44:53下午 +, Sudeep Holla wrote:
> On Tue, Feb 14, 2017 at 9:19 AM, Chunyan Zhang
> wrote:
> > From: Orson Zhai
> >
> > SC9860G is a 8 cores of A53 SoC with 4G LTE support SoC from Spreadtrum.
> >
> > According to regular hierarchy of sprd dts, whale2.dtsi c
Am 17. Februar 2017 06:09:42 MEZ schrieb Christophe Ricard
:
>Are you sure it is not better to introduce this delay directly in the
>rpi spi driver ?
>
>Other than that i don't see any issue with it.
Yes - it would be perfect to fix the issue in the upstream rpi spi master
driver.
However thi
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/blackfin
Prior to this patch, there were 11 uses of pr_warning and
0 uses of pr_warn in arch/blackfin
Signed-off-by: Joe Perches
---
arch/blackfin/kernel/nmi.c | 2 +-
arch/blackfin/kernel/ptra
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/alpha
Prior to this patch, there were 2 uses of pr_warning and
0 uses of pr_warn in arch/alpha
Signed-off-by: Joe Perches
---
arch/alpha/kernel/perf_event.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletion
There are ~4300 uses of pr_warn and ~250 uses of the older
pr_warning in the kernel source tree.
Make the use of pr_warn consistent across all kernel files.
This excludes all files in tools/ as there is a separate
define pr_warning for that directory tree and pr_warn is
not used in tools/.
Done
Am 17. Februar 2017 06:11:53 MEZ schrieb Christophe Ricard
:
>I am not sure i understand here, are you considering there could be
>burstcount > 64 with "TCG" TPM ?
>
With the current upstream version, any command larger with a response of more
than 64 byte is broken, since the splitting loop w
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/powerpc
Prior to this patch, there were 36 uses of pr_warning and
217 uses of pr_warn in arch/powerpc
Signed-off-by: Joe Perches
---
arch/powerpc/kernel/pci-common.c| 4 ++--
arch/powerpc/mm/in
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/sparc
Prior to this patch, there was 1 use of pr_warning and
8 uses of pr_warn in arch/sparc
Signed-off-by: Joe Perches
---
arch/sparc/kernel/smp_64.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/block
Prior to this patch, there were 2 uses of pr_warning and
26 uses of pr_warn in drivers/block
Signed-off-by: Joe Perches
---
drivers/block/drbd/drbd_nl.c | 13 ++---
1 file changed, 6 insertions
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/crypto
Prior to this patch, there were 3 uses of pr_warning and
12 uses of pr_warn in drivers/crypto
Signed-off-by: Joe Perches
---
drivers/crypto/n2_core.c | 12 ++--
1 file changed, 6 insertions(+)
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/acpi
Prior to this patch, there were 20 uses of pr_warning and
45 uses of pr_warn in drivers/acpi
Signed-off-by: Joe Perches
---
drivers/acpi/apei/apei-base.c | 32
drivers/a
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/ide
Prior to this patch, there were 2 uses of pr_warning and
0 uses of pr_warn in drivers/ide
Signed-off-by: Joe Perches
---
drivers/ide/tx4938ide.c | 2 +-
drivers/ide/tx4939ide.c | 5 ++---
2 files changed
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/clocksource
Prior to this patch, there was 1 use of pr_warning and
34 uses of pr_warn in drivers/clocksource
Signed-off-by: Joe Perches
---
drivers/clocksource/samsung_pwm_timer.c | 4 ++--
1 file changed, 2
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/x86
Prior to this patch, there were 46 uses of pr_warning and
122 uses of pr_warn in arch/x86
Miscellanea:
o Coalesce a few formats and realign arguments
o Convert a couple of multiple line printks to single lin
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/input
Prior to this patch, there were 8 uses of pr_warning and
17 uses of pr_warn in drivers/input
Signed-off-by: Joe Perches
---
drivers/input/gameport/gameport.c | 4 ++--
drivers/input/joystick/gamecon.c
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/fmc
Prior to this patch, there was 1 use of pr_warning and
0 uses of pr_warn in drivers/fmc
Signed-off-by: Joe Perches
---
drivers/fmc/fmc-fakedev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/cdrom
Prior to this patch, there were 2 uses of pr_warning and
0 uses of pr_warn in drivers/cdrom
Signed-off-by: Joe Perches
---
drivers/cdrom/gdrom.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-
Am 17. Februar 2017 06:09:30 MEZ schrieb Christophe Ricard
:
>That's is correct, this is a mistake on my side and never saw it :-(.
>
>I guess it was possibly leading to "waste" at least 1 wait state on
>some
>TPMs.
Unfortunately the 1 for indicating end of waitstates does only appear once so
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/media
Prior to this patch, there was 1 use of pr_warning and
310 uses of pr_warn in drivers/media
Signed-off-by: Joe Perches
---
drivers/media/platform/sh_vou.c | 4 ++--
1 file changed, 2 insertions(+), 2 d
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/of
Prior to this patch, there were 5 uses of pr_warning and
19 uses of pr_warn in drivers/of
Signed-off-by: Joe Perches
---
drivers/of/fdt.c | 20 ++--
1 file changed, 10 insertions(+), 10 de
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/gpu
Prior to this patch, there were 15 uses of pr_warning and
20 uses of pr_warn in drivers/gpu
Signed-off-by: Joe Perches
---
drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c | 2 +-
drivers/gpu/drm/am
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/mfd
Prior to this patch, there were 4 uses of pr_warning and
9 uses of pr_warn in drivers/mfd
Signed-off-by: Joe Perches
---
drivers/mfd/db8500-prcmu.c | 2 +-
drivers/mfd/sta2x11-mfd.c | 4 ++--
drivers/
To enable eventual removal of pr_warning
This makes pr_warn use consistent for kernel/trace
Prior to this patch, there were 2 uses of pr_warning and
79 uses of pr_warn in kernel/trace
Signed-off-by: Joe Perches
---
kernel/trace/trace_benchmark.c | 4 ++--
1 file changed, 2 insertions(+), 2 del
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/sh
Prior to this patch, there was 1 use of pr_warning and
0 uses of pr_warn in drivers/sh
Signed-off-by: Joe Perches
---
drivers/sh/intc/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote:
> > On Thu, Feb 16, 2017 at 06:57:08PM -0800, Darren Hart wrote:
> > > On Fri, Feb 10, 2017 at 02:42:00AM +0200, Andy Shevchenko wrote:
> > > > On Fri, Feb 10, 2017 at 2:16 AM, Jonathan Woithe
> > > > wrote:
> > > > > On Wed, Feb
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/mtd
Prior to this patch, there were 7 uses of pr_warning and
31 uses of pr_warn in drivers/mtd
Signed-off-by: Joe Perches
---
drivers/mtd/chips/cfi_cmdset_0002.c | 12
drivers/mtd/nand/cmx270_na
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/rapidio
Prior to this patch, there was 1 use of pr_warning and
2 uses of pr_warn in drivers/rapidio
Signed-off-by: Joe Perches
---
drivers/rapidio/rio-sysfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 del
To enable eventual removal of pr_warning
This makes pr_warn use consistent for lib
Prior to this patch, there were 2 uses of pr_warning and
59 uses of pr_warn in lib
Signed-off-by: Joe Perches
---
lib/cpu_rmap.c | 2 +-
lib/dma-debug.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/platform
Prior to this patch, there were 7 uses of pr_warning and
108 uses of pr_warn in drivers/platform
Signed-off-by: Joe Perches
---
drivers/platform/x86/asus-laptop.c| 2 +-
drivers/platform/x86/ee
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/tty
Prior to this patch, there were 2 uses of pr_warning and
23 uses of pr_warn in drivers/tty
Signed-off-by: Joe Perches
---
drivers/tty/hvc/hvcs.c | 2 +-
drivers/tty/tty_io.c | 4 ++--
2 files changed,
To enable eventual removal of pr_warning
This makes pr_warn use consistent for sound/soc
Prior to this patch, there were 5 uses of pr_warning and
10 uses of pr_warn in sound/soc
Signed-off-by: Joe Perches
---
sound/soc/fsl/imx-audmux.c | 6 +++---
sound/soc/samsung/s3c-i2s-v2.c | 6 +++---
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/scsi
Prior to this patch, there was 1 use of pr_warning and
96 uses of pr_warn in drivers/scsi
Signed-off-by: Joe Perches
---
drivers/scsi/a3000.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/video
Prior to this patch, there were 6 uses of pr_warning and
25 uses of pr_warn in drivers/video
Signed-off-by: Joe Perches
---
drivers/video/fbdev/aty/radeon_base.c | 4 ++--
drivers/video/fbdev/core/fbmo
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/oprofile
Prior to this patch, there were 2 uses of pr_warning and
0 uses of pr_warn in drivers/oprofile
Signed-off-by: Joe Perches
---
drivers/oprofile/oprofile_perf.c | 8
1 file changed, 4 inserti
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/char
Prior to this patch, there were 1 use of pr_warning and
40 uses of pr_warn in drivers/char
Signed-off-by: Joe Perches
---
drivers/char/virtio_console.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/macintosh
Prior to this patch, there were 10 uses of pr_warning and
1 use of pr_warn in drivers/macintosh
Signed-off-by: Joe Perches
---
drivers/macintosh/windfarm_fcu_controls.c | 5 ++---
drivers/macintos
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/isdn
Prior to this patch, there were 20 uses of pr_warning and
3 uses of pr_warn in drivers/isdn
Signed-off-by: Joe Perches
---
drivers/isdn/gigaset/interface.c| 2 +-
drivers/isdn/hardware/mISDN/av
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/sh
Prior to this patch, there were 6 uses of pr_warning and
1 use of pr_warn in arch/sh
Signed-off-by: Joe Perches
---
arch/sh/boards/mach-sdk7786/nmi.c| 2 +-
arch/sh/drivers/pci/fixups-sdk7786.c | 2 +-
a
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/arm64
Prior to this patch, there were 7 uses of pr_warning and
27 uses of pr_warn in arch/arm64
Signed-off-by: Joe Perches
---
arch/arm64/include/asm/syscall.h | 8
arch/arm64/kernel/hw_breakpoint.c |
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/ia64
Prior to this patch, there was 1 use of pr_warning and
1 use of pr_warn in arch/ia64
Signed-off-by: Joe Perches
---
arch/ia64/kernel/setup.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
dif
To enable eventual removal of pr_warning.
This makes pr_warn use consistent for arch/arm
Prior to this patch, there were 2 uses of pr_warning and
405 uses of pr_warn in arch/arm
Signed-off-by: Joe Perches
---
arch/arm/mach-ep93xx/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
On Fri, 2017-02-17 at 14:28 +1100, Cyril Bur wrote:
> In order to manage server systems, there is typically another
> processor
> known as a BMC (Baseboard Management Controller) which is responsible
> for powering the server and other various elements, sometimes fans,
> often the system flash.
.
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> Move the LPI property table allocation into its own function, as
> this is going to be required for those associated with VMs in
> the future.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3-its.c | 28 ++-
On 17/01/2017 11:20, Marc Zyngier wrote:
> Allow the pending state of an LPI to be set or cleared via
> irq_set_irqchip_state.
>
> Signed-off-by: Marc Zyngier
Reviewed-by: Eric Auger
Eric
> ---
> drivers/irqchip/irq-gic-v3-its.c | 78
>
> 1 file ch
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> The VCPU tables can be quite sparse as well, and it makes sense
> to use indirect tables as well if possible.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3-its.c | 20 +---
> 1 file changed, 13 insertions(+
On 17/01/2017 11:20, Marc Zyngier wrote:
> Most ITS commands do operate on a collection object, and require
> a SYNC command to be performed on that collection in order to
> guarantee the execution of the first command.
>
> With GICv4 ITS, another set of commands perform similar operations
> on
On one system during power off slot, find card get power on right away.
# echo 0 > /sys/bus/pci/slots/1/power
pci_hotplug: power_write_file: power = 0
pciehp :16:00.0:pcie004: pciehp_get_power_status: SLOTCTRL a8 value read
11f1
pciehp :16:00.0:pcie004: pciehp_unconfigure_device: domai
Here, dss_init_ports is not handling return error form
dpi_init_port and sdi_init_port. Now dss_init_ports is returning
always 0. And it's making below code as a dead code.
static int dss_bind(struct device *dev)
{
.
.
r = dss_init_ports(pdev); //dss_init_ports will return always 0
if (r)/
From: Sean Wang
MT6323 PMIC is a multi-function device that includes
LED function. It allows attaching up to 4 LEDs which
can either be on, off or dimmed and/or blinked with
the controller.
Signed-off-by: Sean Wang
---
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
dri
From: Sean Wang
Add compatible string as "mt6323-led" that will make
the OF core spawn child devices for the LED subnode
of that MT6323 MFD device.
Signed-off-by: Sean Wang
---
drivers/mfd/mt6397-core.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/mfd/mt6397-core.c b/drivers
Pan Xinhui writes:
> diff --git a/arch/powerpc/xmon/xmon.c b/arch/powerpc/xmon/xmon.c
> index 9c0e17c..f6e5c3d 100644
> --- a/arch/powerpc/xmon/xmon.c
> +++ b/arch/powerpc/xmon/xmon.c
> @@ -76,6 +76,7 @@ static int xmon_gate;
> #endif /* CONFIG_SMP */
>
> static unsigned long in_xmon __read
From: Sean Wang
This patch adds documentation for devicetree bindings
for LED support as the subnode of MT6323 PMIC
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/mfd/mt6397.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/mt6397
From: Sean Wang
This patch adds documentation for devicetree bindings
for LED support on MT6323 PMIC
Signed-off-by: Sean Wang
---
.../devicetree/bindings/leds/leds-mt6323.txt | 60 ++
1 file changed, 60 insertions(+)
create mode 100644 Documentation/devicetree/bindin
From: Sean Wang
MT7623 SoC uses MT6323 PMIC as the default power supply
which has LED function insides. The patchset introduces
the LED support for MT6323 with on, off and hardware
dimmed and blinked and it should work on other similar
SoCs if also using MT6323.
Changes since v1:
- fixed typo in
Hi all,
Changes since 20170216:
The powerpc tree gained a conflict against Linus' tree.
The tip tree gained conflicts against the drm, kspp, openrisc and
powerpc trees.
The akpm-current tree gained conflicts against the kspp and tip trees.
I dropped 3 patches from the akpm tree that turn
Hi Shaohua,
On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote:
> On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote:
> > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote:
> > > @@ -1419,11 +1419,18 @@ static int try_to_unmap_one(struct page *page,
> > > struct vm_a
On 23 January 2017 at 19:57, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
>> On Mon, 16 Jan 2017, Felipe Balbi wrote:
>>
>>> > The gadget driver never calls usb_ep_queue in order to receive the next
>>> > SETUP packet; the UDC driver takes care of SETUP handling
>>> > automatically.
>>>
>>>
Hi Johannes,
On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote:
> On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote:
> > @@ -1419,11 +1419,18 @@ static int try_to_unmap_one(struct page *page,
> > struct vm_area_struct *vma,
> > VM_BUG_ON_PAGE(!PageSwapCa
On 09-02-17, 09:11, Viresh Kumar wrote:
> The first 5 patches update the PM domain and QoS frameworks to support
> that and the last one presents the front end interface to it.
@Kevin and Ulf,
Is there something wrong with this series? Its been 7 weeks since this
series is getting posted and I ha
On Fri, 2017-02-17 at 12:36 +0800, Daniel J Blueman wrote:
> When booting a VM in libvirt/KVM attached to a local bridge and KASAN
> enabled on 4.9.10, we see a stream of KASAN warnings about off-slab
> access [1].
>
> Let me know if you'd like more debug.
Could you try the following patch ?
Tha
Hi Frederic,
[auto build test ERROR on tip/timers/core]
[cannot apply to v4.10-rc8 next-20170216]
[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/commits/Frederic-Weisbecker/nohz-Fix-possible-missing
On Fri, Feb 17, 2017 at 02:47:56PM +1030, Jonathan Woithe wrote:
> On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote:
> > On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote:
> > > Do you want me to continue to use Acked-by, or should I switch to
> > > Reviewed-by?
> >
> > Th
I am not sure i understand here, are you considering there could be
burstcount > 64 with "TCG" TPM ?
Or is this because of TIS vs PTP differences ?
To be honest, this is a little behind me now :-)
On 16/02/2017 08:08, Peter Huewe wrote:
Limiting transfers to MAX_SPI_FRAMESIZE was not expecte
Fix checkpatch warning about line being over 80 characters.
Signed-off-by: Olav Haugan
---
drivers/staging/speakup/synth.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c
index b57315110e67..8340748ae9cb 10
On 2017年02月17日 12:53, John Fastabend wrote:
On 17-02-15 01:08 AM, Jason Wang wrote:
We set queues before reset which will cause a crash[1]. This is
because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
number to do the correct detection. So fix this by:
- set queues after reset
That's is correct, this is a mistake on my side and never saw it :-(.
I guess it was possibly leading to "waste" at least 1 wait state on some
TPMs.
Wouldn't it be better to merge that with #1 and update the comment
consequently?
On 16/02/2017 08:08, Peter Huewe wrote:
Wait states are sig
Are you sure it is not better to introduce this delay directly in the
rpi spi driver ?
Other than that i don't see any issue with it.
On 16/02/2017 08:09, Peter Huewe wrote:
Testing the implementation with a Raspberry Pi 2 showed that under some
circumstances its SPI master erroneously releas
v2:
-Split fixes into separate patches
Olav Haugan (2):
staging: speakup: (coding style) Simplify comparisons to NULL
staging: speakup: (coding style) Limit line to 80 chars
drivers/staging/speakup/synth.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
--
Qual
Fix checkpatch check notices by simplifying comparisons to NULL.
Signed-off-by: Olav Haugan
---
drivers/staging/speakup/synth.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c
index a61c02ba06d
Nitpick: Are you sure this patch is necessary having #3 on top of it ?
On 16/02/2017 08:08, Peter Huewe wrote:
Abort the transfer with ETIMEDOUT when the TPM signals more than
TPM_RETRY wait states. Continuing with the transfer in this state
will only lead to arbitrary failures in other parts of
On 02/16/17 15:27, Daniel Kiper wrote:
>
> That is obvious. Do you think that Multiboot/Multiboot2 protocols are
> substantially suboptimal?
>
Yes. They push a lot of things into the bootloader for no good reason,
thus tying the kernel's hands and making the whole boot process more
fragile.
It
On 17-02-15 01:08 AM, Jason Wang wrote:
> We set queues before reset which will cause a crash[1]. This is
> because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
> number to do the correct detection. So fix this by:
>
> - set queues after reset, to keep the old vi->curr_queue_pairs.
Hi all,
Today's linux-next merge of the akpm-current tree got conflicts in:
arch/x86/Kconfig.debug
arch/x86/kernel/Makefile
between commits:
ad21fc4faa2a ("arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to
be common")
3ad38ceb2769 ("x86/mm: Remove CONFIG_DEBUG_NX_TEST")
fro
commit bb98e72adaf9d19719aba35f802d4836f5d5176c
Author: Hans de Goede
Date: Fri Dec 2 15:29:04 2016 +0100
drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from
vlv_init_display_clock_gating
On my Cherrytrail CUBE iwork8 Air tablet PIPE-A would get stuck on loading
i915 at boo
Oleg Nesterov writes:
> de_thread() waits for other threads with ->cred_guard_mutex held and this
> is really bad because the time is not bounded, debugger can delay the exit
> and this lock has a lot of users (mostly abusers imo) in fs/proc and more.
> And this leads to deadlock if debugger trie
Hi all,
Today's linux-next merge of the akpm-current tree got conflicts in:
arch/cris/include/asm/Kbuild
arch/m32r/include/asm/Kbuild
arch/parisc/include/asm/Kbuild
arch/score/include/asm/Kbuild
between commit:
b672592f0221 ("sched/cputime: Remove generic asm headers")
from the tip t
When booting a VM in libvirt/KVM attached to a local bridge and KASAN
enabled on 4.9.10, we see a stream of KASAN warnings about off-slab
access [1].
Let me know if you'd like more debug.
Thanks,
Daniel
-- [1]
[ 473.579567] BUG: KASAN: slab-out-of-bounds in
ip_route_me_harder+0xbd5/0xf20 at
On Wed, Feb 15, 2017 at 10:41:40PM +, Ben Hutchings wrote:
> 3.16.40-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Dave Chinner
>
> commit 541d48f05fa1c19a4a968d38df685529e728a20a upstream.
>
> oss.sgi.com is going away, move contact
Hello Linus,
Here are a few last minute NTB bug fixes for v4.10. They are fairly
critical, and would appreicate them getting pulled in (though I
understand this is extremely late in the cycle).
Thanks,
Jon
The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc:
Linux 4.
Hi Arnd,
On 17/02/17 02:28, Arnd Bergmann wrote:
> On Thursday, February 16, 2017 9:50:39 PM CET Chris Packham wrote:
>> The DFX server on the 98dx3236 and compatible SoCs has an ID register
>> that provides revision information that the PCI based ID register
>> doesn't have. Use this if it's avail
On Thu, Feb 16, 2017 at 11:08 AM, wrote:
> On Thu, Feb 16, 2017 at 10:52:19AM -0500, Soheil Hassas Yeganeh wrote:
>> On Thu, Feb 16, 2017 at 10:50 AM, Soheil Hassas Yeganeh
>> wrote:
>> > Thank you Vito for the report.
>> >
>> > The patch you cited actually resolves a similar backward compatibil
On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote:
> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote:
> > Do you want me to continue to use Acked-by, or should I switch to
> > Reviewed-by?
>
> These tags do have different meanings, and have come up at Kernel Summit the
>
On Fri, Feb 17, 2017 at 09:25:27AM +0800, Ming Lei wrote:
> Hi Shaohua,
>
> On Fri, Feb 17, 2017 at 6:16 AM, Shaohua Li wrote:
> > On Thu, Feb 16, 2017 at 07:45:30PM +0800, Ming Lei wrote:
> >> In MD's resync I/O path, there are lots of direct access to bio's
> >> bvec table. This patchset kills
1 - 100 of 854 matches
Mail list logo
