On 04/30/2015 06:39 PM, Jeremy Fitzhardinge wrote:
On 04/30/2015 03:53 AM, Juergen Gross wrote:
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer
On Thu, Apr 23, 2015 at 05:26:45PM +0530, Rameshwar Prasad Sahu wrote:
Suject line should mention the fixes you are doing and not tool!
> v5 changes:
> * Re-pull v3 changes that I missed in v4
>
> v4 changes:
> * Re-generate patch on top of latest for-linux git
>
> v3 changes:
>
Ping.
Any comments on this patch ?
Regards
Preeti U Murthy
On 04/28/2015 02:15 PM, Preeti U Murthy wrote:
> Today the number of bits of the broadcast masks that is output into
> /proc/timer_list is sizeof(unsigned long). This means that on machines
> with larger number of CPUs, the bitmasks of
This is to fix a kernel NULL dereference oops introduced by commit
59fc630b("RAID5: batch adjacent full stripe write"), which introduced
several batch_xxx fields, and did initiation for them at grow_one_stripes(),
but forgot to do same at resize_stripes().
This oops can be easily triggered by
On Mon, 04 May 2015, Vinod Koul wrote:
> On Sat, May 02, 2015 at 09:57:10AM +0200, Nicholas Mc Guire wrote:
> > CodingStyle fix only - align function parameters to opening (.
> >
> This doesnt look any better to me...
>
True it makes little difference when looking at these few lines
I guess
This patch removes the 'num_cables' filed from 'struct adc_jack_pdata'
because 'struct extcon_dev' contains the 'max_supported' field which
means the number of supported cable of extcon device.
Signed-off-by: Chanwoo Choi
---
drivers/extcon/extcon-adc-jack.c | 12
1 file changed,
This patch alters the MHL-TA cable name to TA cable name because MHL-TA is not
standard name. The MHL-TA is MHL cable with charger cable (TA or USB). So, this
patch use the TA cable instead of MHL-TA to inform the charger cable state.
- MHL-TA -> TA
Cc: Jaewon Kim
Cc: Krzysztof Kozlowski
This patch change the name of various jig cables as 'JIG' because the name of
various jig cables are strange and ambiguous on user-space aspect. They include
the different information of either USB and UART state. It is never important
for user-space process. This patch unifies the name of jig
This patch change the name of various dock devices as 'DOCK' because the name of
various dock devices have not the standard naming rules. The name of dock
devices
include the differenct word but it is ambiguous and never important information
on user-space aspect. This patch unifies the name of
This patchset alter the unused name of external connector (jig/dock/MHL) as
following. The name of jig cable and dock device include the non-standard H/W
information. On user-space side, this information are not necessary. The extcon
core will support the other method to inform the specific H/W
On Sun, May 03, 2015 at 03:33:40PM +0200, Jean Delvare wrote:
> Hi Sudip,
Thanks Jean for your time.
>
> On Tue, 28 Apr 2015 17:00:21 +0530, Sudip Mukherjee wrote:
> > + if (!is_parport(>bus_dev))
> > + return;
>
> Can this actually happen?
i got this idea from
Am Sonntag, 3. Mai 2015, 16:58:34 schrieb Theodore Ts'o:
Hi Theodore,
>On Sun, May 03, 2015 at 05:33:00PM +0200, Stephan Mueller wrote:
>> The patch set adds an in-kernel /dev/random equivalent that was discussed
>> with Ted Ts'o last July -- see [2] and [3]. A test module for testing the
>>
On Thu, Apr 09, 2015 at 12:35:54PM +0300, Peter Ujfalusi wrote:
> The sDMA requests are routed through the DMA crossbar and without the
> crossbar only peripherals using DMA request 0-127 can be used.
>
Need an ACK from ARM folks before I apply this and the DT ones too please
--
~Vinod
--
To
On Mon, 2015-05-04 at 07:10 +0200, Mike Galbraith wrote:
> On Mon, 2015-05-04 at 12:39 +0800, Zefan Li wrote:
>
> > >> We are moving toward unified hierarchy where all the cgroup controllers
> > >> are bound together, so it would make cgroups easier to use if we have
> > >> less
> > >>
On Thu, Apr 09, 2015 at 12:35:49PM +0300, Peter Ujfalusi wrote:
> +int omap_dmaxbar_init(void)
> +{
> + return platform_driver_register(_dma_xbar_driver);
> +}
> +arch_initcall(omap_dmaxbar_init);
All looks fine except this bit, I think I did point out this last time as
well, though dont
On 04/30/2015 11:10 AM, Krzysztof Kozlowski wrote:
> On 28.04.2015 17:40, Chanwoo Choi wrote:
>> On Tue, Apr 28, 2015 at 12:43 PM, Krzysztof Kozlowski
>> wrote:
>>> On 27.04.2015 21:31, Chanwoo Choi wrote:
This patchset alter the unused name of external connector (jig/dock/MHL)
as
* Guenter Roeck wrote:
> On 05/02/2015 12:00 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.19.7 release.
> >There are 177 patches in this series, all will be posted as a response
> >to this one. If anyone has any issues with these being applied, please
Hi,
I am experimenting a rc.sysinit without udev.
Only creating /dev with mount -t devtmpfs dev /dev
It also mounts /proc and /sys and /tmp and /var .
So the kernel boots up loading a lot of hardware, but some important
modules are not loaded , like sound, network and video.
I am not sure how to
2015-05-04 13:28 GMT+09:00 :
> From: Dinh Nguyen
>
> Turn on the clock to the PL330 DMA if there is a clock node provided.
Why? There is no explanation in the patch for this important question - why?
Amba bus already does this and provide a wrapper function.
Additionally that would mess up
Hi,
during boot up, I am trying to find where the kernel takes more time
to do actions (is slower ?).
I looked at dmesg and found some places where it takes more time, but
not sure if this is normal :
[0.070964] smpboot: CPU0: AMD Athlon(tm) 7750 Dual-Core Processor
(fam: 10, model: 02,
On Sat, May 02, 2015 at 09:57:10AM +0200, Nicholas Mc Guire wrote:
> CodingStyle fix only - align function parameters to opening (.
>
This doesnt look any better to me...
--
~Vinod
> Signed-off-by: Nicholas Mc Guire
> ---
>
> Patch was compile tested with ap325rxa_defconfig (implies
>
Dear Lee,
This patch includes the documentation about extcon-arizona.c.
How are we apply this patch to either mfd git or extcon git?
Thanks,
Chanwoo Choi
On 05/04/2015 01:42 PM, Inha Song wrote:
> This patch add device tree bindings for the pdata needed to configure
> the Accessory Detect Mode
On Sun, May 03, 2015 at 10:33:43PM +0300, Laurent Pinchart wrote:
> Hi Nicholas,
>
> Thank you for the patch.
>
> On Saturday 02 May 2015 09:57:08 Nicholas Mc Guire wrote:
> > shdma_tx_submit() called via dmaengine_submit() returns the assigned
> > cookie but this is not used here so the
On 05/04/2015 01:42 PM, Inha Song wrote:
> This patch add support for select accessory detect mode to HPDETL or HPDETR.
> Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
> to measure the impedance of an external load connected to the headphone.
>
> Depending on board
On Fri, Apr 24, 2015 at 02:42:03PM +0100, Al Viro wrote:
> That avoids this spin_lock() on each absolute symlink at the price of extra
> 32 bits in struct nameidata. It looks like doing on-demand reallocation
> of nd->stack is the right way to go anyway, so the pressure on nameidata size
> is
On Mon, 2015-05-04 at 12:39 +0800, Zefan Li wrote:
> >> We are moving toward unified hierarchy where all the cgroup controllers
> >> are bound together, so it would make cgroups easier to use if we have less
> >> restrictions on attaching tasks between cgroups.
> >
> > Forcing group scheduling
This set of patches adds support for select accessory detect mode to HPDETL or
HPDETR.
Changes in v5:
- Rebased on extcon-next branch.
Changes in v4:
- Set the hpdet_channel default value to HPDETL in variable declaration.
- Fix the indentation in binding documentation.
Changes in v3:
This patch add support for select accessory detect mode to HPDETL or HPDETR.
Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
to measure the impedance of an external load connected to the headphone.
Depending on board design, headphone detect pins can change to HPDETR
On Sun, 2015-05-03 at 18:45 -0700, Linus Torvalds wrote:
> On Sat, May 2, 2015 at 2:46 AM, Abelardo Ricart III
> wrote:
> > endif
> >
> > -signing_key.priv signing_key.x509: x509.genkey
> > +signing_key.priv signing_key.x509: | x509.genkey
>
> Hmm. Thinking some more about this, I'm not
This patch add device tree bindings for the pdata needed to configure
the Accessory Detect Mode select when Headphone detection.
Signed-off-by: Inha Song
Acked-by: Lee Jones
Acked-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++
1 file changed, 6
On 05/03/2015 12:49 PM, Guenter Roeck wrote:
On 05/02/2015 12:03 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.77 release.
There are 65 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being
On 2015/5/4 11:13, Mike Galbraith wrote:
> On Mon, 2015-05-04 at 08:54 +0800, Zefan Li wrote:
>> It's allowed to promote a task from normal to realtime after it has been
>> attached to a non-root cgroup, but it will fail if the attaching happens
>> after it has become realtime. I don't see how
From: Dinh Nguyen
Turn on the clock to the PL330 DMA if there is a clock node provided.
Signed-off-by: Dinh Nguyen
---
drivers/dma/pl330.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index 0e1f567..82eb641 100644
--- a/drivers/dma/pl330.c
On Sun, 2015-05-03 at 23:42 +0200, Jiri Kosina wrote:
> Hi,
>
> so over a past few days, I tried to perform a bisect, but failed as
> expected. The issue is not reliably enough reproducible for me, so I ended
> up with a completely bogus commit.
>
> *However*, now that I have been following
From: Vivien Didelot
Date: Fri, 1 May 2015 10:43:52 -0400
> Add the missing unregister for the mv88e6352_switch_driver.
>
> Signed-off-by: Vivien Didelot
Applied, thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Sometimes, on x86_64, decompression fails with the following
error:
Decompressing Linux...
Decoding failed
-- System halted
This condition is not needed for a 64bit kernel(from commit d5e7caf):
if( ... ||
(op + COPYLENGTH) > oend)
goto _output_error
macro LZ4_SECURE_COPY() tests op
I just upgraded one of my systems from 4.0.0 to 4.0.1, and
discovered that it would no longer boot. I tried recompiling
my kernel, to see if I had somehow corrupted it, but I got the
same results. After searching google for a bit, I discovered
the discussion here:
Re: [PATCHv2] lz4: fix system
Fix the indentations using tabs instead of spaces to align our code.
Signed-off-by: Junling Zheng
---
arch/arm/mach-hisi/Kconfig | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-hisi/Kconfig b/arch/arm/mach-hisi/Kconfig
index 83061ad..a12b764 100644
Replace a few spaces with tabs in mach-hisi to keep the code style.
Signed-off-by: Junling Zheng
---
arch/arm/mach-hisi/hotplug.c | 4 ++--
arch/arm/mach-hisi/platsmp.c | 10 +-
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/arm/mach-hisi/hotplug.c
From: Paul Gortmaker
Date: Thu, 30 Apr 2015 21:47:42 -0400
> This file is built off of a tristate Kconfig option and also contains
> modular function calls so it should explicitly include module.h to
> avoid compile breakage during header shuffles done in the future.
>
> Cc: Giuseppe Cavallaro
On 05/04/15 at 11:06am, Li, ZhenHua wrote:
> Hi baoquan,
> Could you paste the kernel log of the first kernel ?
Please check the attachment.
[0.00] microcode: CPU0 microcode updated early to revision 0x710, date
= 2013-06-17
[0.00] Initializing cgroup subsys cpuset
[0.00]
MSI descriptors are per-irq instead of per irqchip, so move it into
struct irq_common_data.
Signed-off-by: Jiang Liu
---
include/linux/irq.h |8
include/linux/irqdesc.h |2 +-
kernel/irq/chip.c |2 +-
kernel/irq/irqdesc.c|2 +-
4 files changed, 7
Use helper function to access irq_data->msi_desc, so we could move
msi_desc from struct irq_data into struct irq_common_data later.
Signed-off-by: Jiang Liu
---
arch/ia64/kernel/msi_ia64.c |2 +-
arch/ia64/sn/kernel/msi_sn.c|2 +-
arch/powerpc/sysdev/xics/ics-opal.c |
For most cases, callers pass irq_data->irq to helper function
__irq_set_chip_handler_name_locked() and then it looks up irq_data again
by calling irq_get_irq_data(irq).
So pass irq_data directly instead of irq_data->irq to
__irq_set_chip_handler_name_locked().
Signed-off-by: Jiang Liu
---
On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
> On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
> > On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
> > > On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
> > > > On Tue, Apr 28, 2015 at
The field 'affinity' in irq_desc won't change once the irq_desc data
structure is created. So cache irq_desc->affinity instead of irq_desc.
This also helps to hide struct irq_desc from device drivers.
Signed-off-by: Jiang Liu
---
drivers/net/ethernet/mellanox/mlx4/en_cq.c |6 +++---
Irq affinity mask is per-irq instead of per irqchip, so move it into
struct irq_common_data.
Signed-off-by: Jiang Liu
---
include/linux/irq.h | 12 ++--
kernel/irq/irqdesc.c |9 +
kernel/irq/manage.c | 12 ++--
kernel/irq/proc.c|2 +-
4 files changed,
This patch implements the notify entry defined in hc_driver for xHC
driver. For HCD_MSG_DEV_SUSPEND message, it will issue stop endpoint
command for each endpoint in the device. The Suspend(SP) bit in the
command TRB will be set, which gives xHC a hint about the suspend.
For HCD_MSG_DEV_RESUME, it
There is no need to call xhci_stop_device() and xhci_ring_device() in
hub control and bus suspend functions since all device suspend and
resume have been notified through the new notify entry in hc_driver.
Signed-off-by: Lu Baolu
---
drivers/usb/host/xhci-hub.c | 47
This patch adds a new entry pointer in hc_driver. With this new entry,
USB core can notify host driver when something happens and host driver
is willing to be notified. One use case of this interface comes from
xHCI compatible host controller driver.
The xHCI spec is designed to allow an xHC
This patch adds a new entry pointer in hc_driver. With this new entry,
USB core can notify host driver when something happens and host driver
is willing to be notified. One use case of this interface comes from
xHCI compatible host controller driver.
The xHCI spec is designed to allow an xHC
The field affinity in struct irq_data is type of cpumask_var_t, so
we should pass in data->affinity instead of >affinity when
calling cpumask_().
Signed-off-by: Jiang Liu
---
arch/mn10300/kernel/irq.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Handler data (handler_data) is per-irq instead of per irqchip, so move
it into struct irq_common_data.
Signed-off-by: Jiang Liu
---
arch/sparc/kernel/irq_64.c| 15 +--
arch/sparc/kernel/sun4d_irq.c |4 ++--
arch/sparc/kernel/sun4m_irq.c |6 --
NUMA is enabled by CONFIG_NUMA instead of CONFIG_SMP, so use CONFIG_NUMA
to guard irq_common_data.node.
Signed-off-by: Jiang Liu
---
include/linux/irq.h |4 ++--
kernel/irq/irqdesc.c |4 +++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/include/linux/irq.h
NUMA node information is per-irq instead of per-irqchip, so move it into
struct irq_common_data.
Signed-off-by: Jiang Liu
---
arch/sh/kernel/irq.c |2 +-
arch/x86/kernel/apic/vector.c |8
arch/x86/platform/uv/uv_irq.c |2 +-
include/linux/irq.h | 20
On Mon, 2015-05-04 at 08:54 +0800, Zefan Li wrote:
> It's allowed to promote a task from normal to realtime after it has been
> attached to a non-root cgroup, but it will fail if the attaching happens
> after it has become realtime. I don't see how this restriction is useful.
In the
With introduction of hierarchy irqdomain, struct irq_data becomes
per-chip instead of per-irq and there may be multiple irq_datas
associated with the same irq. Some per-irq data stored in
struct irq_data now may get duplicated into multiple irq_datas,
and causes inconsistent view.
So introduce
Hi all,
Now the irq core supports hierarchy irq and stacked irqchips,
so there may be multiple irq_datas associated with the same irq. But
some fields in struct irq_data are per-irq instance and duplicating
those fields into multiple irq_data may cause troubles.
So this patch
Hi all,
Changes since 20150501:
Removed tree: virtio (maintainer moved on)
The akpm-current tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1436
1426 files changed, 81272 insertions(+), 32795 deletions(-)
Hi baoquan,
Could you paste the kernel log of the first kernel ?
Thanks
Zhenhua
On 05/03/2015 04:55 PM, Baoquan He wrote:
On 04/29/15 at 07:20pm, Baoquan He wrote:
Bad news, I rebuilt a kernel with your patchset on 4.0.0+ (this commit
f614c81). Now dmar fault is seen again.
The lspci log and
The hypervisor continues assuming that vcpu_info is stored in per-cpu data
which was set up by xen_vcpu_setup(),
while on canceled suspend, the call to xen_hvm_init_shared_info() will now make
the guest think that vcpu_info
is in the shared page, so we do not call xen_hvm_init_shared_info() on
It was introduced in commit f2ca09f381a59
(ARM: 8311/1: Don't use is_module_addr in setting page attributes)
We have no need to check start twice, but see if end is also in range.
Signed-off-by: Hillf Danton
Acked-by: Laura Abbott
---
--- a/arch/arm/mm/pageattr.cMon May 4 10:33:49 2015
On NUMA systems, an IO device may be associated with a NUMA node.
It may improve IO performance to allocate resources, such as memory
and interrupts, from device local node.
This patch introduces a mechanism to support CPU vector allocation
policies, so users may choose the best suitable CPU
Commit b106ee63abcc ("irq_remapping/vt-d: Enhance Intel IR driver to
support hierarchical irqdomains") caused a regression, which forgot
to initialize remapping data structures other than the first entry
when setting up remapping entries for multiple MSIs.
Code is written by Thomas and commit
Hi all,
This is a small patch set based on tip/x86/apic.
This first patch is a bugfix for tip/x86/apic. And the second patch
is an enhancement to optimize CPU vector allocation on NUMA systems.
It introduces a mechanism to allocate CPU vectors from device local
NUMA node and a kernel
So the -rc2's have lately been pretty small - looking more like late
-rc's than early ones. It *used* to be that I couldn't even post the
shortlog, because it was just too big. That's not been the case for
the last few releases.
I think people tend to take a breather after the merge window,
On Tue, 2015-04-28 at 23:37 +0200, Frans Klaver wrote:
> On Thu, Apr 16, 2015 at 01:27:14PM +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > commit 6b44d910ae7de5316fcf1fc828ff4a8d48cac5e2 ("mtd:
Hi all,
I've decided to try and put more effort into testing on physical machines, but
couldn't
even get the box to boot :(
[0.00] page:ea04 count:0 mapcount:1 mapping:
(null) index:0x0
[0.00] flags: 0x0()
[0.00] page dumped because:
On Mon, May 04, 2015 at 11:20:08AM +0900, Minchan Kim wrote:
> Hello Sergey,
>
> On Thu, Apr 30, 2015 at 03:51:12PM +0900, Sergey Senozhatsky wrote:
> > On (04/30/15 15:44), Minchan Kim wrote:
> > > > > I think the problem of deadlock is that you are trying to remove
> > > > > sysfs file
> > > >
On 2015.5.2 2:55, Boris Ostrovsky wrote:
> On 04/30/2015 03:27 AM, Ouyang Zhaowei (Charles) wrote:
>>
>> On 2015.4.29 5:31, Boris Ostrovsky wrote:
>>> On 04/28/2015 08:30 AM, Ouyang Zhaowei (Charles) wrote:
On 2015.4.26 7:31, Boris Ostrovsky wrote:
> On 04/24/2015 05:30 AM, Ouyang
Hello Sergey,
On Thu, Apr 30, 2015 at 03:51:12PM +0900, Sergey Senozhatsky wrote:
> On (04/30/15 15:44), Minchan Kim wrote:
> > > > I think the problem of deadlock is that you are trying to remove sysfs
> > > > file
> > > > in sysfs handler.
> > > >
> > > > #> echo 1 > /sys/xxx/zram_remove
> >
Quark X1000 SoC contains a 512 KiB embedded SRAM (eSRAM) memory that can
be mapped onto an area of DRAM in block or on per-page overlay mode where a
4 KiB aligned region can be overlayed - allowing for broken up mappings
with a 4 KiB individual granularity.
eSRAM has access times similar to an L1
Quark X1000 contains an embedded SRAM (eSRAM) a fast access SRAM. This code
is a self-test routine to measure the performance of that SRAM for
different read-values. The tests are designed the performance gains
provided by eSRAM using different read-sizes and comparing the performance
of eSRAM
Quark X1000 ships with 512 KiB of embedded SRAM (eSRAM) a low-latency
memory with access times similar to an L1 cache. eSRAM is used during the
initial bootstrap phases of EFI firmware, this driver provides a gen_pool
interface to eSRAM to allow drivers to make use of eSRAM for fast-access
On Thu, 2015-04-30 at 21:12 +0100, Mark Brown wrote:
> On Wed, Apr 22, 2015 at 11:17:20AM +0800, Koro Chen wrote:
>
> > If using DPCM, it seems the most suitable FE DAIs will be memif, and
> > external interface like I2S should be BE DAIs. Do you think it is
> > suitable for our memif to be FE
On 02.05.2015 03:46, Stephen Boyd wrote:
On 04/28, Krzysztof Kozlowski wrote:
Fix the indentation - spaces used instead of tabs and actually wrong
number of spaces.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/tegra/clk-emc.c | 16
1 file changed, 8 insertions(+), 8
On Sat, May 2, 2015 at 2:46 AM, Abelardo Ricart III wrote:
> endif
>
> -signing_key.priv signing_key.x509: x509.genkey
> +signing_key.priv signing_key.x509: | x509.genkey
Hmm. Thinking some more about this, I'm not entirely convinced.
With this change, if we change kernel/Makefile to have a
The following changes since commit 6ddb2447846a8ece111e316a2863c2355023682d:
ext4 crypto: enable encryption feature flag (2015-04-16 01:56:00 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/for_linus_stable
for you to fetch
Hi Octavian,
On 04/27/2015 07:23 PM, Octavian Purdila wrote:
On Tue, Apr 28, 2015 at 12:57 AM, sathyanarayanan kuppuswamy
wrote:
Hi
On 04/27/2015 08:54 AM, Octavian Purdila wrote:
On Mon, Apr 27, 2015 at 6:42 PM, Kuppuswamy Sathyanarayanan
wrote:
Since Acpi framework already exports this
It's allowed to promote a task from normal to realtime after it has been
attached to a non-root cgroup, but it will fail if the attaching happens
after it has become realtime. I don't see how this restriction is useful.
We are moving toward unified hierarchy where all the cgroup controllers
are
On Thu, Apr 30, 2015 at 12:33:03PM -0400, Steven Rostedt wrote:
> Running a test on a large CPU count box with xfs, I hit a live lock
> with the following backtraces on several CPUs:
>
> Call Trace:
> [] __const_udelay+0x28/0x30
> [] xfs_icsb_lock_cntr+0x2a/0x40 [xfs]
> []
Hi, Andrew,
Sorry for late. I am in vacation in last week.
On Fri, 2015-04-24 at 10:42 -0700, Andrew Morton wrote:
> On Thu, 23 Apr 2015 14:25:38 +0800 Huang Ying wrote:
>
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
The check was needed only when we supported modular cgroup subsystem.
Signed-off-by: Zefan Li
---
block/blk-cgroup.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
index 0ac817b..92b7edd 100644
--- a/block/blk-cgroup.c
+++
Borislav,
On 2015/5/3 17:37, Borislav Petkov wrote:
On Fri, May 01, 2015 at 02:03:48PM +0800, Ethan Zhao wrote:
For the record, it is a public secret that CPU hotplug is broken. IOW,
you're wasting your time with those senseless pounder tests but ok.
:<, Someone else is stressing the CPU
On 05/02/2015 11:58 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.0.2 release.
There are 220 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 05/02/2015 12:00 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.19.7 release.
There are 177 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Add self as maintainer for the new driver.
Signed-off-by: Kevin Cernekee
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ea0001760035..15153fc37cc4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9878,6 +9878,12 @@ L:
Document the bindings for the soon-to-be-added tas571x driver.
Signed-off-by: Kevin Cernekee
---
.../devicetree/bindings/sound/tas571x.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/tas571x.txt
diff --git
Introduce a new codec driver for the Texas Instruments
TAS5711/TAS5717/TAS5719 power amplifier chips. These chips are typically
used to take an I2S digital audio input and drive 10-20W into a pair of
speakers.
Signed-off-by: Kevin Cernekee
---
sound/soc/codecs/Kconfig | 5 +
Existing regmap users call regcache_mark_dirty() as part of the
suspend/resume sequence, to tell regcache that non-default values need to
be resynced post-resume. Add an internal "no_sync_defaults" regmap flag
to remember this state, so that regcache_sync() can differentiate between
these two
V2->V3:
Revert earlier changes to the regcache APIs.
Change regcache_sync() so that regcache_mark_dirty() is used to indicate
that the HW was reset. This allows tas571x (which does NOT call
regcache_mark_dirty()) to use regcache_sync() to write back any register
changes that occurred while in
These patches cleanup the driver from some no longer needed
functions, renames hci_{read, write}1 functions and also some comment
blocks were changed.
Azael Avalos (3):
toshiba_acpi: Remove no longer needed hci_{read, write}2 functions
toshiba_acpi: Rename hci_{read, write}1 functions
These patches add support to use the rfkill core functionality to the
Toshiba bluetooth driver and adapting the existing code to it.
Changes since v1:
- Merged patches two and six to avoid a broken dependency
- Merged patches three and four
- The debug message is now printed in one line instead
This patch simply renames the hci_{read, write}1 functions to
hci_{read, write}.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_acpi.c | 44 ++---
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/drivers/platform/x86/toshiba_acpi.c
This patch removes some blank lines after comment blocks, capitalizes
some comments first words and adds a few comments to the beggining
of some functions.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_acpi.c | 31 +--
1 file changed, 17 insertions(+),
This patch removes the hci_{read, write}2 functions from the driver,
and the toshiba_hotkey_event_type_get function was adapted to use the
tci_raw function.
The hci_write2 function was only used by the bluetooth rfkill code,
but since its removal, it was causing build warnings, and the
hci_read2
The function toshiba_bluetooth_status is currently printing the
status of the device whenever it is queried, but since the
introduction of the rfkill poll code, this value will get printed
everytime the poll occurs.
This patch removes the status message from the *_status function, and
adds a
This patch adds a struct named toshiba_bluetooth_dev, which will be
used to contain the acpi_device struct and bluetooth status booleans.
This struct will also be used by later patches to store the rfkill
struct as well.
Also, a helper function named toshiba_bluetooth_sync_status was added
to be
This patch adapts toshiba_bluetooth_enable, toshiba_bt_rfkill_notify
and toshiba_bt_resume functions to rfkill.
The *_enable function was cleaned from code that the rfkill code now
provides, and the other two functions were modified to update the rfkill
switch status, as they were only calling
This patch adds RFKill handler functions to the driver, allowing it
to register and update the rfkill switch status.
Also, a comment block was moved from the header to the poll function,
as it explains why we need to poll the killswitch on older devices.
Signed-off-by: Azael Avalos
---
1 - 100 of 532 matches
Mail list logo
