On Mon, Nov 3, 2014 at 1:27 PM, Greg Kroah-Hartman
wrote:
> On Mon, Nov 03, 2014 at 11:33:23AM -0800, Andy Lutomirski wrote:
>> On 11/02/2014 07:07 PM, Kweh Hock Leong wrote:
>> > From: "Kweh, Hock Leong"
>> >
>> >
>> > Hi Guys,
>> >
>> > This patchset is created on top of "efi: Capsule update
> > Between 3.17 and 3.18-rc2, qla2xxx is broken on my sparc64 machines. It
> > fails to boot (hangs in firmware rings init).
> >
> > This is the result of bisect:
> >
> > 98aee70d19a7e3203649fa2078464e4f402a0ad8 is the first bad commit
> > commit 98aee70d19a7e3203649fa2078464e4f402a0ad8
> >
On Mon, 3 Nov 2014, Dave Hansen wrote:
> On 10/27/2014 01:49 PM, Thomas Gleixner wrote:
> > Errm. Before user space can use the bounds table for the new mapping
> > it needs to add the entries, right? So:
> >
> > CPU 0 CPU 1
> >
> > down_write(mm->bd_sem);
>
From: "Steven Rostedt (Red Hat)"
Add a helper function reset_tracer() that will clear the current_tracer
(echo nop > current_tracer).
Signed-off-by: Steven Rostedt
---
tools/testing/selftests/ftrace/test.d/functions | 4
1 file changed, 4 insertions(+)
diff --git
From: "Steven Rostedt (Red Hat)"
Added three test cases to get the feel of adding tests to ftracetest.
The three cases are:
function profiling test, to make sure function profiling still works
with function tracing (was a regression)
function graph filter test to make sure that function
From: "Steven Rostedt (Red Hat)"
Created the file tools/testing/ftrace/test.d/functions that will
hold helper functions.
First function added was clear_trace() that is descriptive in its
name to show that "echo > trace" is clearing the trace file.
Signed-off-by: Steven Rostedt
---
From: "Steven Rostedt (Red Hat)"
Add calls that disable and enable tracing respectively by echoing
0 or 1 into tracing_on.
Signed-off-by: Steven Rostedt
---
tools/testing/selftests/ftrace/test.d/functions | 8
1 file changed, 8 insertions(+)
diff --git
Second attempt. I took the advice from Masami Hiramatsu and modified
my tests. I also added some helper functions to ftracetests as well.
I split the one function graph test into two. One to just test the
filtering of the function graph and another to test with stack tracer.
Steven Rostedt (Red
On Mon, 2014-11-03 at 17:14 +, Lee Jones wrote:
>On Fri, 31 Oct 2014, gyun...@gmail.com wrote:
> Code looks fine, but what are its dependencies. I'm assuming nothing;
> however, did Mark say that something depends on it?
That would be REGULATOR_SKY81452. That is currently dangling (since
* Heikki Krogerus [141017 07:43]:
> Provide complete association for the phy and it's user
> (musb) with the new phy lookup method.
>
> Signed-off-by: Heikki Krogerus
Kishon, this looks OK for you to queue with other PHY patches:
Acked-by: Tony Lindgren
> ---
>
On Mon, Nov 03, 2014 at 11:33:23AM -0800, Andy Lutomirski wrote:
> On 11/02/2014 07:07 PM, Kweh Hock Leong wrote:
> > From: "Kweh, Hock Leong"
> >
> >
> > Hi Guys,
> >
> > This patchset is created on top of "efi: Capsule update support" patch:
> >
On 11/03/2014 04:01 PM, Peter Hurley wrote:
> On 11/03/2014 11:05 AM, Johannes Thumshirn wrote:
>> * Enable the handling of UART core's automatic flow control feature.
>> When AFE is active disable generation of modem status IRQs.
>
> So HUPCL doesn't work when CRTSCTS is set?
Sorry, I meant
Hi oops.kernel.org folks,
I'm wanting to collect information on FW/BIOS bugs, and I figured that
we could use the oops.kernel.org infrastructure to do this.
Now, I'd prefer to not use the regular BUG/WARN because it might confuse
users and the stacktrace is entirely pointless -- we know were/why
On 3 November 2014 08:34, Geert Uytterhoeven wrote:
> Add a device node for the System Controller, with subnodes that
> represent the hardware power area hierarchy.
> Hook up all devices to their respective PM domains.
>
> Add a minimal device node for the Coresight-ETM hardware block, and hook
>
On Fri, 2014-10-10 at 17:09 +0300, Dmitry Kasatkin wrote:
> Define configuration option to load X509 certificate into the
> IMA trusted kernel keyring. It implements ima_load_x509() hook
> to load X509 certificate into the .ima trusted kernel keyring
> from root filesystem.
>
> Changes in v2:
>
On Mon, Nov 03, 2014 at 12:42:57PM -0800, Stephanie Wallick wrote:
> --- /dev/null
> +++ b/drivers/staging/mausb/TODO
> @@ -0,0 +1,14 @@
> +TODO:
> + - checkpatch.pl cleanups
Is this still true?
And why does this need to be a staging driver? What's wrong with making
it a "real" driver now?
On Mon, Nov 03, 2014 at 12:42:57PM -0800, Stephanie Wallick wrote:
> --- /dev/null
> +++ b/drivers/staging/mausb/drivers/Makefile
> @@ -0,0 +1,20 @@
> +#MY_CFLAGS =-g -O0 -DEBUG_OUTPUT
Please remove that line, it's not ever to be used.
--
To unsubscribe from this list: send the line
On Mon, Nov 03, 2014 at 12:42:48PM -0800, Stephanie Wallick wrote:
> +EXPORT_SYMBOL(mausb_register_ms_driver);
EXPORT_SYMBOL_GPL()? I have to ask...
> +static int mausb_hcd_init(void)
> +{
> + int ret;
> +
> + /* register HCD driver */
> + ret = platform_driver_register(_driver);
On 11/03/2014 05:35 AM, Peter Zijlstra wrote:
On Wed, Oct 29, 2014 at 04:19:09PM -0400, Waiman Long wrote:
arch/x86/include/asm/pvqspinlock.h| 411 +
I do wonder why all this needs to live in x86..
I haven't looked into the para-virtualization code in
On Mon, Nov 03, 2014 at 12:42:48PM -0800, Stephanie Wallick wrote:
> +#define DEBUG
I doubt you want this in the driver enabled by default :(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Suravee Suthikulpanit
ARM GICv2m specification extends GICv2 to support MSI(-X) with
a new set of register frame. This patch introduces support for
the non-secure GICv2m register frame. Currently, GICV2m is available
in certain version of GIC-400.
The patch introduces a new property in
From: Suravee Suthikulpanit
Add a helper function to set irq type in parent irq domain.
Signed-off-by: Suravee Suthikulpanit
---
include/linux/irq.h | 1 +
kernel/irq/chip.c | 10 ++
2 files changed, 11 insertions(+)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index
From: Suravee Suthikulpanit
This patch set introduces support for MSI(-X) in GICv2m specification,
which is implemented in some variation of GIC400.
This patch adopt the new hierarchy irq domain, and is rebased from:
Git tree :
Em Thu, Oct 30, 2014 at 04:09:41PM +0200, Adrian Hunter escreveu:
> Here are the thread stack patches again. Please let me
> know if you want more explanation.
>
> Changes:
>
> perf tools: Add a thread stack for synthesizing call chains
> Added some error returns
>
Reported by Dan Carpenter:
drivers/hid/hid-logitech-hidpp.c:359 hidpp_root_get_protocol_version() warn:
should this return really be negated?
drivers/hid/hid-logitech-hidpp.c:398 hidpp_devicenametype_get_count() warn:
should this return really be negated?
drivers/hid/hid-logitech-hidpp.c:417
- remove the constant '1'
- when the device is not connected, the protocol error
HIDPP_ERROR_RESOURCE_ERROR is raised. We should not warn the user about
it because it is somewhat expected as an answer when we check if the
device is connected.
Signed-off-by: Benjamin Tissoires
---
Changes
Linus,
On Fri, Oct 31, 2014 at 1:49 AM, Linus Walleij wrote:
> On Tue, Oct 28, 2014 at 9:57 PM, Doug Anderson wrote:
>> The pinctrl bindings / API allow you to specify that:
>> - a pin should be an output
>> - a pin should have its input path enabled / disabled
>>
>> ...but they don't allow you
On Sat, Nov 01, 2014 at 11:15:54PM -0400, Johannes Weiner wrote:
> Memory cgroups used to have 5 per-page pointers. To allow users to
> disable that amount of overhead during runtime, those pointers were
> allocated in a separate array, with a translation layer between them
> and struct page.
>
Em Mon, 03 Nov 2014 21:54:53 +0100
Beniamino Galvani escreveu:
> On Mon, Nov 03, 2014 at 11:14:10AM -0200, Mauro Carvalho Chehab wrote:
> > Em Sun, 12 Oct 2014 22:01:53 +0200
> > Beniamino Galvani escreveu:
> >
> > > Amlogic Meson SoCs include a infrared remote control receiver that can
> > >
On 3 November 2014 08:34, Geert Uytterhoeven wrote:
> Hi Rafael, Simon, Magnus,
>
> This patch series enables DT support for PM domains on Renesas R-Mobile SoCs.
>
> Currently it's limited to R-Mobile A1 (r8a7740), but given the similarity of
> the SYSC System-Controller on the various
Signed-off-by: Vladimir Davydov
---
mm/slab.c | 30 ++
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
index a9eb49f40c0a..178a3b733a50 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -3521,6 +3521,18 @@ void
On 11/03/2014 11:05 AM, Johannes Thumshirn wrote:
> * Enable the handling of UART core's automatic flow control feature.
> When AFE is active disable generation of modem status IRQs.
So HUPCL doesn't work when CRTSCTS is set?
Is this because there's actually a problem with the IP core that
Currently, new slabs are charged to the memory cgroup that owns the
cache (kmem_cache->memcg_params->memcg), but I'm going to decouple kmem
caches from memory cgroups so I make them charged to the current cgroup.
Signed-off-by: Vladimir Davydov
---
include/linux/memcontrol.h |5 -
Currently, we try to destroy per memcg kmem caches on css offline. Since
a cache can contain active objects when the memory cgroup is removed, we
can't destroy all caches immediately and therefore should introduce
asynchronous destruction for this scheme to work properly. However, this
requires a
This will allow new kmem active cgroups to reuse the id and therefore
the caches used by the dead memory cgroup.
Signed-off-by: Vladimir Davydov
---
mm/memcontrol.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index
Basically, we substitute the reference to the owner memory cgroup in
memcg_cache_params with the index in the memcg_caches array. This
decouples kmem cache from the memcg it was created for and will allow to
reuse it for another cgroup after css offline.
Signed-off-by: Vladimir Davydov
---
We use the same set of checks in both memcg_kmem_newpage_charge and
memcg_kmem_get_cache, and I need it in yet another function, which will
be introduced by one of the following patches. So let's introduce a
helper function for it.
Signed-off-by: Vladimir Davydov
---
include/linux/memcontrol.h
No need in these helpers any more. We can do the stuff in
memcg_create_kmem_cache and kmem_cache_destroy.
Signed-off-by: Vladimir Davydov
---
include/linux/memcontrol.h |2 -
include/linux/slab.h |3 +-
mm/memcontrol.c| 115 ++--
Hi,
Currently, each kmem active memory cgroup has its own set of kmem
caches. The caches are only used by the memory cgroup they were created
for, so when the cgroup is taken offline they must be destroyed.
However, we can't easily destroy all the caches on css offline, because
they still may
Since we now reuse per cgroup kmem caches, the slab we allocate an
object from may be accounted to a dead memory cgroup. If we leave such a
slab accounted to a dead cgroup, we risk pinning the cgroup forever, so
we introduce a new function, memcg_kmem_recharge_slab, which is to be
called in the
On Mon, Nov 03, 2014 at 11:14:10AM -0200, Mauro Carvalho Chehab wrote:
> Em Sun, 12 Oct 2014 22:01:53 +0200
> Beniamino Galvani escreveu:
>
> > Amlogic Meson SoCs include a infrared remote control receiver that can
> > operate in two modes: in "NEC" mode the hardware can decode frames
> > using
On 10/27/2014 01:49 PM, Thomas Gleixner wrote:
> Errm. Before user space can use the bounds table for the new mapping
> it needs to add the entries, right? So:
>
> CPU 0 CPU 1
>
> down_write(mm->bd_sem);
> mpx_pre_unmap();
>clear bounds directory entries
Adds various scripts for building, loading and unloading the MA USB
drivers and a utility that can be used for connecting and disconnecting
the host and device drivers.
Signed-off-by: Sean O. Stalley
Signed-off-by: Stephanie Wallick
---
.../staging/mausb/scripts/build_load_connect.sh| 69
This is where we implement USB 2.0 and 3.0 roothubs. From the host's
perspective,
hub state is set and tracked just like any other USB roothub. Likewise, requests
to the roothub appear to be handled like any other wired USB request.
Signed-off-by: Sean O. Stalley
Signed-off-by: Stephanie
This is where we create, store and handle endpoint and device structures
that are specific to the MA USB drivers. Each MA USB structure maps 1:1
with it's corresponding USB structure (e.g. there is one MA USB endpoint
per USB endpoint).
Signed-off-by: Sean O. Stalley
Signed-off-by: Stephanie
The Media Agnostic USB Specification outlines a number of managment
packet types for management and control functions. Each function is
initiated with a particular type of managment request packet and
completed with the corresponding management response packet. This
is where we fill the fields for
This is where we interface with the existing USB stack and implement the
functionality of a USB host controller driver. From the host's perspective,
we appear as just another USB host controller. However, instead of passing
traffic along a wired USB bus, the driver hands USB packets off for
This is where we implement the behavior of a USB device controller for
the MA USB device-side driver. The MA UDC interfaces with a gadget driver
and appears to the driver as a regular UDC. However, instead of sending
USB packets over a wired USB bus, the MA UDC hands MA USB packets off to
a media
This is where we handle MA USB packets. The structure and types of MA USB
packets are defined in the MA USB specification. When an MA USB driver
receives a USB packet, it translates it into a MA USB packet (or packets
if urb exceeds maximum USB packet size). When an MA USB packet is received,
the
From: Jérôme Glisse
Motivation:
Heterogeneous memory management is intended to allow a device to transparently
access a process address space without having to lock pages of the process or
take references on them. In other word mirroring a process address space while
allowing the regular memory
The MA USB Specification outlines packet types and a protocol for
bulk and interrupt transfers. This is where we implement that protocol.
MA USB transfers are initiated by the host via a TransferRequest packet.
The host then either sends data to the device via subsequent
TransferRequest packets
Signed-off-by: Sean O. Stalley
Signed-off-by: Stephanie Wallick
---
drivers/staging/Kconfig| 2 ++
drivers/staging/Makefile | 1 +
drivers/staging/mausb/Kconfig | 16
drivers/staging/mausb/Makefile | 3 +++
Commit-ID: 87983c66bc02c9cd8e4a42e7924435145d52bb13
Gitweb: http://git.kernel.org/tip/87983c66bc02c9cd8e4a42e7924435145d52bb13
Author: Andy Lutomirski
AuthorDate: Wed, 29 Oct 2014 14:33:45 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 3 Nov 2014 21:44:57 +0100
x86_64, vsyscall:
From: Jérôme Glisse
Page table is a common structure format most notably use by cpu mmu. The
arch depend page table code has strong tie to the architecture which makes
it unsuitable to be use by other non arch specific code.
This patch implement a generic and arch independent page table. It is
Media Agnostic (MA) USB enables the USB protocol to be used over a wide
range of physical media. MA USB is a relatively new protocol and is
currently unsupported in the Linux kernel. This patch set adds the
following drivers with the following capabilities:
1) MA USB Host:
- provides
Commit-ID: 1ad83c858c7d4ea210429142c99a1548e6715a35
Gitweb: http://git.kernel.org/tip/1ad83c858c7d4ea210429142c99a1548e6715a35
Author: Andy Lutomirski
AuthorDate: Wed, 29 Oct 2014 14:33:47 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 3 Nov 2014 21:44:57 +0100
x86_64,vsyscall:
Commit-ID: 95c46b56922409ed8838b3b420b11cfebb8c6c88
Gitweb: http://git.kernel.org/tip/95c46b56922409ed8838b3b420b11cfebb8c6c88
Author: Andy Lutomirski
AuthorDate: Wed, 29 Oct 2014 14:33:46 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 3 Nov 2014 21:44:57 +0100
x86_64, vsyscall:
This is where we handle media specific packets and transport. The MS driver
interfaces with a media agnostic (MA) driver via a series of transfer pairs.
Transfer pairs consist of a set of functions to pass MA USB packets back
and forth between MA and MS drivers. There is one transfer pair per
From: Jérôme Glisse
The event information will be usefull for new user of mmu_notifier API.
The event argument differentiate between a vma disappearing, a page
being write protected or simply a page being unmaped. This allow new
user to take different path for different event for instance on
From: Jérôme Glisse
The mmu_notifier_invalidate_range_start() and
mmu_notifier_invalidate_range_end()
can be considered as forming an "atomic" section for the cpu page table update
point of view. Between this two function the cpu page table content is
unreliable
for the address range being
From: Jérôme Glisse
This is a dummy driver which full fill two purposes :
- showcase the hmm api and gives references on how to use it.
- provide an extensive user space api to stress test hmm.
This is a particularly dangerous module as it allow to access a
mirror of a process address space
Andrew i received no feedback since last time i sent this patchset, so i
would really like to have it merge for next kernel. While right now there
is no kernel driver that leverage this code, the hardware is coming and we
still have a long way to go before we have all the features needed. Right
Hi,
On Mon, Nov 03, 2014 at 10:51:08AM -0800, Guenter Roeck wrote:
> On Mon, Nov 03, 2014 at 12:06:02PM -0600, Felipe Balbi wrote:
> > On Mon, Nov 03, 2014 at 10:01:50AM -0800, Guenter Roeck wrote:
> > > On Mon, Nov 03, 2014 at 10:32:27AM -0600, Felipe Balbi wrote:
> > > > From: George Cherian
>
On Mon, Nov 3, 2014 at 12:41 PM, Thomas Gleixner wrote:
> On Mon, 3 Nov 2014, Andy Lutomirski wrote:
>> On Mon, Nov 3, 2014 at 12:31 PM, Thomas Gleixner wrote:
>> > On Wed, 29 Oct 2014, Andy Lutomirski wrote:
>> >
>> >> vsyscall_64.c is just vsyscall emulation. Tidy it up accordingly.
>> >>
>>
On Mon, 3 Nov 2014, Andy Lutomirski wrote:
> On Mon, Nov 3, 2014 at 12:31 PM, Thomas Gleixner wrote:
> > On Wed, 29 Oct 2014, Andy Lutomirski wrote:
> >
> >> vsyscall_64.c is just vsyscall emulation. Tidy it up accordingly.
> >>
> >> If my comment editing offends anyone, let me know and I can
On Mon, Nov 3, 2014 at 3:32 PM, Dan Carpenter wrote:
> On Mon, Nov 03, 2014 at 02:50:52PM -0500, Benjamin Tissoires wrote:
>> @@ -524,8 +541,11 @@ static int hidpp_touchpad_get_raw_info(struct
>> hidpp_device *hidpp,
>> ret = hidpp_send_fap_command_sync(hidpp, feature_index,
>>
Hi,
On Mon, Nov 03, 2014 at 08:42:47PM +0200, Mika Westerberg wrote:
> > > > > > > > I think adding the module exit + allowing this driver to be a
> > > > > > > > module
> > > > > > > > would be a good approach. Then we don't need to force generic
> > > > > > > > x86 kernel
> > > > > > > >
Add GPO0 and GPO1 (General Purpose Outputs) controls to mixer.
These can be used on some cards to control amplifier mute (seen in ES1868
datasheet) or additional onboard chips such as QX2130 QXpander processor.
These GPOs are present on ES1868, ES1869, ES1887 and ES1888 chips.
Tested on ES1868
From: Sudip Mukherjee
Date: Mon, 3 Nov 2014 17:42:29 +0530
> this is check for dev is unnecessary, as we are already checking dev
> after allocating it via alloc_netdev, and jumping to label: out
> if it is NULL.
>
> Signed-off-by: Sudip Mukherjee
Applied, thanks.
--
To unsubscribe from this
On Mon, Nov 3, 2014 at 12:31 PM, Thomas Gleixner wrote:
> On Wed, 29 Oct 2014, Andy Lutomirski wrote:
>
>> vsyscall_64.c is just vsyscall emulation. Tidy it up accordingly.
>>
>> If my comment editing offends anyone, let me know and I can fix it.
>>
>> Reviewed-by: Josh Triplett
>>
When a subdriver is rmmod-ed then re-insmod-ed, the hid device is not
destroyed as it is owned by the transport layer.
So when we re-probed the device, the hid device is assumed to be already
claimed, and can lead to page faults if hid-core tries to forward the
emitted data to the to-be-created
On Mon, Nov 03, 2014 at 02:50:52PM -0500, Benjamin Tissoires wrote:
> @@ -524,8 +541,11 @@ static int hidpp_touchpad_get_raw_info(struct
> hidpp_device *hidpp,
> ret = hidpp_send_fap_command_sync(hidpp, feature_index,
> CMD_TOUCHPAD_GET_RAW_INFO, NULL, 0, );
>
> - if
On Wed, 29 Oct 2014, Andy Lutomirski wrote:
> vsyscall_64.c is just vsyscall emulation. Tidy it up accordingly.
>
> If my comment editing offends anyone, let me know and I can fix it.
>
> Reviewed-by: Josh Triplett
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/kernel/vsyscall_64.c | 51
On Mon, Nov 3, 2014 at 12:24 PM, Johannes Berg
wrote:
> On Mon, 2014-11-03 at 12:21 -0800, Luis R. Rodriguez wrote:
>
>> OK I'll prefix the stuff we copy over with something else then, BPAUTO.
>
> I still want to keep CPTCFG though :)
:*( OK I'll give it a shot...
Luis
--
To unsubscribe from
On Mon, 3 Nov 2014 19:33:45 +0100
Robert Richter wrote:
> On 03.11.14 10:16:51, Stephen Hemminger wrote:
> > On Fri, 31 Oct 2014 22:44:11 +0530
> > Sunil Kovvuri wrote:
> >
> > > On Fri, Oct 31, 2014 at 8:24 AM, Stephen Hemminger
> > > wrote:
> > > > On Thu, 30 Oct 2014 17:54:34 +0100
> > > >
On Mon, 2014-11-03 at 12:21 -0800, Luis R. Rodriguez wrote:
> OK I'll prefix the stuff we copy over with something else then, BPAUTO.
I still want to keep CPTCFG though :)
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Nov 3, 2014 at 12:20 PM, Johannes Berg
wrote:
> On Mon, 2014-11-03 at 11:56 -0800, Luis R. Rodriguez wrote:
>
>> With my current code I end up with on a package (not integration):
>>
>> config BACKPORT_BUILD_AVERAGE
>> bool
>> depends on !AVERAGE
>> default y if
On Mon, 2014-11-03 at 11:56 -0800, Luis R. Rodriguez wrote:
> With my current code I end up with on a package (not integration):
>
> config BACKPORT_BUILD_AVERAGE
> bool
> depends on !AVERAGE
> default y if BACKPORT_USERSEL_BUILD_ALL
> default y if
On Mon, 3 Nov 2014, Arnd Bergmann wrote:
> On Saturday 01 November 2014 18:03:47 Kevin Cernekee wrote:
> > V2->V3:
> >
> > - Move updated irq_reg_{readl,writel} functions back into
> >so they can be called by irqchip drivers
> >
> > - Add gc->reg_{readl,writel} function pointers so that
When the TIF_SINGLESTEP tracee dequeues a signal, handle_signal()
clears TIF_FORCED_TF and X86_EFLAGS_TF but leaves TIF_SINGLESTEP set.
If the tracer does PTRACE_SINGLESTEP again, enable_single_step() sets
X86_EFLAGS_TF but not TIF_FORCED_TF. This means that the subsequent
PTRACE_CONT doesn't not
Hello,
This is the very old bug initially reported by Evan in 2010, see
https://bugzilla.kernel.org/show_bug.cgi?id=16061
Somehow we forgot to fix it and now Pedro reports it again.
>From the changelog:
Note: in the longer term we should probably change setup_sigcontext()
to use
From: Johannes Weiner
Date: Mon, 3 Nov 2014 13:27:40 -0500
> Remove unneeded !CONFIG_MEMCG memcg bad_page() dummies as well.
>
> Signed-off-by: Johannes Weiner
Acked-by: David S. Miller
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sun, 2 Nov 2014, Meelis Roos wrote:
Between 3.17 and 3.18-rc2, qla2xxx is broken on my sparc64 machines. It fails
to boot (hangs in firmware rings init).
This is the result of bisect:
98aee70d19a7e3203649fa2078464e4f402a0ad8 is the first bad commit
commit
From: Herbert Xu
Date: Mon, 3 Nov 2014 13:37:51 +0800
> On Mon, Nov 03, 2014 at 12:45:03AM +, Al Viro wrote:
>>
>> Note, BTW, that there's a damn good reason to convert the socket side of
>> things to iov_iter - as it is, ->splice_write() there is basically done with
>> page-by-page mapping
On 11/3/2014 8:10 AM, Marc Zyngier wrote:
On 03/11/14 09:50, Marc Zyngier wrote:
@@ -843,10 +847,14 @@ static int gic_irq_domain_alloc(struct irq_domain
*domain, unsigned int virq,
unsigned int type = IRQ_TYPE_NONE;
struct of_phandle_args *irq_data = arg;
- ret =
On 11/3/2014 3:50 AM, Marc Zyngier wrote:
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
>index a99c211..4069eb3 100644
>--- a/drivers/irqchip/irq-gic.c
>+++ b/drivers/irqchip/irq-gic.c
>@@ -46,6 +46,7 @@
> #include
>
> #include "irq-gic-common.h"
>+#include
On Mon, Nov 3, 2014 at 11:40 AM, Johannes Berg
wrote:
> On Mon, 2014-11-03 at 11:30 -0800, Luis R. Rodriguez wrote:
>> On Fri, Oct 31, 2014 at 1:33 PM, Luis R. Rodriguez wrote:
>> >> That also makes me think of something else - we currently use BACKPORT_
>> >> as a prefix for some of the other
On 10/31/2014 4:40 AM, Thomas Gleixner wrote:
On Fri, 31 Oct 2014, suravee.suthikulpa...@amd.com wrote:
+/*
+ * alloc_msi_irq - Allocate MSIs from available MSI bitmap.
+ * @data: Pointer to v2m_data
+ * @nvec: Number of interrupts to allocate
+ * @irq: Pointer to the allocated irq
+ *
+ *
On Tue, 21 Oct 2014, Shuah Khan wrote:
> Andrew/Ingo/Thomas,
>
> You are all on the signed-off list for rt-tester. I have been poking
> around the source tree looking for existing test and came across rt-tester.
>
> What are your thoughts on rt-tester suitability to reside under
>
On Mon, 3 Nov 2014 11:18:36 +0200
Cristian Stoica wrote:
> On 10/31/2014 08:22 PM, Kim Phillips wrote:
> > On Fri, 31 Oct 2014 18:57:33 +0200
> > Cristian Stoica wrote:
> >
> > If this issue was brought up by h/w, the appropriate new error codes
> > should be being introduced.
>
> If you have
Reported by Dan Carpenter:
drivers/hid/hid-logitech-hidpp.c:359 hidpp_root_get_protocol_version() warn:
should this return really be negated?
drivers/hid/hid-logitech-hidpp.c:398 hidpp_devicenametype_get_count() warn:
should this return really be negated?
drivers/hid/hid-logitech-hidpp.c:417
- remove the constant '1'
- when the device is not connected, the protocol error
HIDPP_ERROR_RESOURCE_ERROR is raised. We should not warn the user about
it because it is somewhat expected as an answer when we check if the
device is connected.
Signed-off-by: Benjamin Tissoires
---
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
> Add safe function to check if Numachip is detected, to be used elsewhere.
I cannot find a use case for this. I guess this is a left over of the
earlier 2G change, right?
Thanks,
tglx
--
To unsubscribe from this list: send the line
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
> I just got a window to test this, and it reliably addresses the boot-time core
> onlining race that we've seen occasionally on a 2000-core customer system.
> Splendid work, Thomas.
>
> Tested-by: Daniel J Blueman
Well, you forgot to read my follow
> > However, researching the net, users currently interpret iowait entirely as
> > blkio wait. Furthermore, io_schedule() calls delayacct_blkio_{start|end}()
> > which
> > worked fine for my tests with I2C but might show that iowait was really
> > meant as
> > blkiowait? So, should other
On Mon, 2014-11-03 at 11:30 -0800, Luis R. Rodriguez wrote:
> On Fri, Oct 31, 2014 at 1:33 PM, Luis R. Rodriguez wrote:
> >> That also makes me think of something else - we currently use BACKPORT_
> >> as a prefix for some of the other stuff under compat/Kconfig, and in
> >> fact rename some
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
> On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
> entry creation time by 16x. Large is defined as 64GB or more memory.
This changelog sucks.
It neither tells which sysfs entries are meant nor does it explain
what the actual
On 11/02/2014 07:07 PM, Kweh Hock Leong wrote:
> From: "Kweh, Hock Leong"
>
>
> Hi Guys,
>
> This patchset is created on top of "efi: Capsule update support" patch:
> http://permalink.gmane.org/gmane.linux.kernel.efi/4837
>
> It leverages the request_firmware_nowait() to expose the user
This patch is concerned with migrating the time variables for the s390
network driver. The changes handle the y2038 problem where timespec will
overflow in the year 2038. timespec was replaced by unsigned long and
all time variables get their values from the jiffies global variable.
This was done
On Fri, Oct 31, 2014 at 1:33 PM, Luis R. Rodriguez wrote:
>> That also makes me think of something else - we currently use BACKPORT_
>> as a prefix for some of the other stuff under compat/Kconfig, and in
>> fact rename some things (like CONFIG_BACKPORT_AVERAGE) so maybe also
>> using
301 - 400 of 2138 matches
Mail list logo
