On Fri, Sep 05, 2014 at 11:10:13AM -0600, Jens Axboe wrote:
> On 09/05/2014 11:03 AM, Arne Wiebalck wrote:
> >
> > On Sep 5, 2014, at 6:41 PM, Peter Kieser
> > wrote:
> >
> >>
> >> On 2014-09-05 8:37 AM, Eddie Chapman wrote:
> >>> On 05/09/14 15:17, Jens Axboe wrote:
> (from oldest to
On Friday 05 September 2014 19:16:36 Peter Griffin wrote:
> On Fri, 05 Sep 2014, Arnd Bergmann wrote:
>
> > On Friday 05 September 2014 18:23:45 Peter Griffin wrote:
> > > +struct st_platform_priv {
> > > + struct clk *clks[USB_MAX_CLKS];
> > > + struct clk *clk48;
> > > +
On Fri, Sep 05, 2014 at 11:09:50AM -0700, Paul E. McKenney wrote:
> On Fri, Sep 05, 2014 at 08:16:48PM +1200, Michael Cree wrote:
> > On Thu, Sep 04, 2014 at 07:08:48PM -0700, H. Peter Anvin wrote:
> > > On 09/04/2014 05:59 PM, Peter Hurley wrote:
> > > > I have no idea how prevalent the ev56 is
On Fri, Sep 05, 2014 at 11:12:17AM -0700, Luis R. Rodriguez wrote:
> On Fri, Sep 5, 2014 at 10:49 AM, Tejun Heo wrote:
> > Hello,
> >
> > On Fri, Sep 05, 2014 at 09:44:05AM -0700, Dmitry Torokhov wrote:
> >> Which problem are we talking about here though? It does solve the slow
> >> device
> >>
Hi,
> > +static int st_wdog_remove(struct platform_device *pdev)
> > +{
> > + struct st_wdog *st_wdog = watchdog_get_drvdata(_wdog_dev);
> > +
> > + if (watchdog_active(_wdog_dev))
> > + st_wdog_stop(_wdog_dev);
> > +
> > + st_wdog_setup(st_wdog, WDT_DISABLE);
> > +
> > +
The patch was applied in our tree, but we have not issued a pull
request because other patches are still under discussion.
We might issue a pull request first.
Best,
Lennox
2014-09-05 22:00 GMT+08:00 Richard Weinberger :
> Am 05.09.2014 15:57, schrieb Guenter Roeck:
>> On 09/05/2014 02:32 AM,
2014-09-05 0:38 GMT+03:00 Greg KH :
> On Thu, Sep 04, 2014 at 11:58:36PM +0300, Andreea Bernat wrote:
>> Hello,
>>
>> I cloned this:
>> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
>>
>> and after moved to staging-next branch, but in both cases, in
>> those files I don't find
Dear Bjorn Helgaas,
On Fri, 5 Sep 2014 11:41:22 -0600, Bjorn Helgaas wrote:
> This fix looks right to me. I added a stable tag as follows. Thomas
> and/or Jason, and you ack this?
Hum, I think I would actually prefer something like:
if (DT_FLAGS_TO_TYPE(flags) == DT_TYPE_IO)
On Thu, Sep 04, 2014 at 12:59:39PM -0500, Christoph Lameter wrote:
> On Fri, 5 Sep 2014, Tejun Heo wrote:
>
> > I suppose this should go through percpu/for-3.18-consistent-ops? Can
> > we please cc irq folks and get acks?
>
> Russell and Nicolas were cced. This is arm specific.
Sorry, but I
Hi Arnd,
On Fri, 05 Sep 2014, Arnd Bergmann wrote:
> On Friday 05 September 2014 18:23:45 Peter Griffin wrote:
> > +struct st_platform_priv {
> > + struct clk *clks[USB_MAX_CLKS];
> > + struct clk *clk48;
> > + struct reset_control *rst;
> > + struct reset_control *pwr;
>
On Fri, Sep 5, 2014 at 10:49 AM, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 05, 2014 at 09:44:05AM -0700, Dmitry Torokhov wrote:
>> Which problem are we talking about here though? It does solve the slow device
>> stalling the rest if the kernel booting (non-module case) for me.
>
> The other one.
On Fri, Sep 5, 2014 at 11:00 AM, Tejun Heo wrote:
> On Fri, Sep 05, 2014 at 09:31:50AM -0700, Cong Wang wrote:
>> On Fri, Sep 5, 2014 at 7:08 AM, Tejun Heo wrote:
>> >> + /* It might not be safe to check TIF_MEMDIE for pm freeze. */
>> >
>> > This is just another representation of the
On Fri, Sep 05, 2014 at 08:16:48PM +1200, Michael Cree wrote:
> On Thu, Sep 04, 2014 at 07:08:48PM -0700, H. Peter Anvin wrote:
> > On 09/04/2014 05:59 PM, Peter Hurley wrote:
> > > I have no idea how prevalent the ev56 is compared to the ev5.
> > > Still we're talking about a chip that came out
On Sat, Sep 06, 2014 at 02:49:25AM +0900, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 05, 2014 at 09:44:05AM -0700, Dmitry Torokhov wrote:
> > Which problem are we talking about here though? It does solve the slow
> > device
> > stalling the rest if the kernel booting (non-module case) for me.
>
On Fri, 5 Sep 2014, Daniel Thompson wrote:
> On 04/09/14 19:57, Nicolas Pitre wrote:
> > On Thu, 4 Sep 2014, Daniel Thompson wrote:
> >
> >> +@ svc_exit_via_fiq - similar to svc_exit but switches to FIQ mode before
> >> exit
> >> +@
> >> +@ This macro acts in a similar manner to svc_exit but
On 09/05/2014 02:05 AM, Mark Rutland wrote:
> On Wed, Sep 03, 2014 at 05:59:58PM +0100, Florian Fainelli wrote:
>> On 09/03/2014 05:43 AM, Mark Rutland wrote:
>>> On Wed, Sep 03, 2014 at 01:13:02PM +0100, Thomas Gleixner wrote:
You forgot to CC the device tree dudes. We want an ack on the
On Fri, Sep 05, 2014 at 09:31:50AM -0700, Cong Wang wrote:
> On Fri, Sep 5, 2014 at 7:08 AM, Tejun Heo wrote:
> >> + /* It might not be safe to check TIF_MEMDIE for pm freeze. */
> >
> > This is just another representation of the following code which isn't
> > particularly useful. Wouldn't
On Thu, Sep 04, 2014 at 12:01:19PM +0530, Vivek Gautam wrote:
> > Don't we have phy_power_on()
> > for that ? It looks like you could just as well do this from
> > phy_power_on() ?
>
> No, unfortunately keeping these calibration settings in phy_power_on()
> doesn't help, since we need to do this
On Friday 05 September 2014 18:23:45 Peter Griffin wrote:
> +struct st_platform_priv {
> + struct clk *clks[USB_MAX_CLKS];
> + struct clk *clk48;
> + struct reset_control *rst;
> + struct reset_control *pwr;
> + struct phy *phy;
> +};
Any reason why this is in a
On Friday 05 September 2014 13:39:42 Murali Karicheri wrote:
> +
> /* enable RC mode in devcfg */
> val = readl(reg_p);
> - val &= ~PCIE_MODE_MASK;
> - val |= PCIE_RC_MODE;
> + port_id <<= 1;
> + val &= ~(PCIE_MODE_MASK << port_id);
> + val |=
On Fri, Sep 05, 2014 at 01:21:00PM -0400, Murali Karicheri wrote:
> Keystone K2E EVM uses Marvel 0x9182 controller. This requires support
> for the ID in the ahci driver.
>
> Signed-off-by: Murali Karicheri
Applied to libata/for-3.17-fixes w/ stable cc'd.
Thanks.
--
tejun
--
To unsubscribe
On Friday 05 September 2014 11:41:22 Bjorn Helgaas wrote:
> On Fri, Aug 08, 2014 at 05:34:05PM +0200, Geert Uytterhoeven wrote:
> > drivers/pci/host/pci-mvebu.c: In function 'mvebu_get_tgt_attr':
> > drivers/pci/host/pci-mvebu.c:887:39: warning: 'rtype' may be used
> > uninitialized in this
On Thu, Sep 04, 2014 at 12:40:06PM +0200, Rasmus Villemoes wrote:
> The C operator <= defines a perfectly fine total ordering on the set
> of values representable in a long. However, unlike its namesake in the
> integers, it is not translation invariant, meaning that we do not have
> "b <= c" iff
Hello,
On Fri, Sep 05, 2014 at 09:44:05AM -0700, Dmitry Torokhov wrote:
> Which problem are we talking about here though? It does solve the slow device
> stalling the rest if the kernel booting (non-module case) for me.
The other one. The one with timeout. Neither cxgb4 or pata_marvell
has
James and Jens:
I got a WARNING when unbinding the sd driver from a USB flash drive and
then binding it back again. Here's where the flash drive gets probed
initially:
[ 143.300886] usb-storage 4-8:1.0: usb_probe_interface
[ 143.300911] usb-storage 4-8:1.0: usb_probe_interface - got id
[
On Fri, Aug 08, 2014 at 05:34:05PM +0200, Geert Uytterhoeven wrote:
> drivers/pci/host/pci-mvebu.c: In function 'mvebu_get_tgt_attr':
> drivers/pci/host/pci-mvebu.c:887:39: warning: 'rtype' may be used
> uninitialized in this function [-Wmaybe-uninitialized]
>if (slot == PCI_SLOT(devfn) &&
K2E SoC has two PCI ports. The SATA controller is connected to second
PCI port (port 1). This patch enhances the driver to support multiple
ports.
Update the DT Documentation for the new attribute, ti,pcie-port and
remove the note for bootargs as this is no longer needed.
Signed-off-by: Murali
On Thu, Sep 04, 2014 at 08:32:18AM +0200, Robert Baldyga wrote:
> This patch introduces virtual endpoint address mapping. It separates
> function logic form physical endpoint addresses making it more hardware
> independent.
>
> Following modifications changes user space API, so to enable them
If the online CPU check in gic_set_affinity() fails, return a proper
errno value instead of -1.
Signed-off-by: Andrew Bresticker
---
No changes from v1.
---
drivers/irqchip/irq-mips-gic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-mips-gic.c
Move GIC irqchip support to drivers/irqchip/ and rename the Kconfig
option from IRQ_GIC to MIPS_GIC to avoid confusion with the ARM GIC.
Signed-off-by: Andrew Bresticker
---
New for v2.
Should irq_cpu.c get moved over too?
---
arch/mips/Kconfig| 10
When DT-based probing is used for the GIC and the GIC is also used
for IPIs (i.e. MIPS_GIC_IPI=y), set up the last 2 * NR_CPUs GIC
interrupts as the reschedule and call IPIs.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- removed open-coding of irq_set_type
---
On Fri, Sep 05, 2014 at 12:59:49PM +0200, Oleg Nesterov wrote:
> On 09/04, Luis R. Rodriguez wrote:
> >
> > From: "Luis R. Rodriguez"
> >
> > The new umh kill option has allowed kthreads to receive
> > kill signals but they are generally accepting all sources
> > of kill signals
>
> And I think
On Fri, Sep 05, 2014 at 04:48:11PM +, Serge Hallyn wrote:
> Quoting Seth Forshee (seth.fors...@canonical.com):
> > Update fuse to support mounts from within user namespaces. This
> > is mostly a matter of translating uids and gids into the
> > namespace of the process reading requests before
On 09/05/2014 07:21 PM, Alexei Starovoitov wrote:
...
imo it's cleaner to convert to bool unconditionally instead
of annotating things everywhere.
Will do, fine as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Currently interrupt vectors 2 and 5 are left disabled on secondary CPUs.
Since systems using CPS must also have a GIC, which is responsible for
routing all external interrupts and can map them to any hardware interrupt
vector, enable the remaining vectors. The two software interrupt vectors
are
Implement an irq_set_type callback for the GIC which is used to set
the polarity and trigger type of GIC interrupts.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- fixed polarity setting for edge-triggered interrupts
---
arch/mips/include/asm/gic.h| 9 +++
On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
> From: Dave Young
>
> X86 will pass setup_data region while necessary, these regions could be
> overwitten by kernel due to kaslr.
>
> Thus iterate and add setup regions to mem_avoid[] in this patch.
> Up to now there isn't a official
The GIC driver will use it to create the GIC-to-CPU interrupt mappings.
Signed-off-by: Andrew Bresticker
---
New for v2.
---
arch/mips/include/asm/irq_cpu.h | 2 ++
arch/mips/kernel/irq_cpu.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git
Define a generic MIPS_GIC_IRQ_BASE which is suitable for Malta and
the upcoming Danube board in . Since Sead-3 is
different and uses a MIPS_GIC_IRQ_BASE equal to the CPU IRQ base (0),
define its MIPS_GIC_IRQ_BASE in .
Signed-off-by: Andrew Bresticker
---
No changes from v1.
---
Add the vendor prefix "mti" for MIPS Technologies, Inc.
Signed-off-by: Andrew Bresticker
---
New for v2.
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
Implement a default gic_irq_ack() and gic_finish_irq(). These are
suitable for handling IPIs on Malta and the upcoming Danube board.
Signed-off-by: Andrew Bresticker
---
No changes from v1.
---
drivers/irqchip/irq-mips-gic.c | 14 ++
1 file changed, 14 insertions(+)
diff --git
Add device-tree support for the MIPS GIC. With DT, no per-platform
static device interrupt mapping is supplied and instead all device
interrupts are specified through the DT. The GIC-to-CPU interrupts
must also be specified in the DT.
Platforms using DT-based probing of the GIC need only supply
On Fri, Sep 5, 2014 at 9:59 AM, Mark Rutland wrote:
>
> As you point out below, the race on event->ctx is the fundamental issue. That
> is what results in decrementing the refcount twice (once on a stale event->ctx
> pointer).
So quite frankly, the whole perf_pmu_migrate_context() thing looks
The Global Interrupt Controller (GIC) present on certain MIPS systems
can be used to route external interrupts to individual VPEs and CPU
interrupt vectors. It also supports a timer and software-generated
interrupts.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- moved from mips/ to
This series add support for mapping and routing GIC interrupts through
the device-tree, which will be used on the upcoming interAptiv-based
Danube SoC.
- Patches 1 and 2 provide improvements to the CPU interrupt controller
when used with DT.
- Patch 3 exports the MIPS CPU IRQ domain so that the
The MIPS GIC supports 7 local interrupts, 5 of which are just core
interrupts which can be re-routed through the GIC. This patch adds
support for mapping and handling the remaining two: the GIC timer
and watchdog. GIC interrupts from 0 to GIC_NUM_INTRS are still the
shared external interrupts
Instead of using GIC interrupt 0 for the timer (which was not even
handled correctly by the GIC irqchip code and could conflict with an
actual external interrupt), use the designated local interrupt for
the GIC timer.
Also, since the timer is a per-CPU interrupt, initialize it with
When mapping an interrupt in the CPU IRQ domain, set the vint handler
for that interrupt if the CPU uses vectored interrupt handling.
Signed-off-by: Andrew Bresticker
---
No changes from v1.
---
arch/mips/kernel/irq_cpu.c | 4
1 file changed, 4 insertions(+)
diff --git
Now that the GIC driver properly supports local interrupts, extend
the static interrupt mapping to include the GIC timer and watchdog
and fix up the GIC interrupt setup and handling so that the local
interrupts are properly handled. Note that ipi_map is also renamed
to gic_irq_map since it is now
For platforms which boot with device-tree and use the MIPS CPU interrupt
controller binding, a generic plat_irq_dispatch() can be used since all
CPU interrupts should be mapped through the CPU IRQ domain. Implement a
plat_irq_dispatch() which simply handles the highest pending interrupt.
On Fri, Sep 05, 2014 at 01:24:17PM +0200, Oleg Nesterov wrote:
> On 09/04, Luis R. Rodriguez wrote:
> >
> > struct driver_private {
> > struct kobject kobj;
> > struct klist klist_devices;
> > struct klist_node knode_bus;
> > struct module_kobject *mkobj;
> > + struct
This patch adds the ehci-st.c and ohci-st.c files for the usb 2.0
& usb1.1 host controller drivers found on stih41x and stih4xx STMicroelectronics
SoC's into the STI arch section of the maintainers file.
Signed-off-by: Peter Griffin
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff
This patch adds the glue code required to ensure the on-chip OHCI
controller works on STi consumer electronics SoC's from STMicroelectronics.
It mainly manages the setting and enabling of the relevant clocks and manages
the reset / power signals to the IP block.
Signed-off-by: Peter Griffin
---
This patch documents the device tree bindings required for the
ehci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ehci-st.txt | 39 +++
1 file changed, 39 insertions(+)
create mode 100644
This patch adds the glue code required to ensure the on-chip EHCI
controller works on STi consumer electronics SoC's from STMicroelectronics.
It mainly manages the setting and enabling of the relevant clocks and manages
the reset / power signals to the IP block.
Signed-off-by: Peter Griffin
---
Hi,
As part of the RESEND I've rebased this series on top of 3.17-rc3. I believe all
feedback has been addressed.
The series was re-worked from v2 onwards to split out the ehci and ohci parts
into their own drivers / devices like most other ARM platforms based on
feedback from Arnd Bergmann (see
This patch documents the device tree bindings required for
the ohci on-chip controller found in ST consumer electronics SoC's.
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/ohci-st.txt | 37 +++
1 file changed, 37 insertions(+)
create mode 100644
On Fri, Sep 5, 2014 at 10:17 AM, Daniel Borkmann wrote:
> On 09/05/2014 07:13 PM, Mikulas Patocka wrote:
>>
>> On Fri, 5 Sep 2014, Daniel Borkmann wrote:
>>>
>>> On 09/05/2014 07:00 PM, Hannes Frederic Sowa wrote:
On Fr, 2014-09-05 at 18:20 +0200, Daniel Borkmann wrote:
>
> Hi
Keystone K2E EVM uses Marvel 0x9182 controller. This requires support
for the ID in the ahci driver.
Signed-off-by: Murali Karicheri
CC: Tejun Heo
CC: Santosh Shilimkar
---
- Resending with some description in the commit log
drivers/ata/ahci.c |2 ++
1 file changed, 2 insertions(+)
The userspace drm.h include doesn't prefix the drm directory. This can lead
to compile failures as /usr/include/drm/ isn't in the standard gcc include
paths. Fix it to be , which matches the rest of the driver drm
header files that get installed into /usr/include/drm.
Red Hat Bugzilla:
This is a win8 feature that has been implemented. Turn on the feature bit
to enable the feature. With this feature turned on, when the host is waiting
for space to become available on the ringbuffer (host to guest), the guest
will interrupt the host when space becomes available (as part of
On 09/05/2014 07:13 PM, Mikulas Patocka wrote:
On Fri, 5 Sep 2014, Daniel Borkmann wrote:
On 09/05/2014 07:00 PM, Hannes Frederic Sowa wrote:
On Fr, 2014-09-05 at 18:20 +0200, Daniel Borkmann wrote:
Hi Mikulas,
On 09/05/2014 06:01 PM, Mikulas Patocka wrote:
This patch fixes false positive
On Fri, Sep 5, 2014 at 7:08 AM, Baoquan He wrote:
> Currently kaslr enabling can extend the kernel virtual address space
> to 1G, next is for modules. So if kernel is loaded to above 1G, system
> running will be exceptional, This happened when kexec/kdump load kernel.
>
> So add a check to see if
On Fri, Aug 08, 2014 at 01:36:03PM +0800, Ethan Zhao wrote:
> This patch set introduces three PCI device flag operation helper functions
> when set pci device PF/VF to assigned or deassigned status also check it.
> and patch 2,3,4 apply these helper functions to KVM,XEN and PCI.
>
> v2: simplify
Some Toshiba models with illumination support set a different
value on the returned codes, thus not allowing the illumination
LED to be registered, where it should be.
This patch removes a check from toshiba_illumination_available
function to allow such models to register the illumination LED.
The function toshiba_touchpad_store is not checking
for invalid values and simply returns silently.
This patch checks for invalid values and returns accordingly.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_acpi.c | 14 ++
1 file changed, 10 insertions(+), 4
Newer Toshiba models now come with a new (and different) keyboard
backlight implementation whith three modes of operation: TIMER,
ON and OFF, and the LED is controlled internally by the firmware.
This patch adds support for that type of backlight, changing the
existing code to accomodate the new
The accelerometer sensor is very sensitive, and having userspace
poll the sysfs position entry is not very battery friendly.
This patch removes the sysfs entry and instead, it creates an
input polled device (joystick) for the built-in accelerometer.
Signed-off-by: Azael Avalos
---
Up for review.
This series of patches introduce support for the new
keyboard backlight type found on recent Toshiba laptops,
removes the position sysfs entry and instead creates an
input polled device (joystick), and a few fixes and
additions to the keymap list.
Azael Avalos (5):
toshiba_acpi:
Appart from reporting hotkeys, the INFO method is used
as a system wide event notifier for hardware or
software changes.
This patch adds additional "events" to the keymap list,
ignored by now, until we find them a good use.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_acpi.c |
On Fri, 5 Sep 2014, Daniel Borkmann wrote:
> On 09/05/2014 07:00 PM, Hannes Frederic Sowa wrote:
> > On Fr, 2014-09-05 at 18:20 +0200, Daniel Borkmann wrote:
> > > Hi Mikulas,
> > >
> > > On 09/05/2014 06:01 PM, Mikulas Patocka wrote:
> > > > This patch fixes false positive kmemcheck warning
Signed-off-by: Murali Karicheri
CC: Tejun Heo
CC: Santosh Shilimkar
---
drivers/ata/ahci.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index a29f801..02a415e 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -442,6 +442,8 @@
Quoting Seth Forshee (seth.fors...@canonical.com):
> If the process reading on the fuse fd is executing in a pid
> namespace then giving it the global pid of the process making
> a request doesn't make sense. Instead, capture the pid namespace
> when the filesystem is first mounted and translate
On Fri, Sep 5, 2014 at 7:08 AM, Baoquan He wrote:
> kaslr's action is splitted into 2 parts. The 1st is getting available memory
> slots and randomly choose the kernel relocation address. After decompression
> of kernel to the chosen place, the 2nd part begin to check if kaslr has got
> a
On 09/05/2014 07:00 PM, Hannes Frederic Sowa wrote:
On Fr, 2014-09-05 at 18:20 +0200, Daniel Borkmann wrote:
Hi Mikulas,
On 09/05/2014 06:01 PM, Mikulas Patocka wrote:
This patch fixes false positive kmemcheck warning in bpf.
When we try to write the variable len, the compiler generates a
On 09/05/2014 11:03 AM, Arne Wiebalck wrote:
>
> On Sep 5, 2014, at 6:41 PM, Peter Kieser
> wrote:
>
>>
>> On 2014-09-05 8:37 AM, Eddie Chapman wrote:
>>> On 05/09/14 15:17, Jens Axboe wrote:
(from oldest to newest). And that's just from 3.16 to 3.17-rc3, going
all the way back to
On Sep 5, 2014, at 6:41 PM, Peter Kieser
wrote:
>
> On 2014-09-05 8:37 AM, Eddie Chapman wrote:
>> On 05/09/14 15:17, Jens Axboe wrote:
>>> (from oldest to newest). And that's just from 3.16 to 3.17-rc3, going
>>> all the way back to 3.10 would be a lot of work. If there's anyone that
>>>
On Thu, 4 Sep 2014, Paul E. McKenney wrote:
> On Thu, Sep 04, 2014 at 10:18:31AM -0500, Christoph Lameter wrote:
> > This is on top of the first patch (but still not against your tree). I
> > wonder what you think about this one. No special operations.
> >
> >
> > Since dynticks_idle is only ever
On Thu, 4 Sep 2014, Paul E. McKenney wrote:
> So in short, you don't see the potential for this use case actually
> breaking anything, correct?
In general its a performance impact but depending on how this_cpu_ops may
be implemented in a particular platform there may also be correctness
issues
On Fr, 2014-09-05 at 18:20 +0200, Daniel Borkmann wrote:
> Hi Mikulas,
>
> On 09/05/2014 06:01 PM, Mikulas Patocka wrote:
> > This patch fixes false positive kmemcheck warning in bpf.
> >
> > When we try to write the variable len, the compiler generates a code that
> > reads the 32-bit word,
On Fri, Sep 05, 2014 at 04:41:43PM +0100, Linus Torvalds wrote:
> On Fri, Sep 5, 2014 at 8:16 AM, Peter Zijlstra wrote:
> >
> > How horrible is the below patch (performance wise). It does pretty much
> > the same thing except that percpu_rw_semaphore is a lot saner, its
> > read side performance
Quoting Seth Forshee (seth.fors...@canonical.com):
> Filesystem uids which don't map into a user namespace may result
> in inode->i_uid being INVALID_UID. A symlink and its parent
> could have different owners in the filesystem can both get
> mapped to INVALID_UID, which may result in following a
On Thu, Sep 4, 2014 at 11:38 PM, Laszlo Ersek wrote:
> On 09/05/14 07:47, Anders Darander wrote:
> In other words, the rounding up of the kernel will be undone in a
> "somewhat higher level" driver in the firmware, and the request size
> that reaches DiskIo (the "lowel level driver") remains the
Add support for the Dell Latitude E6540 which needs a different fan speed
multiplier.
Signed-off-by: Steven Honeyman
---
drivers/char/i8k.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/char/i8k.c b/drivers/char/i8k.c
index 65525c7..34174d0 100644
---
On Fri, Sep 5, 2014 at 7:08 AM, Baoquan He wrote:
> Now kaslr makes kernel image size changable, not the fixed size 512M.
> So KERNEL_IMAGE_SIZE need be exported to VMCOREINFO, otherwise makedumfile
> will crash.
Seems like a good idea, yes.
>
> Signed-off-by: Baoquan He
> ---
>
On Fri, Sep 05, 2014 at 05:55:20PM +0100, Peter Griffin wrote:
> Hi Felipe,
>
> On Fri, 05 Sep 2014, Felipe Balbi wrote:
> > > > +
> > > > + device_for_each_child(>dev, NULL, st_dwc3_remove_child);
> > >
> > > same as before, of_platform_depopulate(). I can fix this one myself this
> > >
On 09/05/2014 03:28 AM, Mikko Perttunen wrote:
From: Mikko Perttunen
Currently the i2c-tegra bus driver prepares, enables
and set_rates its clocks separately for each transfer.
This causes locking problems when doing I2C transfers
from clock notifiers; see
Hi Felipe,
On Fri, 05 Sep 2014, Felipe Balbi wrote:
> > > +
> > > + device_for_each_child(>dev, NULL, st_dwc3_remove_child);
> >
> > same as before, of_platform_depopulate(). I can fix this one myself this
> > time.
Oh sorry, not sure what happened there, thanks for fixing it up:-)
>
> it's in
On Fri 05-09-14 09:43:52, Cong Wang wrote:
> On Fri, Sep 5, 2014 at 7:08 AM, Tejun Heo wrote:
> >
> > Prolly should sta...@vger.kernel.org?
>
> Oh, yes. I assume the maintainer (Michal?) will send it to stable
I guess you meant Rafael.
> once it is accepted, or I can do that after it is
From: huang lin
This adds basic SPI nodes to the base rk3288 device tree file.
A few notes:
* It's assumed that most users of the SPI ports are using chip select
0. Thus the default pinctrl for the ports enables chip select 0
(but not chip select 1 on ports that have it). If a board wants
Changes since 20140904:
None.
Non-merge commits (relative to Linus' tree): 3727
3261 files changed, 133225 insertions(+), 99782 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git .
If you are tracking the linux-next tree
On Fri, Sep 05, 2014 at 04:33:17PM +0100, Daniel Thompson wrote:
> Drivers that are shared between arm and arm64 and which employ
> FIQ on arm cannot include asm/fiq.h without #ifdef'ing. This patch
> introduces a dummy version of asm/fiq.h to arm64 to avoid this.
>
> Signed-off-by: Daniel
Michel Dänzer writes:
> On 30.08.2014 22:59, Mikael Pettersson wrote:
> > Since 3.17-rc1 my radeon card (RV370 / X1050 card) causes screen corruption
> > after a while in X + firefox. This still occurs with yesterday's HEAD
> > of Linus' repo. 3.16 and ealier kernels are fine.
> >
> > I
Quoting Seth Forshee (seth.fors...@canonical.com):
> Update fuse to support mounts from within user namespaces. This
> is mostly a matter of translating uids and gids into the
> namespace of the process reading requests before handing the
> requests off to userspace.
>
> Due to security concerns
On Fri, Sep 5, 2014 at 12:32 PM, Christoph Hellwig wrote:
> On Fri, Sep 05, 2014 at 12:27:21PM -0400, Milosz Tanski wrote:
>> I would prefer a interface more like recv() where I can specify the
>> flag if I want blocking behavior for this read or not. Let me explain
>> why:
>>
>> In a VLDB like
On Fri, 5 Sep 2014, Linus Torvalds wrote:
> However, the more fundamental question is "what protects accesses to
> 'events->ctx'". Why is "put_event()" so special that *it* gets locking
> for the reading of "event->ctx", but none of the other cases of
> reading the ctx pointer gets it or needs
On Fri, 5 Sep 2014, Tejun Heo wrote:
> I suppose this should go through percpu/for-3.18-consistent-ops? Can
> we please cc irq folks and get acks?
Russell and Nicolas were cced. This is arm specific.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Friday, September 05, 2014 11:12:41 PM Tejun Heo wrote:
> On Fri, Sep 05, 2014 at 12:47:16AM -0700, Luis R. Rodriguez wrote:
> > Ah -- well without it the way we "find" drivers that need this new
> > "async feature" is by a bug report and folks saying their system can't
> > boot, or they say
On Fri, Sep 5, 2014 at 7:08 AM, Tejun Heo wrote:
>
> Prolly should sta...@vger.kernel.org?
Oh, yes. I assume the maintainer (Michal?) will send it to stable
once it is accepted, or I can do that after it is merged.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 2014-09-05 8:37 AM, Eddie Chapman wrote:
On 05/09/14 15:17, Jens Axboe wrote:
(from oldest to newest). And that's just from 3.16 to 3.17-rc3, going
all the way back to 3.10 would be a lot of work. If there's anyone that
cares about bcache on stable kernels (and actually use it), now would
301 - 400 of 1674 matches
Mail list logo
