Hi Linus,
The following changes since commit 74d33293e467df61de1b1d8b2fbe29e550dec33b:
Linux 4.2-rc5 (2015-08-02 18:34:55 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.3-1
for you to fetch changes up to
On Friday, September 04, 2015 06:06:47 PM Marc Zyngier wrote:
> IRQ controllers and timers are the two types of device the kernel
> requires before being able to use the device driver model.
>
> ACPI so far lacks a proper probing infrastructure similar to the one
> we have with DT, where we're
Hi Doug, Tejun,
This is from cgroups for-4.3 branch.
linux-rdma trunk will face compilation error as its behind Tejun's
for-4.3 branch.
Patch has dependency on the some of the cgroup subsystem functionality
for fork().
Therefore its required to merge those changes first to linux-rdma trunk.
On Mon, Sep 7, 2015 at 10:42 PM, Linus Torvalds
wrote:
> On Mon, Sep 7, 2015 at 1:31 PM, Sedat Dilek wrote:
>>
>> So, how do I do that conveniently?
>
> For a single file? Just compile everything with the primary compiler,
> and then delete the single object file, and do "make" again.
>
That
On 09/07/2015 11:50 PM, Alexey Brodkin wrote:
Current implementation via IS_ERR(phydev) may make no sense because
of_phy_attach() returns NULL on failure instead of error value.
Still for checking result of phy_connect() IS_ERR() is useful.
To address both situations we use combined
On Monday, September 07, 2015 11:42:41 PM Irina Tirdea wrote:
> Add new option to sysfs control interface, allowing the user to force
> suspend the device.
Had we thought this had been a good idea, we'd have added that thing to
the interface from the start.
The problem with it is that user space
On Mon, Sep 7, 2015 at 7:23 AM, Tomeu Vizoso wrote:
> Hello,
>
> I have a problem with the panel on my Tegra Chromebook taking longer
> than expected to be ready during boot (Stéphane Marchesin reported what
> is basically the same issue in [0]), and have looked into ordered
> probing as a better
Current implementation via IS_ERR(phydev) may make no sense because
of_phy_attach() returns NULL on failure instead of error value.
Still for checking result of phy_connect() IS_ERR() is useful.
To address both situations we use combined IS_ERR_OR_NULL() check.
Cc: Giuseppe Cavallaro
Cc:
Validate the new compression algorithm before copying it into the zram
'compressor' field, keeping the old one if it's invalid.
The error path code is also slightly refactored.
Signed-off-by: Luis Henriques
---
drivers/block/zram/zram_drv.c | 13 -
1 file changed, 8 insertions(+),
On Sun, Sep 6, 2015 at 11:57 PM, Peter Zijlstra wrote:
>
> Just to continue the argument for arguments sake, the function is named
> 'virt' (not paravirt) and tests the HYPERVISOR CPUID bit. How is that
> not appropriately named?
Well, I think right now one issue is that you can't avoid it, even
Modified device cgroup documentation to reflect its dual purpose
without creating new cgroup subsystem for rdma.
Added documentation to describe functionality and usage of device cgroup
extension for RDMA.
Signed-off-by: Parav Pandit
---
Documentation/cgroups/devices.txt | 32
On Mon, Sep 7, 2015 at 1:31 PM, Sedat Dilek wrote:
>
> So, how do I do that conveniently?
For a single file? Just compile everything with the primary compiler,
and then delete the single object file, and do "make" again.
Use a wrapper around the compiler (and point to that wrapper with the
"to
Add new option to sysfs control interface, allowing the user to force
suspend the device. This is useful for devices that need to be
suspended when closing the lid of a laptop or the screen of a mobile
device, while userspace still holds open handles to it and the
system does not enter system
Extension of device cgroup for RDMA device resources.
This implements RDMA resource tracker to limit RDMA resources such as
AH, CQ, PD, QP, MR, SRQ etc resources for processes of the cgroup.
It implements RDMA resource limit module to limit consuming RDMA
resources for processes of the cgroup.
1. Moved necessary functions and data structures to header file to
reuse them at device cgroup white list functionality and for rdma
functionality.
2. Added infrastructure to invoke RDMA specific routines for resource
configuration, query and during fork handling.
3. Added sysfs interface files
Added RDMA device resource tracking object per task.
Added comments to capture usage of task lock by device cgroup
for rdma.
Signed-off-by: Parav Pandit
---
include/linux/sched.h | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/include/linux/sched.h
RDMA uverbs modules now queries associated device cgroup rdma controller
before allocating device resources and uncharge them while freeing
rdma device resources.
Since fput() sequence can free the resources from the workqueue
context (instead of task context which allocated the resource),
it
Added RDMA resource tracking object of device cgroup.
Signed-off-by: Parav Pandit
---
security/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/security/Makefile b/security/Makefile
index c9bfbc8..c9ad56d 100644
--- a/security/Makefile
+++ b/security/Makefile
@@ -23,6 +23,7 @@
Added user configuration option to enable/disable RDMA resource tracking
feature of device cgroup as sub module.
Signed-off-by: Parav Pandit
---
init/Kconfig | 12
1 file changed, 12 insertions(+)
diff --git a/init/Kconfig b/init/Kconfig
index 2184b34..089db85 100644
---
Currently user space applications can easily take away all the rdma
device specific resources such as AH, CQ, QP, MR etc. Due to which other
applications in other cgroup or kernel space ULPs may not even get chance
to allocate any rdma resources.
This patch-set allows limiting rdma resources to
On Mon, Sep 7, 2015 at 10:15 PM, Linus Torvalds
wrote:
> On Mon, Sep 7, 2015 at 12:12 PM, Sedat Dilek wrote:
>>
>> is it possible to use a different compiler at build-time?
>>
>> I have here a problem with mm/percpu.c and wanted to build everything
>> with LLVM/Clang but this single file with
The recently added endpoint capabilities flags verification breaks Atmel
USBA because the endpoint configuration was only added when the driver
is bound using the legacy pdata interface.
Convert endpoint configuration to new capabilities model when driver is
bound to a device tree as well.
On Mon, Sep 7, 2015 at 12:12 PM, Sedat Dilek wrote:
>
> is it possible to use a different compiler at build-time?
>
> I have here a problem with mm/percpu.c and wanted to build everything
> with LLVM/Clang but this single file with GCC.
>
> Is that possible?
It should work fine. It's
On 09/04/2015 05:39 PM, Jonathan Corbet wrote:
> On Fri, 4 Sep 2015 14:53:34 -0300
> Danilo Cesar Lemes de Paula wrote:
>
>> In the last few days I sent three features:
>> Markdown support (patch series 1)
>> Cross-reference hyperlink support (patch series 1)
>> in-struct-body documentation
On 02/09/2015 09:03, Sudip Mukherjee wrote:
> We were taking the exit path after checking ue->flags and return value
> of setup_routing_entry(), but 'e' was not freed incase of a failure.
>
> Signed-off-by: Sudip Mukherjee
> ---
> virt/kvm/irqchip.c | 8 ++--
> 1 file changed, 6
Using pandoc as the Markdown engine cause some minor side effects as
pandoc includes main tags for almost everything.
Original Markdown support approach removes those main tags, but it caused
some inconsistencies when that tag is not the main one, like:
..
...
As kernel-doc was already
DRM Docbook is now Markdown ready. This means its doc is able to
use markdown text on it.
* Documentation/DocBook/drm.tmpl: Contains a table duplicated from
drivers/gpu/drm/i915/i915_reg.h. This is not needed anymore
* drivers/gpu/drm/drm_modeset_lock.c: had a code example that used
to look
Markdown support is given by calling an external tool, pandoc, for all
highlighted text on kernel-doc.
Pandoc converts Markdown text to proper Docbook tags, which will be
later translated to pdf, html or other targets.
This adds the capability of adding human-readle text highlight (bold,
Docproc process EXPORT_SYMBOL(f1) macro and uses -nofunc f1 to
avoid duplicated documentation in the next call.
It works for most of the cases, but there are some specific situations
where a struct has the same name of an already-exported function.
Current kernel-doc behavior ignores those
"/**" should be used for kernel-doc documentation only.
It causes a warning with the new "in struct body" format.
Signed-off-by: Danilo Cesar Lemes de Paula
Cc: Randy Dunlap
Cc: Daniel Vetter
Cc: Laurent Pinchart
Cc: Jonathan Corbet
Cc: Herbert Xu
Cc: Stephan Mueller
Cc: Michal Marek
Cc:
The "highlight" code is very sensible to the order of the hash keys,
but the order of the keys cannot be predicted. It generates
faulty DocBook entries like:
- @device_for_each_child
Sorting the result is not enough some times (as it's deterministic but
we can't control it).
We should use
The following series contains:
* kernel-doc: markdown support and improvements.
* Fixing kernel-doc highlights.
* Improve doc support for functions and structs with same name.
* misc small fixes for drm docbook.
Signed-off-by: Danilo Cesar Lemes de Paula
Cc: Daniel Vetter
Cc: Jonathan
Good day,
You may find attached remittance for second lot required and copy of the
message of transferring payment on your account (Second part) as per
attached file.
Please let us have your official confirmation letter (on the letter head
with sign and stamp), clarifying receiving the mentioned
On Mon, Sep 07, 2015 at 07:54:18PM +0100, Dietmar Eggemann wrote:
> I would vote for removing this SCHED_LOAD_RESOLUTION thing completely so that
> we can
> assume that load/util and capacity are always using 1024/10.
Ha!, I just requested Google look into moving it to 20 again ;-)
--
To
On Mon, 7 Sep 2015, Arnd Bergmann wrote:
> On Thursday 03 September 2015 21:24:00 Nicolas Pitre wrote:
> > If 768MB targets were common place then it could be worth changing the
> > default vmalloc size to accommodate this memory size and testing all the
> > other targets to make sure no
2015-09-07 18:24 GMT+02:00 Javier Martinez Canillas :
> Only the IGEPv2 boards have a LAN9221i chip connected to the GPMC
> so the pinmux configuration for the GPIO connected to the IRQ line
> of the LAN chip should not be defined in the IGEP common dtsi but
> in the one common to the IGEPv2
On Mon, 7 Sep 2015, Andy Lutomirski wrote:
> > These are all implementation-specific details, including the INT1
> > instruction, which is why I am not at all surprised that they are omitted
> > from architecture manuals.
>
> That bit is BS, though. The INT1 instruction, executed in user mode
Hi Antoine,
Just one observation below.
El 26/08/15 a las 05:07, Antoine Tenart escribió:
> Add a PWM controller driver for the Marvell Berlin SoCs. This PWM
> controller has 4 channels.
>
> Signed-off-by: Antoine Tenart
> Acked-by: Sebastian Hesselbarth
> ---
> drivers/pwm/Kconfig |
412758cb2670 (jump label, locking/static_keys: Update docs) introduced a
typo that might as well get fixed.
Signed-off-by: Jonathan Corbet
---
Documentation/static-keys.txt | 2 +-
include/linux/jump_label.h| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Florian,
I wrote some observations below that maybe can be useful.
El 28/08/15 a las 22:21, Florian Fainelli escribió:
> Add support for the BCM7038-style PWM controller found in all BCM7xxx STB
> SoCs.
> This controller has a hardcoded 2 channels per controller, and cascades a
> variable
Hi,
is it possible to use a different compiler at build-time?
I have here a problem with mm/percpu.c and wanted to build everything
with LLVM/Clang but this single file with GCC.
Is that possible?
Regards,
- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On 07/09/15 17:21, Vincent Guittot wrote:
> On 7 September 2015 at 17:37, Dietmar Eggemann
> wrote:
>> On 04/09/15 00:51, Steve Muckle wrote:
>>> Hi Morten, Dietmar,
>>>
>>> On 08/14/2015 09:23 AM, Morten Rasmussen wrote:
>>> ...
+ * cfs_rq.avg.util_avg is the sum of running time of
On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
>
> Hi Linus,
>
> This is the main pull request for the drm for 4.3. Nouveau is probably the
> biggest
> amount of changes in here, since it missed 4.2. Highlights below, along with
> the usual
> bunch of fixes. There are a
On Mon, 2015-09-07 at 19:08 +0100, Maitesin wrote:
> The coding style issue is the white spaces after and before the
> brackets in the for. The change in the conditional is to make it
> consistence with the other ones in the file. All other conditionals are
> tested like that.
[]
> diff --git
Hello.
On 09/07/2015 09:15 PM, Alexey Brodkin wrote:
Current implementation via IS_ERR(phydev) may make no sense because
of_phy_attach() returns NULL on failure instead of error value.
Still for checking result of phy_connect() IS_ERR() is useful.
So adding explicit check for NULL.
Current implementation via IS_ERR(phydev) may make no sense because
of_phy_attach() returns NULL on failure instead of error value.
Still for checking result of phy_connect() IS_ERR() is useful.
So adding explicit check for NULL.
Cc: Giuseppe Cavallaro
Cc: arc-linux-...@synopsys.com
Cc:
The coding style issue is the white spaces after and before the brackets in the
for. The change in the conditional is to make it consistence with the other
ones in the file. All other conditionals are tested like that.
Signed-off-by: Oscar Forner Martinez
---
fs/isofs/compress.c | 4 ++--
1
On Fri, Sep 04, 2015 at 11:33:35PM +0100, David Daney wrote:
> Hi Mark,
Hi David,
> I now have a prototype implementation for irq-gic-v3-its.c that is using
> this binding on Cavium's ThunderX platform.
>
> Q: Have you guys had any more thoughts on this that might require
> changing the
> > +PCI root complex
> > +
> > +
> > +Optional properties
> > +---
> > +
> > +- msi-map: Maps a Requester ID to an MSI controller and associated
> > + msi-specifier data. The property is an arbitrary number of tuples of
> > +
Sorry, I didn't read these emails, and I never looked at this code...
Can't understand what are you talking about but a minor nit anyway ;)
On 09/04, Petr Mladek wrote:
>
> + __set_current_state(TASK_RUNNING);
> if (!kthread_should_stop())
> wait_to_die();
I bet this
Hi Sergio,
sorry for the delay. I'm fighting deadlines at the moment, so even if
this is my highest spare time priority right now I can't find enough
quiet time to dig into the problem. I'd suggest you resend a report
to linux-ide (with a Cc to linux-scsi) so that the people who know the
libata
On 07/09/15 18:15, Catalin Marinas wrote:
On Mon, Sep 07, 2015 at 05:54:06PM +0100, Suzuki K. Poulose wrote:
On 14/08/15 19:28, Robert Richter wrote:
diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
index c52f7ba205b4..4211c39b8744 100644
---
On 07/09/15 17:00, Lorenzo Pieralisi wrote:
> [+M.Salter]
>
> On Fri, Sep 04, 2015 at 06:06:48PM +0100, Marc Zyngier wrote:
>> IRQ controllers and timers are the two types of device the kernel
>> requires before being able to use the device driver model.
>>
>> ACPI so far lacks a proper probing
On 07.09.15 18:09:48, Marc Zyngier wrote:
> On 07/09/15 17:54, Suzuki K. Poulose wrote:
> > On 14/08/15 19:28, Robert Richter wrote:
> >> From: Robert Richter
> >> +static void gicv3_enable_quirks(void)
> >> +{
> >> + if (cpus_have_cap(ARM64_WORKAROUND_CAVIUM_23154))
> >> +
On Mon, Sep 7, 2015 at 10:01 AM, Maciej W. Rozycki wrote:
> These are all implementation-specific details, including the INT1
> instruction, which is why I am not at all surprised that they are omitted
> from architecture manuals.
That bit is BS, though. The INT1 instruction, executed in user
Fixes regression 4.3 mergw window in my config
where hyperv is enable but CONFIG_KEXEC not enabled.
arch/x86/kernel/cpu/mshyperv.c:112: undefined reference to
`native_machine_crash_shutdown'
Introduced by:
commit b4370df2b1f5158de028e167974263c5757b34a6
Author: Vitaly Kuznetsov
Date:
On 27 July 2015 at 10:50, Alex Smith wrote:
> Add DT bindings for NAND devices connected to the NEMC on JZ4780 SoCs,
> as well as the hardware BCH controller, used by the jz4780_{nand,bch}
> drivers.
>
> Signed-off-by: Alex Smith
> Cc: Zubair Lutfullah Kakakhel
> Cc: David Woodhouse
> Cc:
On Mon, Sep 07, 2015 at 05:54:06PM +0100, Suzuki K. Poulose wrote:
> On 14/08/15 19:28, Robert Richter wrote:
> >diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> >index c52f7ba205b4..4211c39b8744 100644
> >--- a/drivers/irqchip/irq-gic-v3.c
> >+++
Sorry for delay,
On 09/02, Boqun Feng wrote:
>
> On Tue, Sep 01, 2015 at 06:39:23PM +0200, Oleg Nesterov wrote:
> > On 09/01, Boqun Feng wrote:
> > >
> > > On Tue, Sep 01, 2015 at 11:59:23AM +0200, Oleg Nesterov wrote:
> > > >
> > > > And just in case, wake_up() differs in a sense that it doesn't
On 07/09/15 17:54, Suzuki K. Poulose wrote:
> On 14/08/15 19:28, Robert Richter wrote:
>> From: Robert Richter
>>
>> This patch implements Cavium ThunderX erratum 23154.
>>
>> The gicv3 of ThunderX requires a modified version for reading the IAR
>> status to ensure data synchronization. Since
From: Ulf Magnusson
Without knowing this, the use of sysfs_streq() becomes puzzling.
The termination happens in kernfs_fop_write().
Signed-off-by: Ulf Magnusson
---
Documentation/filesystems/sysfs.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/filesystems/sysfs.txt
From: Ulf Magnusson
According to commit a59d6293e537 ("debugfs: change parameter check in
debugfs_remove() functions"), this is meant to make cleanup easier for
callers. In that case it ought to be documented.
Signed-off-by: Ulf Magnusson
---
fs/debugfs/inode.c | 6 --
1 file changed, 4
On Mon, 7 Sep 2015, Paolo Bonzini wrote:
> > I didn't do stuff at the probe firmware level so I can't say for sure,
> > but my gut feeling is the debug mode is indeed very close if not the same
> > as SMM. I think duplicating the logic would be an unnecessary waste of
> > silicon.
>
> I
On 15/09/07, Richard Guy Briggs wrote:
> Nothing prevents a new auditd starting up and replacing a valid
> audit_pid when an old auditd is still running, effectively starving out
> the old auditd since audit_pid no longer points to the old valid auditd.
>
> There isn't an easy way to detect if an
You might need to rebase you patch. A patch to netback went it recently.
On Mon, Sep 07, 2015 at 04:33:56PM +0100, Julien Grall wrote:
> The PV network protocol is using 4KB page granularity. The goal of this
> patch is to allow a Linux using 64KB page granularity working as a
> network backend
On Fri, Aug 21, 2015 at 03:01:33PM -0700, Feng Kan wrote:
> diff --git a/arch/arm64/lib/copy_from_user.S b/arch/arm64/lib/copy_from_user.S
> index 1be9ef2..cb085cf 100644
> --- a/arch/arm64/lib/copy_from_user.S
> +++ b/arch/arm64/lib/copy_from_user.S
> @@ -18,6 +18,7 @@
>
> #include
>
On 14/08/15 19:28, Robert Richter wrote:
From: Robert Richter
This patch implements Cavium ThunderX erratum 23154.
The gicv3 of ThunderX requires a modified version for reading the IAR
status to ensure data synchronization. Since this is in the fast-path
and called with each interrupt,
Michal Hocko wrote:
> As the VM cannot do much about these requests we should face the reality
> and allow those allocations to fail. Johannes has already posted the
> patch which does that (http://marc.info/?l=linux-mm=142726428514236=2)
> but the discussion died pretty quickly.
Addition of
Nothing prevents a new auditd starting up and replacing a valid
audit_pid when an old auditd is still running, effectively starving out
the old auditd since audit_pid no longer points to the old valid auditd.
There isn't an easy way to detect if an old auditd is still running on
the existing
On 07.09.15 17:44:41, Marc Zyngier wrote:
> On 25/08/15 11:18, Ganapatrao Kulkarni wrote:
> > The patch below adds a workaround for gicv3 in a numa environment. It
> > is on top of Robert's recent gicv3 errata patch submission v4 and my
> > arm64 numa patches v5.
> >
> > This implements a
On 25/08/15 11:18, Ganapatrao Kulkarni wrote:
> The patch below adds a workaround for gicv3 in a numa environment. It
> is on top of Robert's recent gicv3 errata patch submission v4 and my
> arm64 numa patches v5.
>
> This implements a workaround for gicv3-its erratum 23144 on Cavium's
> ThunderX
On Mon, 7 Sep 2015, Julien Grall wrote:
> For ARM64 guests, Linux is able to support either 64K or 4K page
> granularity. Although, the hypercall interface is always based on 4K
> page granularity.
>
> With 64K page granularity, a single page will be spread over multiple
> Xen frame.
>
> To
On Thu, Sep 3, 2015 at 1:49 PM, Andrey Konovalov wrote:
> On Wed, Sep 2, 2015 at 9:40 PM, Tejun Heo wrote:
>> Hello, Andrey.
>
> Hello Tejun,
>
>> On Wed, Sep 02, 2015 at 01:08:52PM +0200, Andrey Konovalov wrote:
>>> While running KASAN on 4.2 with Trinity I got the following report:
>>>
>>>
Hi Robert,
On 14/08/15 19:28, Robert Richter wrote:
> From: Robert Richter
>
> This patch series adds gicv3 updates and workarounds for HW errata in
> Cavium's ThunderX GICV3.
>
> The first one is an unchanged resubmission of a patch from a gicv3
> series I sent a while ago.
>
> The next
On Sep 8, 2015, at 1:06 AM, James Morse wrote:
> On 07/09/15 16:48, Jungseok Lee wrote:
>> On Sep 7, 2015, at 11:36 PM, James Morse wrote:
>>
>> Hi James,
>>
>>> Having to handle interrupts on top of an existing kernel stack means the
>>> kernel stack must be large enough to accomodate both the
On 2015/9/7 22:56, Marc Zyngier wrote:
> Hi Thomas,
>
> On 07/09/15 14:24, Thomas Gleixner wrote:
>> On Mon, 7 Sep 2015, Marc Zyngier wrote:
>>> On 06/09/15 06:56, Jiang Liu wrote:
On 2015/9/6 12:23, Yang Yingliang wrote:
> Use irq_settings_set_move_pcntxt() helper irqs status with
>
On 14/08/15 19:28, Robert Richter wrote:
> From: Robert Richter
>
> This implements two gicv3-its errata workarounds for ThunderX. Both
> with small impact affecting only ITS table allocation.
>
> erratum 22375: only alloc 8MB table size
> erratum 24313: ignore memory access type
>
> The
On Sun, Sep 06, 2015 at 05:44:30PM +0800, Wu, Songjun wrote:
> On 9/3/2015 19:43, Mark Brown wrote:
> >Why is this a separate DT node? It seems that this IP is entirely self
> >contained so I'm not clear why we need a separate node for the card, the
> >card is usually a separate node because it
Hi Robert,
On 14/08/15 19:28, Robert Richter wrote:
> From: Robert Richter
>
> Some GIC revisions require an individual configuration to esp. add
> workarounds for HW bugs. This patch implements generic code to parse
> the hw revision provided by an IIDR register value and runs specific
> code
Only the IGEPv2 boards have a LAN9221i chip connected to the GPMC
so the pinmux configuration for the GPIO connected to the IRQ line
of the LAN chip should not be defined in the IGEP common dtsi but
in the one common to the IGEPv2 boards.
While there, use the OMAP3_CORE1_IOPAD() macro for the
Spaces at the starting of a line are removed, indentation using
tab, instead of space. Also, line width of more than 80 characters
is also taken care of.
Two warnings are left alone to aid better readability.
Signed-off-by: Muhammad Falak R Wani
---
drivers/leds/leds-ipaq-micro.c | 18
On Sun, Sep 06, 2015 at 05:44:21PM +0800, Wu, Songjun wrote:
> On 9/3/2015 19:37, Mark Brown wrote:
> >On Tue, Sep 01, 2015 at 01:41:40PM +0800, Songjun Wu wrote:
> >>+static const char * const eqcfg_bass_text[] = {
> >>+ "-12 dB", "-6 dB", "0 dB", "+6 dB", "+12 dB"
> >>+};
> >
> >>+static
On 7 September 2015 at 17:37, Dietmar Eggemann wrote:
> On 04/09/15 00:51, Steve Muckle wrote:
>> Hi Morten, Dietmar,
>>
>> On 08/14/2015 09:23 AM, Morten Rasmussen wrote:
>> ...
>>> + * cfs_rq.avg.util_avg is the sum of running time of runnable tasks plus
>>> the
>>> + * recent utilization of
Allow it to be used from SPU, since it should not have unwanted
side-effects.
[ Picked-by: Michael Ellerman ]
Signed-off-by: Mathieu Desnoyers
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Michael Ellerman
CC:
Signed-off-by: Mathieu Desnoyers
Acked-by: "David S. Miller"
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: sparcli...@vger.kernel.org
---
arch/sparc/include/uapi/asm/unistd.h | 3 ++-
arch/sparc/kernel/systbls_32.S | 2 +-
arch/sparc/kernel/systbls_64.S | 4 ++--
3 files
[ Untested on this architecture. To try it out: fetch linux-next/akpm,
apply this patch, build/run a membarrier-enabled kernel, and do make
kselftest. ]
Signed-off-by: Mathieu Desnoyers
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: Richard Henderson
CC: Ivan Kokshaysky
CC: Matt
Signed-off-by: Mathieu Desnoyers
Tested-by: Helge Deller
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: "James E.J. Bottomley"
CC: linux-par...@vger.kernel.org
---
arch/parisc/include/uapi/asm/unistd.h | 3 ++-
arch/parisc/kernel/syscall_table.S| 1 +
2 files changed, 3
[ Untested on this architecture. To try it out: fetch linux-next/akpm,
apply this patch, build/run a membarrier-enabled kernel, and do make
kselftest. ]
Signed-off-by: Mathieu Desnoyers
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: Martin Schwidefsky
CC: Heiko Carstens
CC:
arm64 sys_membarrier number is already wired for arm64 through
asm-generic/unistd.h, but needs to be allocated separately for
the 32-bit compability layer of arm64.
[ Untested on this architecture. To try it out: fetch linux-next/akpm,
apply this patch, build/run a membarrier-enabled kernel,
[ Untested on this architecture. To try it out: fetch linux-next/akpm,
apply this patch, build/run a membarrier-enabled kernel, and do make
kselftest. ]
Signed-off-by: Mathieu Desnoyers
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: Tony Luck
CC: Fenghua Yu
CC:
[ Untested on this architecture. To try it out: fetch linux-next/akpm,
apply this patch, build/run a membarrier-enabled kernel, and do make
kselftest. ]
Signed-off-by: Mathieu Desnoyers
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: Russell King
---
arch/arm/include/asm/unistd.h
Following feedback from architecture maintainers, this is v2 of this
patchset. Status:
* Picked into maintainer's tree:
- powerpc
* Ready to be picked into maintainer's tree (acked/tested):
- mips, sparc/sparc64, parisc,
* Awaiting feedback/testing:
- arm, arm64, ia64, s390/s390x
Thanks,
Signed-off-by: Mathieu Desnoyers
Acked-by: Ralf Baechle
CC: Andrew Morton
CC: linux-...@vger.kernel.org
CC: linux-m...@linux-mips.org
---
arch/mips/include/uapi/asm/unistd.h | 15 +--
arch/mips/kernel/scall32-o32.S | 1 +
arch/mips/kernel/scall64-64.S | 1 +
On 22/08/2015 00:53, Paolo Bonzini wrote:
> VIRTIO_BLK_F_CONFIG_WCE is important in order to achieve good performance
> (up to 2x, though more realistically +30-40%) in latency-bound workloads.
> However, it was removed by mistake together with VIRTIO_BLK_F_FLUSH.
>
> It will be restored in the
On 07/09/15 16:48, Jungseok Lee wrote:
> On Sep 7, 2015, at 11:36 PM, James Morse wrote:
>
> Hi James,
>
>> Having to handle interrupts on top of an existing kernel stack means the
>> kernel stack must be large enough to accomodate both the maximum kernel
>> usage, and the maximum irq handler
- On Sep 3, 2015, at 11:36 PM, Michael Ellerman m...@ellerman.id.au wrote:
> On Thu, 2015-09-03 at 15:47 +, Mathieu Desnoyers wrote:
>> - On Sep 3, 2015, at 5:33 AM, Michael Ellerman m...@ellerman.id.au wrote:
>>
>> > On Tue, 2015-09-01 at 11:32 -0700, Andy Lutomirski wrote:
>> >> On
On 7 September 2015 at 11:54, Alex Smith wrote:
> On 06/09/2015 21:38, Ezequiel Garcia wrote:
>> On 27 Jul 02:50 PM, Alex Smith wrote:
>>> Hi,
>>>
>>> This series adds support for the BCH controller and NAND devices on
>>> the Ingenic JZ4780 SoC.
>>>
>>> Tested on the MIPS Creator Ci20 board. All
[+M.Salter]
On Fri, Sep 04, 2015 at 06:06:48PM +0100, Marc Zyngier wrote:
> IRQ controllers and timers are the two types of device the kernel
> requires before being able to use the device driver model.
>
> ACPI so far lacks a proper probing infrastructure similar to the one
> we have with DT,
This patch implements a HID driver for the Corsair Vengeance K90 keyboard.
It fixes the behaviour of the keys using incorrect HID usage codes and exposes
the macro playback mode and current profile to the user space through sysfs
attributes. It also adds two LED class devices controlling the
I removed the k90_profile class completely. I cannot write a good enough ABI
with what I know of the keyboard so I am leaving that part out of the kernel.
If I change my mind in the future, it will be done in another patch.
I also fixed a bug I had when unregistering the led device. Work was
101 - 200 of 1136 matches
Mail list logo
