On Thu, 26 Feb 2015, Borislav Petkov wrote:
On Thu, Feb 26, 2015 at 10:19:42AM -0800, Vikas Shivappa wrote:
This would be an indication that the System support RDT. On a system with
RDT would see a print.
intel_rdt: cbmlength: xx , CLOss:xx
Ok, so I have a capacity bitmask of length xx and
On Thu, Feb 26, 2015 at 10:28:17AM -0800, Paul E. McKenney wrote:
> Color me confused, both by the existing code and the modifications.
>
> It appears that you are using seqlock to force readers to retry when
> a concurrent update occurs, but I don't see what is ensuring that the
> readers see g
On Wed, 2015-02-25 at 11:47 -0500, Nicolas Pitre wrote:
> On Wed, 25 Feb 2015, Russell King - ARM Linux wrote:
>
> > On Thu, Feb 05, 2015 at 04:11:00PM +, Russell King - ARM Linux wrote:
> > > On Thu, Feb 05, 2015 at 06:29:18AM -0800, Paul E. McKenney wrote:
> > > > Works for me, assuming no h
On Thu, Feb 26, 2015 at 11:00 AM, Bjorn Andersson wrote:
> On Sun, Feb 22, 2015 at 11:54 PM, Srinivas Kandagatla
> wrote:
>> This patch adds rpm node to apq8064 dt as rpm would be used by other
>> devices for regulator support. Also adds all the regulators in the rpm.
>>
>
> This looks good, with
- Original Message -
> From: "Paul E. McKenney"
> To: "Peter Zijlstra"
> Cc: "Mathieu Desnoyers" , "Andi Kleen"
> , "Andi Kleen"
> , x...@kernel.org, linux-kernel@vger.kernel.org,
> o...@redhat.com, ru...@rustcorp.com.au,
> mi...@kernel.org
> Sent: Thursday, February 26, 2015 1:28:17 PM
On Thu, Feb 26, 2015 at 09:42:06AM +0900, Minchan Kim wrote:
> Hello,
>
> On Wed, Feb 25, 2015 at 10:37:48AM -0800, Shaohua Li wrote:
> > On Wed, Feb 25, 2015 at 04:11:18PM +0900, Minchan Kim wrote:
> > > On Wed, Feb 25, 2015 at 09:08:09AM +0900, Minchan Kim wrote:
> > > > Hi Michal,
> > > >
> >
On Thu, Feb 26, 2015 at 10:25 AM, Kumar Gala wrote:
>
> On Feb 23, 2015, at 1:54 AM, Srinivas Kandagatla
> wrote:
>
>> This patch adds rpm node to apq8064 dt as rpm would be used by other
>> devices for regulator support. Also adds all the regulators in the rpm.
>>
>> Signed-off-by: Srinivas Kan
Add trace events for the power allocator governor and the power actor
interface of the cpu cooling device.
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Signed-off-by: Javi Merino
---
drivers/thermal/cpu_cooling.c | 31 +++
A governor may need to store its current state between calls to
throttle(). That state depends on the thermal zone, so store it as
private data in struct thermal_zone_device.
The governors may have two new ops: bind_to_tz() and unbind_from_tz().
When provided, these functions let governors do som
It's useful for tuning to be able to edit thermal_zone_parameters from
userspace. Export them to the thermal_zone sysfs so that they can be
easily changed.
Cc: Zhang Rui
Cc: Eduardo Valentin
Signed-off-by: Javi Merino
---
Documentation/thermal/sysfs-api.txt | 52 +
drivers/th
Add three optional callbacks to the cooling device interface to allow
them to express power. In addition to the callbacks, add helpers to
identify cooling devices that implement the power cooling device API.
Cc: Zhang Rui
Cc: Eduardo Valentin
Signed-off-by: Javi Merino
---
drivers/thermal/the
Add a basic power model to the cpu cooling device to implement the
power cooling device API. The power model uses the current frequency,
current load and OPPs for the power calculations. The cpus must have
registered their OPPs using the OPP library.
Cc: Zhang Rui
Cc: Eduardo Valentin
Signed-o
The power allocator governor is a thermal governor that controls system
and device power allocation to control temperature. Conceptually, the
implementation divides the sustainable power of a thermal zone among
all the heat sources in that zone.
This governor relies on "power actors", entities th
From: Punit Agrawal
Introduce an optional property called, sustainable-power, which
represents the power (in mW) which the thermal zone can safely
dissipate.
If provided the property is parsed and associated with the thermal
zone via the thermal zone parameters.
Cc: Zhang Rui
Cc: Eduardo Valen
On Sun, Feb 22, 2015 at 11:54 PM, Srinivas Kandagatla
wrote:
> This patch adds rpm node to apq8064 dt as rpm would be used by other
> devices for regulator support. Also adds all the regulators in the rpm.
>
This looks good, with Kumars suggestion of GIT defines
Reviewed-by: Bjorn Andersson
How
On 02/26/2015 10:42 AM, Russell King - ARM Linux wrote:
On Thu, Feb 26, 2015 at 11:37:08AM +0100, Geert Uytterhoeven wrote:
When trying to kexec into a new kernel on a platform where multiple CPU
cores are present, but no SMP bringup code is available yet, the
kexec_load system call fails with:
Hi linux-pm,
The power allocator governor allocates device power to control
temperature. This requires transforming performance requests into
requested power, which we do with an extended cooling device API
introduced in patch 2 (thermal: extend the cooling device API to
include power information
On Thu, Feb 26, 2015 at 10:19:42AM -0800, Vikas Shivappa wrote:
> This would be an indication that the System support RDT. On a system with
> RDT would see a print.
>
> intel_rdt: cbmlength: xx , CLOss:xx
Ok, so I have a capacity bitmask of length xx and yy classes of service.
And?
Are you expec
From: Nikolai Kondrashov
Merge the hid-huion driver into hid-uclogic as all the devices supported
by hid-huion are in fact UC-Logic devices.
Signed-off-by: Nikolai Kondrashov
Signed-off-by: Benjamin Tissoires
---
no changes in v2
drivers/hid/Kconfig | 8 +-
drivers/hid/Makefile
Hi,
this is the v2 of the merge of Huion and UcLogic.
I removed the previous 3/4 as mentioned during the review and added
3 more.
Note that 6/6 could have been squashed in 2/6, but I kept it separate
to keep the first 2 reviewed.
Cheers,
Benjamin
Benjamin Tissoires (6):
HID: uclogic: Set quirk
Based on a patch from: Nikolai Kondrashov
Most of the tablets handled by hid-uclogic already use MULTI_INPUT.
For the ones which are not quirked in usbhid/hidquirks, they have a
custom report descriptor which contains only one report per HID
interface. For those tablets HID_QUIRK_MULTI_INPUT is t
NO_EMPTY_INPUT is useful when MULTI_INPUT is set. It prevents to create
empty input nodes that user space does not know what to do with.
It does not seem to be required at the moment, this is just a preventive
patch. This check is only made during the plug of the device, so it does
not hurt to hav
We append "Pen", "Pad", "Mouse", "Keyboard", "Consumer Control" or
"System Control" suffix to the appropriate input node to match what
the Wacom driver does and be more convenient for the user to know
which one is which.
Signed-off-by: Benjamin Tissoires
---
changes in v2:
- completed the list w
This hack is only needed for Huion tablets. It does not seem to have
any effect on the other tablets handled by this device right now, but
it's better to check for the product id sooner than discovering that
we have messed up one tablet later.
Signed-off-by: Benjamin Tissoires
---
New in v2
dr
Some Huion tablets present 2 HID Pen interfaces. Only one is used, so
we can drop the unused one.
Signed-off-by: Benjamin Tissoires
---
New in v2
drivers/hid/hid-uclogic.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/hid/hid-uclogic.c b/drivers/hid/hid-uclo
Hi Sudeep,
Thank you for the patch.
On Thursday 26 February 2015 11:47:57 Sudeep Holla wrote:
> As per the SAF1761 data sheet[0], the DcChipID register represents
> the hardware version number (0001h) and the chip ID (1582h) for the
> Peripheral Controller.
>
> However as per the ISP1761 data sh
On to, 2015-02-26 at 10:34 +0100, Bjørn Mork wrote:
> Imre Deak writes:
>
> >> That patch fixes the problem, with only pci_set_power_state commented
> >> out. Do you still want me to try with pci_disable_device() commented
> >> out as well?
> >
> > No, but it would help if you could still try the
On Wed, 2015-02-25 at 20:15 -0800, tip-bot for Matt Fleming wrote:
> Commit-ID: 4afbb24ce5e723c8a093a6674a3c33062175078a
> Gitweb: http://git.kernel.org/tip/4afbb24ce5e723c8a093a6674a3c33062175078a
> Author: Matt Fleming
> AuthorDate: Fri, 23 Jan 2015 18:45:44 +
> Committer: Ingo Mol
On 02/24/2015 12:54 AM, Brian Norris wrote:
> On Mon, Feb 23, 2015 at 12:32:42PM -0300, Ezequiel Garcia wrote:
>> On 01/31/2015 04:02 AM, Brian Norris wrote:
>>> Unless someone else thinks they have an excellent handle on the above,
>>> I'll take a stab at doing this. I actually have a few patche
Signed-off-by: Tal Shorer
---
drivers/usb/gadget/function/f_mass_storage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/f_mass_storage.c
b/drivers/usb/gadget/function/f_mass_storage.c
index 811929c..6d5ca2b 100644
--- a/drivers/usb/gadget/functi
Look fine to me.
Thanks.
Best Regards,
Ge GAO
-Original Message-
From: Jonathan Cameron [mailto:ji...@kernel.org]
Sent: Saturday, February 21, 2015 11:01 AM
To: Viorel Suman; linux-...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org; Srinivas Pandruvada; Ge Gao
Subject: Re: [PATCH v2]
These 2 are left over from the USB dependency cleaning, so there is
no need to keep them.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/hid-multitouch.c | 1 -
drivers/hid/hid-steelseries.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-m
Seems to be the same clock tree change problems as in :
http://www.spinics.net/lists/arm-kernel/msg400244.html
I am able to help to reproduce/test/fix the problem with KaRo imx6q board.
--Mika
-- Forwarded message --
From: Mika Penttilä
Date: Thu, Feb 26, 2015 at 11:58 AM
Subj
On 26/02/15 18:29, Kumar Gala wrote:
On Feb 23, 2015, at 1:53 AM, Srinivas Kandagatla
wrote:
Hi Kumar,
Now that the rpm header file dependency is resolved, Could you
queue these dt patches for rc2.
Thanks,
srini
Nicolas Dechesne (3):
ARM: DT: apq8064: add pci support in CM QS600
ARM
On Thu, Feb 26, 2015 at 8:45 AM, Kees Cook wrote:
> On Thu, Feb 26, 2015 at 7:17 AM, Andy Lutomirski wrote:
>> On Wed, Feb 25, 2015 at 11:06 PM, Wang Nan wrote:
>>> The reason why mapping idt_table to fixmap area should also be applied
>>> to debug_idt_table and trace_idt_table. This patch does
On Thu, Feb 26, 2015 at 05:43:56PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 26, 2015 at 04:02:43PM +, Mathieu Desnoyers wrote:
> > Perhaps you could use mod_value() below, and introduce a
> > "mod_size()" too. This would keep the init vs core selection
> > out of the traversal code.
>
> Inde
On Feb 23, 2015, at 1:53 AM, Srinivas Kandagatla
wrote:
> Hi Kumar,
> Now that the rpm header file dependency is resolved, Could you
> queue these dt patches for rc2.
>
>
> Thanks,
> srini
>
> Nicolas Dechesne (3):
> ARM: DT: apq8064: add pci support in CM QS600
> ARM: DT: apq8064: Add us
On Feb 23, 2015, at 1:55 AM, Srinivas Kandagatla
wrote:
> This patch adds device tree nodes to support two usb hosts on APQ8064
> SOC.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 40 +
> arch/arm/boot/dts/qcom-apq8064.dtsi
On Thu, 26 Feb 2015, Serge E. Hallyn wrote:
> > Well doing that breaks su.
>
> Don't what exactly? You're saying that doing
>
> pI' = pI
> pA' = pA (pA is ambient)
> pP' = (X & fP) | (pI & (fI | pA))
> pE' = pP' & (fE | pA)
>
> stopped su from having CAP_SETGID while
>
> pI' = pI
> pA' = pA (pA
On Feb 23, 2015, at 1:55 AM, Srinivas Kandagatla
wrote:
> This patch adds USB OTG support on USB1 of APQ8064 SOC.
> Tested on IFC6410 with ethernet gadget.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 22
> arch/arm/boot/dts/q
On 26/02/15 18:25, Kumar Gala wrote:
On Feb 23, 2015, at 1:54 AM, Srinivas Kandagatla
wrote:
This patch adds rpm node to apq8064 dt as rpm would be used by other
devices for regulator support. Also adds all the regulators in the rpm.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/d
On Feb 23, 2015, at 1:54 AM, Srinivas Kandagatla
wrote:
> This patch adds rpm node to apq8064 dt as rpm would be used by other
> devices for regulator support. Also adds all the regulators in the rpm.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064.dtsi | 241 +++
From: Borislav Petkov
... so that we can call it multiple times. See next patch.
Signed-off-by: Borislav Petkov
---
tools/perf/bench/mem-memcpy.c | 120 --
1 file changed, 58 insertions(+), 62 deletions(-)
diff --git a/tools/perf/bench/mem-memcpy.c b/to
From: Borislav Petkov
Adjust perf bench to the new changes in the alternatives code for
memcpy/memset.
Signed-off-by: Borislav Petkov
---
tools/perf/bench/mem-memcpy-x86-64-asm-def.h | 6 +++---
tools/perf/bench/mem-memcpy-x86-64-asm.S | 2 --
tools/perf/bench/mem-memset-x86-64-asm-def.h
On Wed, 25 Feb 2015, Borislav Petkov wrote:
On Tue, Feb 24, 2015 at 04:42:10PM -0800, Vikas Shivappa wrote:
+
+ pr_info("cbmlength:%u,Closs: %u\n", cbm_len, maxid);
This text message needs to be much more user-friendly if it is going out
to the console unconditionally.
bit mask len
On Thu, 26 Feb 2015, Vikas Shivappa wrote:
On Thu, 26 Feb 2015, Ingo Molnar wrote:
* Luck, Tony wrote:
The CAT thing was annoying already, but at least one
can find that in the SDM, this RDT thing, not a single
mention.
The problems of development at the bleeding edge. Would
you rath
From: Borislav Petkov
perf bench mem mem{set,cpy} -r all thus runs all available mem
benchmarking routines.
Signed-off-by: Borislav Petkov
---
tools/perf/bench/mem-memcpy.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/tools/perf/bench/mem-memcpy.c b/tools/perf/
On Thu, 26 Feb 2015 19:17:03 +0100
"Rafael J. Wysocki" wrote:
> On Thursday, February 26, 2015 04:47:24 PM Boris Brezillon wrote:
> > On Thu, 26 Feb 2015 16:44:16 +0100
> > "Rafael J. Wysocki" wrote:
[...]
> > >
> > > But it is still a bit risky. Namely, if the driver in question is
> > > s
Hi all,
So this alternatives patchset breaks perf bench mem, here are a couple
of patches ontop, you guys tell me whether it makes sense. I wanted to
make it run all memset/memcpy routines so here are a couple of patches
which do this:
./perf bench mem memset -l 20MB -r all
# Running 'mem/memset'
--
Hello me and my partner have around 20M pounds looking to invest in a
lucrative business! ,Kindly let me know if we can work together in
this avenue and tell me more about your company Have a blessed day
and do reply to me through this email mradams2...@outlook.com or
mrhami...@outlook.com
Bes
This patch makes use of DEVICE_ATTR_{RW, WO} macros, simplifying
device attributes creation.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_haps.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/platform/x86/toshiba_haps.c
b/drivers/platform/x86/t
This patch adds a new file describing the sysfs entries for the
toshiba_haps driver.
Signed-off-by: Azael Avalos
---
Documentation/ABI/testing/sysfs-driver-toshiba_haps | 20
1 file changed, 20 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-driver-toshiba_
These patches make some misc chanes to the driver, replacing sscanf with
kstrtoint, DEVICE_ATTR_{RW, WO} macros and adding documentation about
the sysfs entries.
Azael Avalos (3):
toshiba_haps: Replace sscanf with kstrtoint
toshiba_haps: Make use of DEVICE_ATTR_{RW, WO} macros
Documentation/
These patches add support to a new function that queries the supported Hotkey
Event Type, making the use of the DMI matching unnecessary and also fixes
the "Special Functions" mode on some laptops.
Azael Avalos (3):
toshiba_acpi: Add Hotkey Event Type function and definitions
toshiba_acpi: Use
With the previous patch adding support to "Hotkey Event Type", we can
now use the type to distinguish which keymap to use.
This patch changes the toshiba_acpi_setup_keyboard function to make
use of the hotkey event type to choose the correct keymap without the
need to use the DMI matching list.
S
This patch simply replaces the use of sscanf with kstrtoint returning
the error code in case that something went bad.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_haps.c | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/drivers/platfo
This patch adds support to query the "Hotkey Event Type" the system
supports.
There are two main event types (so far), 0x10 and 0x11, with the
first beign all those laptops that have the old keyboard layout, and
the latter all those new laptops with the new keyboard layout.
Signed-off-by: Azael A
Some Toshiba laptops with the "Special Functions" feature enabled
fail to properly enable such feature unless a specific value is
used to enable the hotkey events.
This patch adds a new function called "*_enable_special_functions",
that simply makes a call to the HCI_HOTKEY_EVENT call, but this ti
Hi Sebastian,
On 17/02/2015 19:52, Sebastian Hesselbarth wrote:
> This patch set improves current mainline support for the Compulab
> CM-A510 System-on-Module (SoM) and its default Compulab SBC-A510
> base board. Thanks to Gabriel Dobato who agreed to remote debug and
> test the provided DT change
On Thursday, February 26, 2015 04:47:24 PM Boris Brezillon wrote:
> On Thu, 26 Feb 2015 16:44:16 +0100
> "Rafael J. Wysocki" wrote:
>
> > On Thursday, February 26, 2015 09:03:47 AM Boris Brezillon wrote:
> > > Hi Rafael,
> > >
> > > On Wed, 25 Feb 2015 22:59:36 +0100
> > > "Rafael J. Wysocki" w
On Wed, Feb 25, 2015 at 07:00:38PM +, Eduardo Valentin wrote:
> On Wed, Feb 25, 2015 at 02:48:49PM +, Javi Merino wrote:
> > Hi Eduardo,
> >
> > On Tue, Feb 24, 2015 at 06:21:26PM +, Eduardo Valentin wrote:
> > > On Wed, Jan 28, 2015 at 05:00:35PM +, Javi Merino wrote:
> > > > +
>
On Thu, Feb 26, 2015 at 11:37:08AM +0100, Geert Uytterhoeven wrote:
> When trying to kexec into a new kernel on a platform where multiple CPU
> cores are present, but no SMP bringup code is available yet, the
> kexec_load system call fails with:
>
> kexec_load failed: Invalid argument
>
> The
On Thu, Feb 26, 2015 at 1:08 AM, Javier Martinez Canillas
wrote:
> Hello Olof,
>
> Thanks a lot for your feedback.
>
> On 02/26/2015 02:13 AM, Gwendal Grignou wrote:
>> Olof,
>>
>> I think the way Javier did it is fine, the 'major' of the ioctl is
>> 0xEC, from ':'.
>>
>> Gwendal.
>>
>
> As Gwenda
On Wed 25-02-15 12:41:07, David Rientjes wrote:
> On Wed, 25 Feb 2015, Michal Hocko wrote:
>
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index 2d224bbdf8e8..c2ff40a30003 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -2363,7 +2363,8 @@ __alloc_pages_may_oom(gfp_t gfp_
On Thu, 26 Feb 2015, Ingo Molnar wrote:
* Luck, Tony wrote:
The CAT thing was annoying already, but at least one
can find that in the SDM, this RDT thing, not a single
mention.
The problems of development at the bleeding edge. Would
you rather Linux sat on the sidelines until there are
e
Hi Chris,
I have not heard any more feedback on this patchset. Is it in your
queue to review or merge into your tree?
Thanks,
Scott
On 15-02-09 04:06 PM, Scott Branden wrote:
This series of patchsets contains the IPROC SDHCI driver used
in a series of Broadcom SoCs
Quirks are also added to
Linus,
please pull sound fixes for v4.0-rc2 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.0-rc2
The topmost commit is de5d0ad506cb10ab143e2ffb9def7607e3671f83
sound fixes for 4.0-rc2
Most of
On February 26, 2015 8:35:17 AM EST, Juergen Gross wrote:
>Add myself as maintainer for the Xen pvUSB stuff.
>
>Signed-off-by: Juergen Gross
>---
> MAINTAINERS | 8
> 1 file changed, 8 insertions(+)
>
>diff --git a/MAINTAINERS b/MAINTAINERS
>index ddc5a8c..8ec1e1f 100644
>--- a/MAINTAINER
On Thu, Feb 26, 2015 at 04:55:35PM +, Mathieu Desnoyers wrote:
> > +static unsigned long mod_value(struct module *mod, int idx)
> > +{
> > + if (idx & init_bit)
>
> Hrm, my first reflex is to look for a "init_bit" variable here.
> Should we use caps for enum entries instead ? e.g. INIT_BIT ?
On Thu, Feb 26, 2015 at 04:55:35PM +, Mathieu Desnoyers wrote:
> > Dunno, it seemed like a good a place as any.
>
> My personal coding-style is to put all definitions
> at the top of C files, but I don't know if it's within
> the kernel coding style guide lines or just something
> I'm personal
On 02/26/2015 03:37 AM, Geert Uytterhoeven wrote:
When trying to kexec into a new kernel on a platform where multiple CPU
cores are present, but no SMP bringup code is available yet, the
kexec_load system call fails with:
kexec_load failed: Invalid argument
The SMP test added to machine_ke
On Thu, Feb 26, 2015 at 04:50:46PM +0100, Quentin Casasnovas wrote:
> Improper pointer arithmetics when calculating the address of the extended
> header could lead to an out of bounds memory read and kernel panic.
>
> Signed-off-by: Quentin Casasnovas
Applied, thanks.
--
Regards/Gruss,
Bor
On Thu, 26 Feb 2015 19:05:57 +0800
Zefan Li wrote:
> Make it return -ENOMEM ? Or make it a global variable and allocate memory for
> it
> in cpuset_init().
Here you are. This addresses your concern, as well as the
issue David Rientjes found earlier.
---8<---
Subject: cpusets,isolcpus: add fil
Sudip,
On Thu, Feb 26, 2015 at 01:18:31PM +0800, Sudip JAIN wrote:
> Hello Jeremiah,
>
> Please find the patch "inline"
>
There are more problems than just not being "inline".
- The subject line wrong.
- The log message is formatted wrong.
- This patch is not in a form that can be applied.
- A
On Feb 25 2015 or thereabouts, Benjamin Tissoires wrote:
> On Feb 25 2015 or thereabouts, Nikolai Kondrashov wrote:
> > On 02/25/2015 02:05 AM, Benjamin Tissoires wrote:
> > >The Huion tablets show 3 interfaces. Only the first and the third
> > >are currently used.
> > >Also remove HID_QUIRK_MULTI_
- Original Message -
> From: "Peter Zijlstra"
> To: "Mathieu Desnoyers"
> Cc: "Andi Kleen" , "Andi Kleen" ,
> x...@kernel.org,
> linux-kernel@vger.kernel.org, o...@redhat.com, paul...@linux.vnet.ibm.com,
> ru...@rustcorp.com.au, mi...@kernel.org
> Sent: Thursday, February 26, 2015 11:43
Use external clock for RMII since the internal clock doesn't meet the
jitter requirements.
Signed-off-by: George McCollister
---
arch/arm/boot/dts/am335x-lxm.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-lxm.dts b/arch/arm/boot/dts/am335x-lxm.dts
index 7266
On Thu, Feb 26, 2015 at 04:02:43PM +, Mathieu Desnoyers wrote:
> Perhaps you could use mod_value() below, and introduce a
> "mod_size()" too. This would keep the init vs core selection
> out of the traversal code.
Indeed!
> Is it customary to define static variables in the
> middle of a C fil
On Thu, Feb 26, 2015 at 7:17 AM, Andy Lutomirski wrote:
> On Wed, Feb 25, 2015 at 11:06 PM, Wang Nan wrote:
>> The reason why mapping idt_table to fixmap area should also be applied
>> to debug_idt_table and trace_idt_table. This patch does same thing for
>> all IDTs.
>>
>> Signed-off-by: Wang Na
Change 'disabed' and 'disabel' to 'disabled'
Change 'inviation' to 'invitation'
Change 'negoitation' to 'negotiation'
Signed-off-by: Yannick Guerrini
---
drivers/staging/rtl8188eu/include/wifi.h| 24
drivers/staging/rtl8188eu/os_dep/usb_intf.c | 2 +-
2 files change
On Thu, Feb 26, 2015 at 10:48 AM, Lorenzo Pieralisi
wrote:
> On Wed, Feb 25, 2015 at 11:36:10PM +, Rafael J. Wysocki wrote:
>> On Wednesday, February 25, 2015 02:39:17 PM Lorenzo Pieralisi wrote:
>> > On Wed, Feb 25, 2015 at 02:13:23PM +, Daniel Lezcano wrote:
[cut]
>> I'm not entirely a
On Thu, Feb 26, 2015 at 5:02 AM, Mike Galbraith
wrote:
> On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
>
>> The deadlock returned after I applied this patch in v3.18.7-rt2.
>
> Grr, because dummy here munged a reject when he backported to 3.18-rt.
> Please try the below, my trusty
Building with the attached random configuration file,
In file included from include/linux/pci.h:30:0,
from sound/soc/intel/sst/sst_drv_interface.c:22:
sound/soc/intel/sst/sst_drv_interface.c: In function 'sst_power_control':
sound/soc/intel/sst/sst_drv_interface.c:146:28: error: '
From: Imre Palik
Date: Thu, 26 Feb 2015 11:19:25 +0100
> If you are looking for peculiarities in my setup then here they are:
> I am on 4k pages, and perf is not working :-(
> (I am trying to fix those too, but that is far from being a low hanging
> fruit.)
> So my guess would be that the packet
The stylus of this device works just fine out of the box.
The touch is seen by default as a mouse with relative events and some
gestures.
The wireless and the wired version have slightly different firmwares, but
the debug mode 2 on the feature 2 is common to the 2 devices. In this mode,
all the rep
On Thu, Feb 26, 2015 at 10:32 AM, Andy Lutomirski wrote:
> On Tue, Feb 24, 2015 at 7:23 PM, Brian Gerst wrote:
>> On Tue, Feb 24, 2015 at 3:08 PM, Denys Vlasenko
>> wrote:
>>> On Tue, Feb 24, 2015 at 9:02 PM, Andy Lutomirski
>>> wrote:
> This currently fails in 32-bit kernels (at least in
sched/rt: Use IPI to trigger RT task push migration instead of pulling
When debugging the latencies on a 40 core box, where we hit 300 to
500 microsecond latencies, I found there was a huge contention on the
runqueue locks.
Investigating it further, running ftrace, I found that it was due to
the
Hi Stephan,
Sorry for delayed answer.
On Thu, 2015-02-19 at 16:49 -0800, Stephen Boyd wrote:
> On 02/03/15 04:17, Ivan T. Ivanov wrote:
> > Following set of patches add initial DT support for PMIC devices
> > found on recent Quqalcomm chipsets. Details for SPMI bus and PMIC arbiter
> > could be
arm_kprobe_ftrace() could fail, especially after introducing ftrace IPMODIFY
flag and LifePatching. But this situation is not properly handled.
This patch adds the most important changes.
First, it does not make sense to register "kprobe_ftrace_ops" if the filter was
not set.
Second, we should re
arm_kprobe_ftrace() could fail, especially after introducing ftrace IPMODIFY
flag and LifePatching. This patch set adds the error handling and also some
related fixes.
1st patch includes the most important change. It helps to keep Kprobes
in a sane state.
2nd and 3rd patch allows to propagate the
The global kprobes_all_disarmed flag says that all Kprobes are disarmed
even when they are marked as enabled. This is properly handled in
register_kprobe() but it is ignored in __disable_kprobe().
This problem gets more serious after we started handling errors from
disarm_kprobe(). The second disa
Hi Dmitry,
Thanks for the update of no need to change any of dt-binding prefixes.
I just sent out a v2 patch addressing all of your other comments.
On 15-02-23 09:49 AM, Dmitry Torokhov wrote:
Hi Scott,
On Sun, Feb 15, 2015 at 09:17:51PM -0800, Dmitry Torokhov wrote:
On Sat, Feb 14, 2015 at
On Thu, Feb 26, 2015 at 7:59 AM, Borislav Petkov wrote:
> On Thu, Feb 26, 2015 at 07:16:28AM -0800, Andy Lutomirski wrote:
>> I'm declaring a temporary moratorium on new development here until
>> the already-queued stuff is in -tip, looks okay, and we're in an
>> appropriate part of the cycle. The
The System Trace Macrocell (STM) is an IP block falling under the
CoreSight umbrella. It's main purpose it so expose stimulus channels
to any system component for the purpose of information logging.
Bindings for this IP block adds a couple of items to the current
mandatory definition for CoreSigh
arm_kprobe_ftrace() could fail, especially after introducing ftrace IPMODIFY
flag and LifePatching.
registry_kprobe() and registry_aggr_kprobe() do not mind about the error
because the kprobe gets disabled and they keep it registered.
But enable_kprobe() should propagate the error because its tas
Add driver for Broadcom's keypad controller.
Broadcom Keypad controller is used to interface a SoC with a matrix-type
keypad device. The keypad controller supports multiple row and column lines.
A key can be placed at each intersection of a unique row and a unique column.
The keypad controller can
Kprobes might get globally disabled by writing to
/sys/kernel/debug/kprobes/enabled but this situation
is not visible in /sys/kernel/debug/kprobes/list.
This patch updates the list, so that it shows [GLOBALLY DISABLED]
when the related Kprobe is enabled but globally disabled.
It also updates the
Documents the Broadcom keypad controller device tree bindings.
Reviewed-by: Ray Jui
Signed-off-by: Scott Branden
---
.../devicetree/bindings/input/brcm,bcm-keypad.txt | 108 +
1 file changed, 108 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/brcm
kprobes_all_disarmed global flag says that Kprobes are disarmed even
when the Kprobe-specific KPROBE_FLAG_DISABLED is not set.
The global flag is currently set by arm_all_probes() and disarm_all_probes()
functions even when they were not able to switch all Kprobes. It might result
in further error
Also disarm_kprobe_ftrace() could fail, for example if there is an internal
error in the Kprobe code and we try to unregister some Kprobe that is not
registered.
If we fail to unregister the ftrace function, we still could try to disarm
the Kprobe by removing the filter. This is why the first erro
301 - 400 of 793 matches
Mail list logo
