Signed-off-by: Yakir Yang
---
Changes in v3:
- Combine hdmi_set_clock_regenerator_n() and hdmi_regenerate_cts()
Changes in v2: None
drivers/gpu/drm/bridge/dw_hdmi.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/bridge/dw_hdmi.c b/drivers/g
This patch changes the order to:
- write CTS3 CTS_manual = 0
- write CTS3 N_shift = 0
- write CTS3 CTS value
- write CTS2 CTS value
- write CTS1 CTS value
- write N3 N value
- write N2 N value
- write N1 N value
Signed-off-by: Yakir Yang
---
Changes in v3:
- Only adjust the n/cts setting order
C
The ncts_atomic_write & cts_manual bits are present when design id
equal to 0x20. After set the ncts_atomic_write, then the new N and
CTS values are only used when aud_n1 register is updated. After set
cts_manual bit, the new CTS value can set by AudCTS registers.
- write N3 ncts_atomic_write = 1
On 02/03/2015 11:53 AM, Zubair Lutfullah Kakakhel wrote:
On 03/02/15 10:32, Lars-Peter Clausen wrote:
On 02/03/2015 11:17 AM, Zubair Lutfullah Kakakhel wrote:
[...]
V4 Changes
Removed clock binding because of pending work in clock tree. Will add
binding later. Rather than introduce a bad bindi
On Tue, 3 Feb 2015, Daniel Sanders wrote:
> +++ b/mm/slab.c
> @@ -1440,6 +1440,7 @@ void __init kmem_cache_init(void)
> kmalloc_caches[INDEX_NODE] = create_kmalloc_cache("kmalloc-node",
> kmalloc_size(INDEX_NODE), ARCH_KMALLOC_FLAGS);
> slab_state = PARTIA
Uwe Kleine-König wrote:
> Might be a matter of taste, but this check is equivalent to
>
> *p != (*p | mask)
>
> which is what you really want to test for.
I would argue that this is less clear as to what's going on.
David
--
To unsubscribe from this list: send the line "unsubscribe linu
Correctly rollback state if the failure occurs after we have handed over
the ownership of the buffer to the host.
Signed-off-by: K. Y. Srinivasan
Cc: sta...@vger.kernel.org
---
drivers/hv/channel.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/hv/channel.
On Mon, 2 Feb 2015, Andy Lutomirski wrote:
> How many of you will be at LSF/MM? This might be a decent topic.
I will be there for the mm portion and can talk about this if you want.
But note my limited knowledge about security issues.
--
To unsubscribe from this list: send the line "unsubscribe
When transmitting IEC60985 linear PCM audio, we configure the
Aduio Sample Channel Status information of all the channel
status bits in the IEC60958 frame.
(am from https://patchwork.kernel.org/patch/5749101/)
Signed-off-by: Yakir Yang
---
Changes in v3:
- Determine whether sample channel should
This patch removes the sparse warnings present in the lproc_lmv.c
Signed-off-by: Mohammad Jamal
---
drivers/staging/lustre/lustre/lmv/lproc_lmv.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lustre/lmv/lproc_lmv.c
b/drivers/staging/lustre/lus
> What's the answer? Easy and obvious, just (try to) overwrite the contents
> of a file by request from userspace. Filesystems do know where on the
> storage they have written the contents to, so why not just let them delete
> that stuff themself instead? It's almost unbelievable that this was not
If the monitor support audio, so we should support audio for it, even if
the display resolution is No-CEA mode.
Signed-off-by: Yakir Yang
---
Changes in v3: None
Changes in v2:
- enable audio support for No-CEA display mode
drivers/gpu/drm/bridge/dw_hdmi.c | 10 +-
1 file changed, 5 ins
Add more n/cts values, in that case we can support audio for more
display resolutions (128 * SampleRate = PixelClock * N / CTS).
Signed-off-by: Yakir Yang
---
Changes in v3: None
Changes in v2:
- add more n/cts combinations for more display resolutions
drivers/gpu/drm/bridge/dw_hdmi.c | 58
codec driver creat an standard alsa device, than config audio
and report jack status through some callback interfaces that
dw_hdmi driver support.
Signed-off-by: Yakir Yang
---
Changes in v3:
- Keep audio format config function in dw-hdmi-audio driver
and remove audio_config & get_connect_statu
Add audio clock enable/disable/restore interfacess, those functions
can be called concurrently on multiple different threads of execution
to change the hdmi audio enable state.
Signed-off-by: Yakir Yang
---
Changes in v3:
- Delete hdmi_audio_config interface and modify audio clock control functio
On Tue, Feb 03, 2015 at 08:45:02PM +0530, Mohammad Jamal wrote:
> This patch removes the sparse warnings present in the lproc_lmv.c
What "sparse warnings"? Please be specific.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.k
On Mon, 2 Feb 2015, Andy Lutomirski wrote:
> None of this could address the problem here, though: if I hold a
> capability and I want to pass that capability to an exec'd helper, I
> shouldn't need the fs's help to do this.
Amen!
--
To unsubscribe from this list: send the line "unsubscribe linux-
creat dw-hdmi-audio device dynamically in probe function,
and transfer some interfaces to dw-hdmi-audio driver for
setting hdmi audio format & control hdmi audio clock.
Signed-off-by: Yakir Yang
---
Changes in v3:
- Remove audio_config & get_connect_status callback functions
and add write/read/
Required properties:
- compatible: platform specific
- i2s-controller: the i2s controller device node
Signed-off-by: Yakir Yang
---
Changes in v3:
- modify cpu-of-node to i2s-controller
Changes in v2:
- remove codec-name and codec-dai-name
- rename rockchip,rockchip-hdmi-audio.txt to rockchip,ro
On Tue 03-02-15 11:16:00, Mel Gorman wrote:
> On Tue, Feb 03, 2015 at 09:19:15AM +0100, Vlastimil Babka wrote:
[...]
> > And if we agree that there is indeed no guarantee, what's the actual
> > semantic
> > difference from MADV_FREE? I guess none? So there's only a possible
> > perfomance
> > dif
Add a sound driver that combines rockchip-i2s cpu_dai and dw-hdmi-codec
as codec_dai to provide hdmi audio output on rk3288 platforms.
Signed-off-by: Yakir Yang
---
Changes in v3:
- Delete the operation of jack in rockchip-hdmi-audio driver,
get ready to switch to simple-audio-card driver.
Cha
On Tue, Feb 3, 2015 at 9:41 AM, Russell King - ARM Linux
wrote:
> On Tue, Feb 03, 2015 at 03:17:27PM +0100, Arnd Bergmann wrote:
>> On Tuesday 03 February 2015 09:04:03 Rob Clark wrote:
>> > Since I'm stuck w/ an iommu, instead of built in mmu, my plan was to
>> > drop use of dma-mapping entirely
On Tue, Feb 03, 2015 at 03:52:48PM +0100, Arnd Bergmann wrote:
> On Tuesday 03 February 2015 14:41:09 Russell King - ARM Linux wrote:
> > I'd go as far as saying that the "DMA API on top of IOMMU" is more
> > intended to be for a system IOMMU for the bus in question, rather
> > than a device-level
Hi Michal,
On 02/03/2015 05:01 AM, Michal Simek wrote:
> Add one more checking condition which was originally added by:
> "tty: serial: 8250_core: use the ->line argument as a hint in
> serial8250_find_match_or_unused()"
> (sha1: 59b3e898ddfc81a65975043b5eb44103cc29ff6e)
>
> port->line can be set
On Mon, 2 Feb 2015, Serge Hallyn wrote:
> A key concept behind posix capabilities is that the privilege comes from
> both the person and the file being executed. As you say below basically
> anything can be executed by the program so that is completely violated.
Well this patch does not change t
Am 03.02.2015 um 16:13 schrieb Alexander Holler:
Am 03.02.2015 um 15:50 schrieb Alexander Holler:
Maybe I should request removal of shred from Fedora/RH instead.
According to you it's one of the most misleading and useless tools. So
why still confuse people with it and still ship it?
At least
This patch adds a static keyword to lprocfs_lmv_init_vars and
lprocfs_lmv_module_vars to suppress the sparse warnings about
static declaration
Signed-off-by: Mohammad Jamal
---
drivers/staging/lustre/lustre/lmv/lproc_lmv.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
* Tero Kristo [150203 00:49]:
> On 02/03/2015 09:03 AM, Tomeu Vizoso wrote:
> >
> >I think you got it right, just wanted to mention that we can and
> >probably should make the clk_get_parent_* calls in the consumer API to
> >return per-user clk instances but that we need to make sure first that
>
On Tue, Feb 03, 2015 at 02:27:28PM +, Al Viro wrote:
> On Tue, Feb 03, 2015 at 12:10:44PM +0200, Michael S. Tsirkin wrote:
>
> > Hmm does copy_from_iter actually modify the iovec?
> > If so, won't this break aio on tun/macvtap, by
> > reversing the effect of
> > commit 6f26c9a7555e5bcca3560919
On Tue, Feb 3, 2015 at 9:52 AM, Arnd Bergmann wrote:
> On Tuesday 03 February 2015 14:41:09 Russell King - ARM Linux wrote:
>> On Tue, Feb 03, 2015 at 03:17:27PM +0100, Arnd Bergmann wrote:
>> > On Tuesday 03 February 2015 09:04:03 Rob Clark wrote:
>> > > Since I'm stuck w/ an iommu, instead of bu
NetworkDirect is a service that supports guest RDMA. Define the GUID for this
service.
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c |2 ++
include/linux/hyperv.h| 10 ++
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel_mgmt.c b
On 02/02/15 at 08:42am, H. Peter Anvin wrote:
> On 01/20/2015 07:37 PM, Baoquan He wrote:
> >
> >Leftover problem:
> > hpa want to see the physical randomization can cover the whole physical
> > memory. I
> >checked code and found it's hard to do. Because in
> >arch/x86/boot/compressed/head_6
On Tue, Feb 03, 2015 at 01:03:37PM +, Javi Merino wrote:
> On Mon, Feb 02, 2015 at 11:51:20PM +, Lina Iyer wrote:
> > On Wed, Jan 28 2015 at 14:42 -0700, Javi Merino wrote:
> > >The power allocator governor is a thermal governor that controls system
> > >and device power allocation to contr
On Tuesday 03 February 2015 15:22:05 Russell King - ARM Linux wrote:
> On Tue, Feb 03, 2015 at 03:52:48PM +0100, Arnd Bergmann wrote:
> > On Tuesday 03 February 2015 14:41:09 Russell King - ARM Linux wrote:
> > > I'd go as far as saying that the "DMA API on top of IOMMU" is more
> > > intended to b
On 02/03/2015 12:58 AM, David Drysdale wrote:
> On Tue, Feb 3, 2015 at 3:53 AM, Michael Ellerman wrote:
>> On systems which don't implement sys_execveat(), this test produces a
>> lot of output.
>>
>> Add a check at the beginning to see if the syscall is present, and if
>> not just note one error
Hi Michal,
On 3 February 2015 at 16:05, Michal Hocko wrote:
> Hi,
> while debugging an unexpected ENOMEM from fork (there was no memory
> pressure and OVERCOMMIT_ALWAYS) I have found out that fork returns
> ENOMEM even when not short on memory.
>
> In this particular case it was due to depleted
This patch series introduces in the first change a new UFS ioctl,
allowing user-space to send UFS queries and retrieve information from them.
In addition, the other three patches add utilities to support debugging
efforts and supply information that will help analysis of issue:
UFS trace events, du
From: Dolev Raviv
This patch exposes the ioctl interface for UFS driver via SCSI device
ioctl interface. As of now UFS driver would provide the ioctl for query
interface to connected UFS device.
Signed-off-by: Dolev Raviv
Signed-off-by: Noa Rubens
Signed-off-by: Raviv Shvili
Signed-off-by: Ya
On 02.02.2015 13:45, Hanjun Guo wrote:
From: Tomasz Nowicki
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
abstraction agnostic). In
Add trace events to driver to allow monitoring and profilig
of activities such as PM suspend/resume, hibernate enter/exit,
clock gating and clock scaling up/down.
In addition, add UFS host controller register dumps to provide
detailed information in case of errors to assist in analysis
of issues.
On Tue, Feb 03, 2015 at 07:34:01PM +0530, Sudip Mukherjee wrote:
> On Tue, Feb 03, 2015 at 02:44:28PM +0600, Max Perepelitsyn wrote:
> > This symbol is never used anywhere else besides sm7xxfb.c
>
> Hi Greg,
> do i need to do anything about this patch? maybe a tested-by or reviewed-by?
If you tes
From: Sujit Reddy Thumma
Use fault-injection framework to simulate error conditions
in the controller and verify error handling mechanisms
implemented in UFS host controller driver.
This is used only during development and hence
guarded by CONFIG_UFS_FAULT_INJECTION debug config option.
Signed-
From: Lee Susman
Adding debugfs capability for ufshcd.
debugfs attributes introduced in this patch:
- View driver/controller runtime data
- Command tag statistics for performance analisis
- Dump device descriptor info
- Track recoverable errors statistics during runtime
- Change UFS power m
On 2/3/2015 7:17 AM, Christoph Lameter wrote:
> On Mon, 2 Feb 2015, Andy Lutomirski wrote:
>
>> None of this could address the problem here, though: if I hold a
>> capability and I want to pass that capability to an exec'd helper, I
>> shouldn't need the fs's help to do this.
> Amen!
>
That's compl
Hello,
On Wed, Feb 04, 2015 at 12:06:24AM +0900, Sergey Senozhatsky wrote:
> On (02/03/15 23:52), Sergey Senozhatsky wrote:
> > On (02/03/15 23:15), Sergey Senozhatsky wrote:
> > > > How about keep this here? Protected by zram->init_lock.
> > > >set_capacity(zram->disk, 0);
> > >
> >
On Tue, Feb 3, 2015 at 10:17 AM, Davidlohr Bueso wrote:
> On Mon, 2015-02-02 at 11:00 -0800, Linus Torvalds wrote:
>> Hmm. I don't disagree, but would like some more feedback.
>>
>> Davidlohr - you were the person to touch this function last (commit
>> 30493cc9dddb: "lib/int_sqrt.c: optimize squar
On Tue, 3 Feb 2015, Alexander Holler wrote:
> Date: Tue, 03 Feb 2015 15:50:53 +0100
> From: Alexander Holler
> To: Lukáš Czerner
> Cc: linux-fsde...@vger.kernel.org, linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 3/5] WIP: fs: ext4: support unlinkat_s() for secure
> deletion of files
>
Am 03.02.2015 um 16:15 schrieb One Thousand Gnomes:
What's the answer? Easy and obvious, just (try to) overwrite the contents
of a file by request from userspace. Filesystems do know where on the
storage they have written the contents to, so why not just let them delete
that stuff themself instea
Am 03.02.2015 um 16:41 schrieb Lukáš Czerner:
I'll give up.
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.
> -Original Message-
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Monday, February 2, 2015 1:49 AM
> >> btw, I find during netvsc_start_xmit(), ret was change to -ENOSPC
> >> when
> >> queue_sends[q_idx] < 1. But non of the caller check -ENOSPC in fact?
> >
> > In this case,
Hi, Mark
On 02/03/2015 04:58 PM, Mark Salter wrote:
On Wed, 2015-01-28 at 14:39 +0200, Ivan Khoronzhuk wrote:
Some utils, like dmidecode and smbios, needs to access SMBIOS entry
table area in order to get information like SMBIOS version, size, etc.
Currently it's done via /dev/mem. But for situ
Hello,
On Tue, Feb 03, 2015 at 03:26:28AM +, Petr Cermak wrote:
> On Mon, Jan 26, 2015 at 04:00:20PM -0800, David Rientjes wrote:
> > [...]
> > This is a result of allowing something external (process B) be able to
> > clear hwm so that you never knew the value went to 100MB. That's the
> > d
On 02/03/2015 04:00 PM, Joonsoo Kim wrote:
> 2015-02-03 18:05 GMT+09:00 Vlastimil Babka :
>> On 02/03/2015 07:49 AM, Joonsoo Kim wrote:
>>> On Mon, Jan 19, 2015 at 11:05:15AM +0100, Vlastimil Babka wrote:
>>>
>>> Hello,
>>>
>>> I don't have any elegant idea, but, have some humble opinion.
>>>
>>> T
Quoting Andy Lutomirski (l...@amacapital.net):
> On Mon, Feb 2, 2015 at 10:08 AM, Serge Hallyn wrote:
> > Quoting Casey Schaufler (ca...@schaufler-ca.com):
> >> I'm game to participate in such an effort. The POSIX scheme
> >> is workable, but given that it's 20 years old and hasn't
> >> developed
On Tue 03-02-15 16:33:03, Michael Kerrisk wrote:
> Hi Michal,
>
>
> On 3 February 2015 at 16:05, Michal Hocko wrote:
> > Hi,
> > while debugging an unexpected ENOMEM from fork (there was no memory
> > pressure and OVERCOMMIT_ALWAYS) I have found out that fork returns
> > ENOMEM even when not sho
On Thu, 29 Jan 2015 15:40:33 -0800
Linus Torvalds wrote:
> On Wed, Jan 28, 2015 at 8:11 PM, Dave Airlie wrote:
> >
> > Linus, this came up a while back I finally got some confirmation
> > that it fixes those servers.
>
> I'm certainly ok with this. which way should it go in? The users are:
>
>
On Tue, Feb 03, 2015 at 04:31:13PM +0100, Arnd Bergmann wrote:
> On Tuesday 03 February 2015 15:22:05 Russell King - ARM Linux wrote:
> > Don't we already have those in the DMA API? dma_sync_*() ?
> >
> > dma_map_sg() - sets up the system MMU and deals with initial cache
> > coherency handling. D
On Tue, Feb 3, 2015 at 10:11 AM, Davidlohr Bueso wrote:
> On Mon, 2015-02-02 at 11:13 -0800, Linus Torvalds wrote:
>> IOW, instead of
>>
>> m = 1UL << (BITS_PER_LONG - 2);
>>
>> perhaps something like
>>
>>m = 1UL << (BITS_PER_LONG/2- 2);
>>if (m < x)
>>m <<= BITS_PER_LONG/2;
On
Quoting Christoph Lameter (c...@linux.com):
> On Mon, 2 Feb 2015, Serge Hallyn wrote:
>
> > A key concept behind posix capabilities is that the privilege comes from
> > both the person and the file being executed. As you say below basically
> > anything can be executed by the program so that is c
When L2 is using x2apic, we can use virtualize x2apic mode to
gain higher performance, especially in apicv case.
This patch also introduces nested_vmx_check_apicv_controls
for the nested apicv patches.
Signed-off-by: Wincy Van
---
arch/x86/kvm/vmx.c | 114 ++
We can reduce apic register virtualization cost with this feature,
it is also a requirement for virtual interrupt delivery and posted
interrupt processing.
Signed-off-by: Wincy Van
---
arch/x86/kvm/vmx.c | 39 +++
1 files changed, 35 insertions(+), 4 deletio
Quoting Casey Schaufler (ca...@schaufler-ca.com):
> On 2/2/2015 12:37 PM, Andy Lutomirski wrote:
> > On Mon, Feb 2, 2015 at 10:08 AM, Serge Hallyn
> > wrote:
> >> Quoting Casey Schaufler (ca...@schaufler-ca.com):
> >>> I'm game to participate in such an effort. The POSIX scheme
> >>> is workable,
With virtual interrupt delivery, the hardware prevent KVM from
the low efficiency interrupt inject way. In nested vmx, it is
a important feature, we can reduce much more nested-vmexit,
especially in high throughput scenes.
Signed-off-by: Wincy Van
---
arch/x86/kvm/vmx.c | 67 ++
If vcpu has a interrupt in vmx non-root mode, we will
kick that vcpu to inject interrupt timely. With posted
interrupt processing, the kick intr is not needed, and
interrupts are fully taken care of by hardware.
In nested vmx, this feature avoids much more vmexits
than non-nested vmx.
This patch
v1 ---> v2:
Use spin lock to ensure vmcs12 is safe when doing nested
posted interrupt delivery.
v2 ---> v3:
1. Add a new field in nested_vmx to avoid the spin lock in v2.
2. Drop send eoi to L1 when doing nested interrupt delivery.
3. Use hardware MSR bitmap to enable nested virtualize x
> -Original Message-
> From: Christoph Lameter [mailto:c...@linux.com]
> Sent: 03 February 2015 15:15
> To: Daniel Sanders
> Cc: Pekka Enberg; David Rientjes; Joonsoo Kim; Andrew Morton; linux-
> m...@kvack.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/5] LLVMLinux: Correct size
Currently, if L1 enables MSR_BITMAP, we will emulate this feature,
all of L2's msr access is intercepted by L0. Since many features
like virtualize x2apic mode has a complicated logic and it is
difficult for us to emulate, we should use hardware and merge
the bitmap.
This patch introduces nested_v
Quoting Mimi Zohar (zo...@linux.vnet.ibm.com):
> On Mon, 2015-02-02 at 18:08 +, Serge Hallyn wrote:
> > Quoting Casey Schaufler (ca...@schaufler-ca.com):
> > > I'm game to participate in such an effort. The POSIX scheme
> > > is workable, but given that it's 20 years old and hasn't
> > > devel
Hello,
Julia asked me to have a look and see if I can help.
On 02/02/2015 23:50, Mike Turquette wrote:
Quoting Stephen Boyd (2015-02-02 14:35:59)
On 02/02/15 13:31, Julia Lawall wrote:
On Mon, 2 Feb 2015, Stephen Boyd wrote:
Julia,
Is there a way we can write a coccinelle script to check fo
To enable nested apicv support, we need per-cpu vmx
control MSRs:
1. If in-kernel irqchip is enabled, we can enable nested
posted interrupt, we should set posted intr bit in
the nested_vmx_pinbased_ctls_high.
2. If in-kernel irqchip is disabled, we can not enable
nested posted in
Thanks for your response.
On 01/30/2015 12:57 PM, Lukasz Stelmach wrote:
On 28.01.2015 18:28, Mark Salyzyn wrote:
- Precious little user-space content goes to kmsg (otherwise you
can ask why is there a syslogd?), there is a reason for this, user
space is notorious for containing Personal Identi
On Tue, Feb 03, 2015 at 06:21:45AM -0800, Guenter Roeck wrote:
> On 02/03/2015 03:42 AM, Mark Brown wrote:
> >Perhaps it just needs to be more explicit about how it's handling native
> >endian? I didn't spot it.
> Thinking about it, we should actually reject requests for _NATIVE. SMBus
> 16 bit
On Tuesday 03 February 2015 15:54:04 Russell King - ARM Linux wrote:
> On Tue, Feb 03, 2015 at 04:31:13PM +0100, Arnd Bergmann wrote:
> > The dma_map_* interfaces assign the virtual addresses internally,
> > using typically either a global address space for all devices, or one
> > address space per
We need to return set_capacity(disk, 0) from reset_store() back
to zram_reset_device(), a catch by Ganesh Mahendran. Potentially,
we can race set_capacity() calls from init and reset paths.
The problem is that zram_reset_device() is also getting called
from zram_exit(), which performs operations i
On 03/02/2015 16:46, Wincy Van wrote:
> v1 ---> v2:
> Use spin lock to ensure vmcs12 is safe when doing nested
> posted interrupt delivery.
>
> v2 ---> v3:
> 1. Add a new field in nested_vmx to avoid the spin lock in v2.
> 2. Drop send eoi to L1 when doing nested interrupt delivery.
>
On Mon, Feb 02, 2015 at 11:18:24PM +0100, Rafael J. Wysocki wrote:
> On Monday, February 02, 2015 08:45:33 PM Hanjun Guo wrote:
> > From: Graeme Gregory
> >
> > ACPI 5.1 does not currently support S states for ARM64 hardware but
> > ACPI code will call acpi_target_system_state() for device power
From: Markus Elfring
Date: Tue, 3 Feb 2015 16:50:07 +0100
Another update suggestion was taken into account after a patch was applied
from static source code analysis.
Markus Elfring (2):
Delete an unnecessary check before the function call "dvb_unregister_device"
Less function calls in dvb_c
hello,
On (02/04/15 00:39), Minchan Kim wrote:
> So, you mean this?
>
> reset_store
>
> down_write(&zram->init_lock);
> zram_reset_device(zram);
> set_capacity(zram->disk, 0);
> up_write(&zram->init_lock);
>
>
> If so, +1.
> Hope you send a squash patch to Andrew.
ye
On Tue, Feb 3, 2015 at 3:27 AM, Tim Sander wrote:
> Hi Bjorn
>
> Am Montag, 2. Februar 2015, 08:55:33 schrieb Bjorn Helgaas:
>> [+cc Alex]
>>
>> On Mon, Feb 2, 2015 at 5:29 AM, Tim Sander wrote:
>> > The long name for this device is
>> > Lite-On IT Corp. / Plextor M6e PCI Express SSD [Marvell 88S
__recover_probed_insn() should always be called from an address where
an instructions starts. The check for ftrace_location() might help to
discover a potential inconsistency. Something goes terribly wrong when
an address inside the ftrace location is checked. Let's BUG() in this case.
Suggested-b
Hello Vlastimil
Thanks for CCing me into this thread.
On 02/03/2015 12:42 PM, Vlastimil Babka wrote:
> On 02/03/2015 11:53 AM, Kirill A. Shutemov wrote:
>> On Tue, Feb 03, 2015 at 09:19:15AM +0100, Vlastimil Babka wrote:
>>> [CC linux-api, man pages]
>>>
>>> On 02/02/2015 11:22 PM, Dave Hansen wr
On Tue, Feb 3, 2015 at 11:12 AM, Arnd Bergmann wrote:
> I agree for the case you are describing here. From what I understood
> from Rob was that he is looking at something more like:
>
> Fig 3
> CPU--L1cache--L2cache--Memory--IOMMU-device
>
> where the IOMMU controls one or more contexts per d
On Tue, Feb 03, 2015 at 03:40:45PM +0100, Manuel Lauss wrote:
> On Tue, Feb 3, 2015 at 1:44 PM, Mark Brown wrote:
> >> +wm8731->mclk = devm_clk_get(&spi->dev, "mclk");
> >> +if (IS_ERR(wm8731->mclk)) {
> >> +wm8731->mclk = NULL;
> >> +dev_warn(&spi->dev, "assuming static M
From: Markus Elfring
Date: Tue, 3 Feb 2015 16:01:40 +0100
The dvb_unregister_device() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
-
From: Markus Elfring
Date: Tue, 3 Feb 2015 16:47:48 +0100
The functions "dvb_unregister_device" and "kfree" could still be called
by the dvb_ca_en50221_init() function in the case that a previous resource
allocation failed.
* Corresponding details could be improved by adjustments for jump target
On 02/03/2015 04:21 PM, Michal Hocko wrote:
> On Tue 03-02-15 11:16:00, Mel Gorman wrote:
>> On Tue, Feb 03, 2015 at 09:19:15AM +0100, Vlastimil Babka wrote:
> [...]
>>> And if we agree that there is indeed no guarantee, what's the actual
>>> semantic
>>> difference from MADV_FREE? I guess none? S
On Tue, Feb 03, 2015 at 02:04:05PM +0900, Jaewon Kim wrote:
> This patch adds new regulator driver to support max77843
> MFD(Multi Function Device) chip`s regulators.
> The Max77843 has two voltage regulators for USB safeout.
This looks mostly good, a couple of very small things:
> +static const
cm/linux/kernel/git/paulmck/linux-rcu.git
> > revert-c418b8035fac0cc7d242e5de126cec1006a34bed-dd2b39be8eee9d175c7842c30e405a5cbe50095a
>
> On next-20150203 I hit similar error on ARM/Exynos4412 (Trats2 board)
> while suspending to RAM:
Yep, you are not supposed to be using RCU on off
On 02/03/2015 06:13 AM, Tomeu Vizoso wrote:
On 2 February 2015 at 22:08, Stephen Warren wrote:
On 01/28/2015 03:50 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the Nyan
boards. Use the same card ID that alsaucm will expect.
diff --git a/arch/arm/boot/
On 2/3/2015 7:51 AM, Serge E. Hallyn wrote:
> Quoting Casey Schaufler (ca...@schaufler-ca.com):
>> On 2/2/2015 12:37 PM, Andy Lutomirski wrote:
>>> On Mon, Feb 2, 2015 at 10:08 AM, Serge Hallyn
>>> wrote:
Quoting Casey Schaufler (ca...@schaufler-ca.com):
> I'm game to participate in such
On Tuesday 03 February 2015 11:22:01 Rob Clark wrote:
> On Tue, Feb 3, 2015 at 11:12 AM, Arnd Bergmann wrote:
> > I agree for the case you are describing here. From what I understood
> > from Rob was that he is looking at something more like:
> >
> > Fig 3
> > CPU--L1cache--L2cache--Memory--IOMMU-
Am 03.02.2015 um 16:41 schrieb Lukáš Czerner:
On Tue, 3 Feb 2015, Alexander Holler wrote:
I'm already spending a lot of time trying to convince the developers here,
that this a feature most people expect from any filesystem. And I've written
these patches, for which now, even after I've marked
On Tue, Feb 03, 2015 at 03:34:45PM +0100, David Hildenbrand wrote:
> >
> > * Paul E. McKenney wrote:
> >
> > > Hello, Ingo,
> > >
> > > The changes in this series include:
> > >
> > > 1.Documentation updates. These were posted to LKML at
> > > https://lkml.org/lkml/2015/1/7/496.
> >
Hello Minchan (and Michal)
I did not see this patch until just now when Michael explicitly
mentioned it in another discussion because
(a) it was buried in an LMKL thread that started a topic
that was not about a man-pages patch.
(b) linux-man@ was not CCed.
When resubmitting this patch, could
On Tue, 3 Feb 2015 15:16:25 +0100
Jiri Olsa wrote:
> On Mon, Feb 02, 2015 at 02:35:07PM -0500, Steven Rostedt wrote:
>
> SNIP
>
> > }
> > @@ -325,12 +351,19 @@ const char *perf_debugfs_mount(const char *mountpoint)
> > void perf_debugfs_set_path(const char *mntpt)
> > {
> > snprintf(debu
On Fri, Jan 30, 2015 at 12:04:01PM +0200, Stanimir Varbanov wrote:
> From: Joonwoo Park
>
> Add initial pinctrl driver to support pin configuration with
> pinctrl framework for msm8916.
>
> Signed-off-by: Joonwoo Park
> Signed-off-by: Stanimir Varbanov
> Reviewed-by: Bjorn Andersson
Looks go
On Sat, Jan 24, 2015 at 08:30:27AM +0100, Jean-Francois Moine wrote:
> Mark Brown wrote:
> > On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
> > > The simple card builder, 'dt-card' (maybe a better name would have been
> > > 'graph-card'), acts just like the simple-card excep
On Mon, Feb 02, 2015 at 12:45:28PM +, Hanjun Guo wrote:
> Hi,
>
> This is the v8 of ACPI core patches for ARM64 based on ACPI 5.1, there are
> some updates since v7:
>
> - Add two more documantation to explain why we need ACPI in ARM64 servers
>by Grant, and recommendations and prohibiti
On Mon, Feb 2, 2015 at 11:36 AM, Nix wrote:
> On 2 Feb 2015, Myron Stowe verbalised:
>
>> Nix:
>>
>> Thanks for the work you've already done with the bisection. Let's see
>> if we can get to the bottom of this. Would you capture two couple sets
>> of logs, one without the issue and another set w
The commit [8975626ea35a: drm/cirrus: allow 32bpp framebuffers for
cirrus drm] broke X modesetting driver because cirrus driver still
provides the full list of modes up to 1280x1024 while the 32bpp can
support only up to 800x600.
We might be able to filter out the invalid modes in mode_valid
callb
301 - 400 of 960 matches
Mail list logo
