The ADC in s3c64xx is almost the same as exynosv1, but
has a different 'select' method. Adding this here will be
helpful to move over the existing s3c64xx platform from the
legacy plat-samsung/adc driver to the new exynos-adc.
Signed-off-by: Arnd Bergmann
---
[In reply to Exynos3250 ADC support,
On Fri, Jul 18, 2014 at 12:13 PM, Peter Zijlstra wrote:
> On Fri, Jul 18, 2014 at 06:43:39PM +0100, Pawel Moll wrote:
>> This change is trying to make the sched clock "similar" to the
>> monotonic raw one.
>>
>> The main goal is to provide some kind of unification between time
>> flow in kernel
On Fri, Jul 18, 2014 at 03:00:46PM -0400, Alan Stern wrote:
> "Quiescing" is the wrong word. "Quiescing a device" means stopping the
> device from doing anything, which isn't what you want. You want to
> ignore any activity the device may generate and reduce the device's
> power consumption as
On 07/18/2014 09:14 AM, Alex Elder wrote:
> It is possible for the log to be filled too quickly for the consoles
> to be able to keep up. This is detected in console_unlock(), and
> when it occurs, a message is printed on the console. When reviewing
> some nearby code, Petr Mládek suggested it
Hi James,
Please pull these seccomp changes for 3.17.
(And if I should base off something other than security-next, please
let me know. Or if there are any things I should be doing differently
with this tree.)
Thanks!
-Kees
The following changes since commit
> From: Robert Baldyga [mailto:r.bald...@samsung.com]
> Sent: Friday, July 18, 2014 4:39 AM
>
> This patchset contains fixes for dwc2 gadget driver. It touches PHY,
> FIFO configuration, initialization sequence and adds many other small fixes.
>
> Best regards
> Robert Baldyga
> Samsung R
On 07/17/2014 10:00 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> In file included from arch/x86/vdso/vdso2c.c:161:0:
> arch/x86/vdso/vdso2c.c: In function 'main':
>
On Fri, Jul 18, 2014 at 06:43:39PM +0100, Pawel Moll wrote:
> This change is trying to make the sched clock "similar" to the
> monotonic raw one.
>
> The main goal is to provide some kind of unification between time
> flow in kernel and in user space, mainly to achieve correlation
> between perf
On 07/18/14 09:10, Chanwoo Choi wrote:
On 07/09/2014 12:00 PM, Chanwoo Choi wrote:
From: Tomasz Figa
This patch add I2S (Inter-IC Sound) dt node which supports 1-port stereo
(1 channels) IIS-bus for audio interface with DMA-based operation.
Signed-off-by: Tomasz Figa
Signed-off-by: Inha Song
On Fri, 18 Jul 2014, Nicholas Krause wrote:
> I am removing two fix mes in this file as after dicussing then it seems
> there is no reason to check against Null for usb_device as it can never
> be NULL and this is check is therefore not needed.
>
> Signed-off-by: Nicholas Krause
> ---
>
On 07/18/14 07:42, Javier Martinez Canillas wrote:
Hello Kukjin,
Hi,
On 06/24/2014 06:28 PM, Doug Anderson wrote:
This adds cros_ec to exynos5420-peach-pit and exynos5800-peach-pi,
including:
* The keyboard
* The i2c tunnel
* The tps65090 under the i2c tunnel
* The battery under the i2c
bly won't be till next week.
Anyway, I've updated the keys-preparse-1 branch and tagged it anew with
keys-preparse-1-20140718. There was a spelling fix in the docs and the
patches have been rebased on the updated security/next.
I've also rebuilt the keys-next branch, basing it on the updated
secu
On Fri, Jul 18, 2014 at 10:51:19AM -0700, John Stultz wrote:
> Very cool work! I've not been able to review it carefully, but one good
> stress test would be to pick a system where the hardware used for
> sched_clock is different from the hardware used for timekeeping.
>
> Probably easily done on
On Fri, Jul 18, 2014 at 10:11 AM, Mimi Zohar wrote:
> On Mon, 2014-07-14 at 14:38 -0700, Kees Cook wrote:
>> As an alternative to loading bytes from the "data" blob when reading
>> firmware, let kernel read from an fd, so that the LSM can reason about
>> the origin of firmware contents during
On Fri, 18 Jul 2014, Patrik Fimml wrote:
> 2. Give userspace a way of quiescing a device. Handles to the device
> stay open, but the device will no longer perform its function and,
> if possible, power down.
"Quiescing" is the wrong word. "Quiescing a device" means stopping the
device
On Fri, Jul 18, 2014 at 11:51 AM, Andy Lutomirski wrote:
> On Fri, Jul 18, 2014 at 11:13 AM, Kees Cook wrote:
>> On Fri, Jul 18, 2014 at 10:17 AM, Andy Lutomirski
>> wrote:
>>> On Thu, Jul 17, 2014 at 8:26 PM, James Morris wrote:
On Thu, 17 Jul 2014, Kees Cook wrote:
> Twelfth
Hello,
On Fri, Jul 18, 2014 at 11:47:08AM -0700, Nish Aravamudan wrote:
> Why are any callers of the format kthread_create_on_node(...,
> cpu_to_node(cpu), ...) not using kthread_create_on_cpu(..., cpu, ...)?
Ah, okay, that's because unbound workers are NUMA node affine, not
CPU.
> It seems
On Fri, Jul 18, 2014 at 11:51 AM, Aditya Kali wrote:
> On Fri, Jul 18, 2014 at 9:51 AM, Andy Lutomirski wrote:
>> On Jul 17, 2014 1:56 PM, "Aditya Kali" wrote:
>>>
>>> On Thu, Jul 17, 2014 at 12:57 PM, Andy Lutomirski
>>> wrote:
>>> > What happens if someone moves a task in a cgroup namespace
On 07/18/2014 12:47 PM, Heiko Stübner wrote:
Hi Daniel,
Am Freitag, 18. Juli 2014, 11:46:51 schrieb Daniel Lezcano:
On 07/07/2014 05:13 PM, Matthias Brugger wrote:
This adds a generic devicetree board file and a dtsi for boards
based on MT6589 SoCs from Mediatek.
Apart from the generic parts
On Fri, Jul 18, 2014 at 11:47 AM, Steven Rostedt wrote:
> Do you think this is worthy of stable and 3.16 material?
Perhaps. Not sure that I need it (I'm stuck waiting for the extlog_trace pieces
which are now queued in "tip", but won't go in until 3.17). But I suppose we
should minimize the
On Fri, 18 Jul 2014, Jiri Slaby wrote:
> From: Naoya Horiguchi
>
> 3.12-stable review patch. If anyone has any objections, please let me know.
>
> ===
>
> commit 4a705fef986231a3e7a6b1a6d3c37025f021f49f upstream.
>
> There's a race between fork() and hugepage migration, as a
On 07/14/14 12:58, Pankaj Dubey wrote:
As exynos_cpuidle_init and exynos_cpufreq_init function have just one lines
of code for registering platform devices. We can move these lines to
exynos_dt_machine_init and delete exynos_cpuidle_init and exynos_cpufreq_init
function. This will help in
On Fri, Jul 18, 2014 at 11:13 AM, Kees Cook wrote:
> On Fri, Jul 18, 2014 at 10:17 AM, Andy Lutomirski wrote:
>> On Thu, Jul 17, 2014 at 8:26 PM, James Morris wrote:
>>> On Thu, 17 Jul 2014, Kees Cook wrote:
>>>
Twelfth time's the charm! :)
>>>
>>> Btw, there doesn't seem to be an official
On Fri, Jul 18, 2014 at 9:51 AM, Andy Lutomirski wrote:
> On Jul 17, 2014 1:56 PM, "Aditya Kali" wrote:
>>
>> On Thu, Jul 17, 2014 at 12:57 PM, Andy Lutomirski
>> wrote:
>> > What happens if someone moves a task in a cgroup namespace outside of
>> > the namespace root cgroup?
>> >
>>
>>
On Fri, 2014-07-18 at 11:17 -0700, Greg KH wrote:
> On Fri, Jul 18, 2014 at 09:54:32AM -0700, James Bottomley wrote:
> > On Fri, 2014-07-18 at 09:43 -0700, Greg KH wrote:
> > > On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote:
> > > > On Fri, Jul 18, 2014 at 05:26:47PM +0200,
On Saturday 19 July 2014 02:02:09 Chanwoo Choi wrote:
> On Sat, Jul 19, 2014 at 1:33 AM, Arnd Bergmann wrote:
> > On Saturday 19 July 2014 01:23:15 Chanwoo Choi wrote:
> >> If don't add new compatible including specific exynos version,
> >> I would add new 'adc-needs-sclk' property with existing
On Fri, 18 Jul 2014 11:43:01 -0700
Tony Luck wrote:
> The "uptime" tracer added in:
>
> commit 8aacf017b065a805d27467843490c976835eb4a5
> tracing: Add "uptime" trace clock that uses jiffies
>
> has wraparound problems when the system has been up more
> than 1 hour 11 minutes and 34
The "uptime" tracer added in:
commit 8aacf017b065a805d27467843490c976835eb4a5
tracing: Add "uptime" trace clock that uses jiffies
has wraparound problems when the system has been up more
than 1 hour 11 minutes and 34 seconds. It converts jiffies
to nanoseconds using:
Since there is a lot of stuff that need to be changed in order to meet the
kernel
coding style in wcmd.c file, I've decided to fix function-per-patch.
The following changes were made in vCommandTimerWait function:
- Camel case change:
- MSecond ---> msec
- hDdeviceContext ---> private
-
This series implements eBPF JIT compiler for arm64.
Please see [14/14] for change log.
Patches [1-13/14] implement code generation functions.
Patch [14/14] implements the actual eBPF JIT compiler.
Many thanks to everyone who's reviewed the code from
RFCv1->RFCv3, especially Alexei for BPF bits,
Introduce function to generate add/subtract (immediate) instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 16
arch/arm64/kernel/insn.c | 44 +++
2 files changed, 60 insertions(+)
diff --git
Introduce function to generate load/store pair instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 16 +++
arch/arm64/kernel/insn.c | 65 +++
2 files changed, 81 insertions(+)
diff --git
Introduce function to generate unconditional branch (register)
instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 7 +++
arch/arm64/kernel/insn.c | 35 +--
2 files changed, 40 insertions(+), 2 deletions(-)
diff --git
Introduce function to generate move wide (immediate) instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 13 +
arch/arm64/kernel/insn.c | 43 +++
2 files changed, 56 insertions(+)
diff --git
Introduce function to generate conditional branch (immediate)
instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 21 +
arch/arm64/kernel/insn.c | 17 +
2 files changed, 38 insertions(+)
diff --git
Introduce function to generate bitfield instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 16 +
arch/arm64/kernel/insn.c | 56 +++
2 files changed, 72 insertions(+)
diff --git a/arch/arm64/include/asm/insn.h
Introduce function to generate load/store (register offset)
instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 20 ++
arch/arm64/kernel/insn.c | 62 +++
2 files changed, 82 insertions(+)
diff --git
Introduce function to generate logical (shifted register)
instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 25 ++
arch/arm64/kernel/insn.c | 60 +++
2 files changed, 85 insertions(+)
diff --git
Introduce function to generate data-processing (1 source) instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 13 +
arch/arm64/kernel/insn.c | 37 +
2 files changed, 50 insertions(+)
diff --git
Introduce function to generate add/subtract (shifted register)
instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 11 ++
arch/arm64/kernel/insn.c | 49 +++
2 files changed, 60 insertions(+)
diff --git
Introduce function to generate data-processing (2 source) instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 20 ++
arch/arm64/kernel/insn.c | 48 +++
2 files changed, 68 insertions(+)
diff --git
Introduce function to generate data-processing (3 source) instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 14 ++
arch/arm64/kernel/insn.c | 42 ++
2 files changed, 56 insertions(+)
diff --git
The JIT compiler emits A64 instructions. It supports eBPF only.
Legacy BPF is supported thanks to conversion by BPF core.
JIT is enabled in the same way as for other architectures:
echo 1 > /proc/sys/net/core/bpf_jit_enable
Or for additional compiler output:
echo 2 >
Introduce function to generate compare & branch (immediate)
instructions.
Signed-off-by: Zi Shen Lim
---
arch/arm64/include/asm/insn.h | 57
arch/arm64/kernel/insn.c | 88 ---
2 files changed, 140 insertions(+), 5
On Fri, Jul 18, 2014 at 01:57:25AM -0400, Elena Ufimtseva wrote:
> Issues Xen hypercall subop XENMEM_get_vnumainfo and sets the
> NUMA topology, otherwise sets dummy NUMA node and prevents
> numa_init from calling other numa initializators as they dont
> work with pv guests.
>
> Signed-off-by:
> -Original Message-
> From: Ethan Zhao [mailto:ethan.z...@oracle.com]
> Sent: Friday, July 18, 2014 9:13 AM
> To: Manish Chopra; Sony Chacko; Rajesh Borundia; netdev
> Cc: linux-kernel; ethan.ker...@gmail.com; Ethan Zhao
> Subject: [PATCH V3] netxen: fix ethtool rx_dropped information in
On Fri, Jul 18, 2014 at 01:06:41PM -0400, Nick Krause wrote:
> On Fri, Jul 18, 2014 at 10:08 AM, Steven Rostedt wrote:
> > On Thu, Jul 17, 2014 at 11:05:12PM -0400, Nick Krause wrote:
> >> On Thu, Jul 17, 2014 at 1:38 PM, Nick Krause wrote:
> >> > On Thu, Jul 17, 2014 at 3:52 AM, Sam Ravnborg
Hello,
On Fri, Jul 18, 2014 at 11:12:01AM -0700, Nish Aravamudan wrote:
> why aren't these callers using kthread_create_on_cpu()? That API was
It is using that. There just are other data structures too.
> already change to use cpu_to_mem() [so one change, rather than of all over
> the kernel
On Fri, Jul 18, 2014 at 09:54:32AM -0700, James Bottomley wrote:
> On Fri, 2014-07-18 at 09:43 -0700, Greg KH wrote:
> > On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote:
> > > On Fri, Jul 18, 2014 at 05:26:47PM +0200, Benoit Taine wrote:
> > > > We should prefer `const struct
On 14-07-18 07:41 AM, James Bottomley wrote:
On Fri, 2014-07-18 at 17:17 +, Elliott, Robert (Server Storage)
wrote:
From: James Bottomley [mailto:jbottom...@parallels.com]
On Fri, 2014-07-18 at 00:51 +, Elliott, Robert (Server Storage)
wrote:
...
Also, in both sd_setup_flush_cmnd
On Fri, Jul 18, 2014 at 10:17 AM, Andy Lutomirski wrote:
> On Thu, Jul 17, 2014 at 8:26 PM, James Morris wrote:
>> On Thu, 17 Jul 2014, Kees Cook wrote:
>>
>>> Twelfth time's the charm! :)
>>
>> Btw, there doesn't seem to be an official seccomp maintainer. Kees, would
>> you like to volunteer
On 07/18/2014 10:45 AM, Nick Krause wrote:
> Hey Greg and others,
> When I built the usb directory today to check a patch I am also
> sending to. I seem to hitting
> a few compiler errors and a lot of warnings. I am going to attach a
> file of my log of this build.
> Cheers Nick
>
Hi,
What
When the grant operations failed, the skb is freed up eventually, and it tries
to release the frags, if there is any. For the main skb nr_frags is set to 0 to
avoid this, but on the frag_list it iterates through the frags array, and tries
to call put_page on the page pointer which contains garbage
Due to this pointer is increased prematurely, the error log contains rubbish.
Signed-off-by: Zoltan Kiss
Reported-by: Armin Zentai
Cc: net...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: xen-de...@lists.xenproject.org
---
diff --git a/drivers/net/xen-netback/netback.c
This series fixes a lot of bugs on the error path around this function, which
were introduced with my grant mapping series in 3.15. They apply to the latest
net tree, but probably to net-next as well without any modification.
I'll post an another series which applies to 3.15 stable, as the problem
This patch makes this function aware that the first frag and the header might
share the same ring slot. That could happen if the first slot is bigger than
PKT_PROT_LEN. Due to this the error path might release that slot twice or never,
depending on the error scenario.
xenvif_idx_release is also
The error handling for skb's with frag_list was completely wrong, it caused
double unmap attempts to happen if the error was on the first skb. Move it to
the right place in the loop.
Signed-off-by: Zoltan Kiss
Reported-by: Armin Zentai
Cc: net...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
On 18/07/14 16:25, Wei Liu wrote:
On Thu, Jul 17, 2014 at 08:09:51PM +0100, Zoltan Kiss wrote:
This patch makes this function aware that the first frag and the header might
share the same ring slot. That could happen if the first slot is bigger than
MAX_SKB_LEN. Due to this the error path might
On Fri, 2014-07-18 at 09:43 -0700, Greg KH wrote:
> On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote:
> > On Fri, Jul 18, 2014 at 05:26:47PM +0200, Benoit Taine wrote:
> > > We should prefer `const struct pci_device_id` over
> > > `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding
On 07/18/2014 11:37 PM, Lennox Wu wrote:
> Score can provide dummy functions if HAS_IOMEM and NO_IOMEM will be
> removed, even if we indeed have no IOMEM.
>
Thank you for your reply, for score, your ideas is OK to me.
And for the COMPILE_TEST needs still discussing below:
> 2014-07-18 18:51
On Fri, Jul 18, 2014 at 02:00:08PM -0400, Tejun Heo wrote:
> This isn't a huge issue but it shows that this is the wrong layer to
> deal with this issue. Let the allocators express where they are.
^
allocator users
> Choosing and
Hello,
On Fri, Jul 18, 2014 at 10:42:29AM -0700, Nish Aravamudan wrote:
> So, to be clear, this is not *necessarily* about memoryless nodes. It's
> about the semantics intended. The workqueue code currently calls
> cpu_to_node() in a few places, and passes that node into the core MM as a
> hint
On 7/17/2014 11:45 PM, Gioh Kim wrote:
>
> Hi,
>
> For page migration of CMA, buffer-heads of lru should be dropped.
> Please refer to https://lkml.org/lkml/2014/7/4/101 for the history.
>
> I have two solution to drop bhs.
> One is invalidating entire lru.
> Another is searching the lru and
On 07/18/2014 10:43 AM, Pawel Moll wrote:
> This change is trying to make the sched clock "similar" to the
> monotonic raw one.
>
> The main goal is to provide some kind of unification between time
> flow in kernel and in user space, mainly to achieve correlation
> between perf timestamps and
Hemant Kumar writes:
First I should say supporting these probes is very useful. Thanks for
working on this.
> +
> +#define SDT_CACHE_DIR "/var/cache/perf/"
This requires running perf as root, right?
It would be better to use the $HOME cache dir, like the recent JSON patches.
> +#define
On Fri, 18 Jul 2014 13:35:48 -0400
Nick Krause wrote:
>
> Why are you even asking this?
What do you think?
-- Steve
--
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
On 18/07/14 16:24, Wei Liu wrote:
On Thu, Jul 17, 2014 at 08:09:49PM +0100, Zoltan Kiss wrote:
The error handling for skb's with frag_list was completely wrong, it caused
double unmap attempts to happen if the error was on the first skb. Move it to
the right place in the loop.
Signed-off-by:
On Fri, Jul 18, 2014 at 02:43:02AM +0200, Rafael J. Wysocki wrote:
> From past discussions on similar topics it followed that there really was
> no generic way for individual drivers to quiesce devices on demand as long as
> user space was running. Everything we could come up with was racy, this
On Mon, Jul 14, 2014 at 06:49:44PM -0300, Gustavo Padovan wrote:
> Hi John,
>
> Some more patches for 3.17. The most important change here is the move of
> the 6lowpan code to net/6lowpan. It has been agreed with Davem that this
> change will go through the bluetooth tree. The rest are mostly
This change is trying to make the sched clock "similar" to the
monotonic raw one.
The main goal is to provide some kind of unification between time
flow in kernel and in user space, mainly to achieve correlation
between perf timestamps and clock_gettime(CLOCK_MONOTONIC_RAW).
This has been
On Fri, 2014-07-18 at 17:17 +, Elliott, Robert (Server Storage)
wrote:
>
>
> > From: James Bottomley [mailto:jbottom...@parallels.com]
> >
> > On Fri, 2014-07-18 at 00:51 +, Elliott, Robert (Server Storage)
> > wrote:
> ...
> > >
> > > Also, in both sd_setup_flush_cmnd and
2014-07-18 20:18 GMT+03:00 walter harms :
> i would expect a ckeck for the upper limit with ARRAY_SIZE
Thanks, resubmitted.
--
Andrey Utkin
--
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
> On powerpc our event names are always uppercase, it would be nice if the perf
> list output honoured that.
>
> Can we instead just honour whatever case is in the input JSON ?
Intel events are upper case too. However perf is not into shouting
in general, so I chose to lower everything.
>
> It
Dropped negativity check; enhanced upper limit check as proposed by
Walter Harms
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=80591
Reported-by: David Binderman
Signed-off-by: Andrey Utkin
---
kernel/debug/kdb/kdb_bp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Jul 18, 2014 at 1:31 PM, Steven Rostedt wrote:
> On Fri, 18 Jul 2014 13:08:39 -0400
> Nick Krause wrote:
>
>> Sorry I was trying to help , I guess this conversation is now closed.
>> It was a fucking stupid idea.
>
> Are you afraid of sex?
>
> -- Steve
Why are you even asking this?
Nick
On Fri, 18 Jul 2014 10:05:00 -0700
Tony Luck wrote:
> On Thu, Jul 17, 2014 at 7:08 PM, Steven Rostedt wrote:
> >> Do we really need to convert to nanoseconds? Couldn't we just return
> >> jiffies:
> >
> > Sure, and we can make it a "counter". That is, the counters don't hide
> > 1000 counts on
Ingo Molnar writes:
>
> We want these description files to be in the perf source code,
> somewhere in tools/perf/live-config/arch/x86/ or so, and installed
> during 'make install' - i.e. part of perf project and installed in
> ~/.debug or ~/.perf or so.
I don't think that's a good idea. It
I am removing two fix mes in this file as after dicussing then it seems
there is no reason to check against Null for usb_device as it can never
be NULL and this is check is therefore not needed.
Signed-off-by: Nicholas Krause
---
drivers/usb/core/hcd.c | 4
1 file changed, 4 deletions(-)
On Fri, 18 Jul 2014 13:08:39 -0400
Nick Krause wrote:
> Sorry I was trying to help , I guess this conversation is now closed.
> It was a fucking stupid idea.
Are you afraid of sex?
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Add DAPM calls to enable/disable the Class D amp.
Also add a DAPM call to turn off the PLL upon
the stream completing.
Signed-off-by: Dan Murphy
---
sound/soc/codecs/tas2552.c | 58 +++-
1 file changed, 41 insertions(+), 17 deletions(-)
diff --git
In the pm suspend/resume it is better
to disable the GPIO after the regmap_cache
setting calls so that if the call is interrupted
the new reg values will be cached and set on resume.
Also add pm_runtime_put in the remove call.
Signed-off-by: Dan Murphy
---
sound/soc/codecs/tas2552.c |8
Hi Paul,
While running the kvm rcutorture test scripts, I encountered a build failure
caused by
Commit 918179699e4a ("rcu: Don't keep timekeeping CPU tick running for
non-nohz_full= CPUs")
This commit fixes the failure. This is on top of paul/rcu/dev.
Signed-off-by: Pranith Kumar
---
Hello.
On 07/18/2014 04:30 PM, Antoine Ténart wrote:
The Berlin SATA PHY drives the PHY related to the SATA interface. Add
the corresponding documentation.
Signed-off-by: Antoine Ténart
---
.../devicetree/bindings/phy/berlin-sata-phy.txt| 34 ++
1 file changed,
Move it from exynos5250-cros-common.dtsi to exynos5250-snow.dts.
Spring does not need it, it uses an Atmel maXTouch instead.
Signed-off-by: Andreas Färber
---
v2: New (Doug Anderson)
arch/arm/boot/dts/exynos5250-cros-common.dtsi | 8
arch/arm/boot/dts/exynos5250-snow.dts |
Adds initial support for the HP Chromebook 11.
Cc: Vincent Palatin
Cc: Doug Anderson
Cc: Stephan van Schaik
Signed-off-by: Andreas Färber
---
v1 -> v2:
* Use label-based overriding/extension of nodes. (Doug Anderson)
* Dropped tps65090 for now, until we know where to place it.
* Dropped
Stephen Rothwell's compiler did something amazing: it unrolled a
loop, discovered that one iteration of that loop contained an
always-true test, and emitted a warning that will IMO only serve to
convince people to disable the warning.
That bogus warning caused me to wonder what prompted such an
Move it from exynos5250-cros-common.dtsi to exynos5250-snow.dts.
Spring does not need it, it uses an s5m8767 instead.
Signed-off-by: Andreas Färber
---
v2: New (Doug Anderson)
arch/arm/boot/dts/exynos5250-cros-common.dtsi | 151 -
arch/arm/boot/dts/exynos5250-snow.dts
The remaining pieces are fairly minor.
Suggested-by: Doug Anderson
Signed-off-by: Andreas Färber
---
v2: New (Doug Anderson)
arch/arm/boot/dts/exynos5250-cros-common.dtsi | 164 -
arch/arm/boot/dts/exynos5250-snow.dts | 169 ++
2 files
On Fri, Jul 18, 2014 at 3:41 AM, Sam Ravnborg wrote:
> On Fri, Jul 18, 2014 at 12:21:04AM -0400, Nick Krause wrote:
>> The build for sparc allmodconfig is still failing for the main branch
>> of the linux kernel.
>> I would recommend fixing these issues. I am attaching my build
>> warnings and
On Tue, Jul 15, 2014 at 05:24:45PM -0600, Bjorn Helgaas wrote:
> Per license_is_gpl_compatible(), the MODULE_LICENSE() string for GPL v2 is
> "GPL v2", not "GPLv2". Use "GPL v2" so this module doesn't taint the
> kernel.
>
> Signed-off-by: Bjorn Helgaas
Applied, thank you.
> ---
>
> From: James Bottomley [mailto:jbottom...@parallels.com]
>
> On Fri, 2014-07-18 at 00:51 +, Elliott, Robert (Server Storage)
> wrote:
...
> >
> > Also, in both sd_setup_flush_cmnd and sd_sync_cache:
> > cmd->cmnd[0] = SYNCHRONIZE_CACHE;
> > cmd->cmd_len = 10;
> >
> >
Am 18.07.2014 17:34, schrieb Andrey Utkin:
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=80591
> Reported-by: David Binderman
> Signed-off-by: Andrey Utkin
> ---
> kernel/debug/kdb/kdb_bp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Fri, Jul 18, 2014 at 10:45 AM, Alan Stern wrote:
> On Fri, 18 Jul 2014, Nick Krause wrote:
>
>> I am assuming this is a stupid question but since I am new I will ask it
>> anyway.
>> Can the usb_bus structure be Null? If can I will send it a patch removing
>> the
>> fix mes on lines 854
On Thu, Jul 17, 2014 at 8:26 PM, James Morris wrote:
> On Thu, 17 Jul 2014, Kees Cook wrote:
>
>> Twelfth time's the charm! :)
>
> Btw, there doesn't seem to be an official seccomp maintainer. Kees, would
> you like to volunteer for this? If so, send in a patch for MAINTAINERS,
> and set up a
On Fri, Jul 18, 2014 at 10:12:38AM -0700, h...@infradead.org wrote:
> This is what I plan to put in after it passes basic testing:
And that one was on top of my previous version. One that applies
against core-for-3.17 below:
---
>From 8a79783e5f72ec034a724e16c1f46604bd97bf68 Mon Sep 17 00:00:00
This is what I plan to put in after it passes basic testing:
---
>From bb617c9465b839d70ecbbc69002a20ccf5f935bd Mon Sep 17 00:00:00 2001
From: "K. Y. Srinivasan"
Date: Fri, 18 Jul 2014 19:12:58 +0200
Subject: sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O
timeout
Commit ID:
On Mon, 2014-07-14 at 14:38 -0700, Kees Cook wrote:
> As an alternative to loading bytes from the "data" blob when reading
> firmware, let kernel read from an fd, so that the LSM can reason about
> the origin of firmware contents during userspace on-demand loading.
>
> Signed-off-by: Kees Cook
On Mon, 2014-07-14 at 14:38 -0700, Kees Cook wrote:
> In order to validate the contents of firmware being loaded, there must be
> a hook to evaluate any loaded firmware that wasn't built into the kernel
> itself. Without this, there is a risk that a root user could load malicious
> firmware
On Fri, Jul 18, 2014 at 01:30:53PM +0200, Lothar Waßmann wrote:
> Aua. This really hurts. I wonder how this could ever be admitted to
> the Linux kernel...
> Further comments suppressed because the would most likely violate the
> CDA.
>
> If someone should not grasp what this patch does, they
On Fri, Jul 18, 2014 at 7:58 AM, Steven Rostedt wrote:
> On Thu, Jul 17, 2014 at 11:24:45PM -0400, Nick Krause wrote:
>> >
>> Yes I am human. Now thinking about it we need it to test for staging.
>
> Why do you say that?
>
> -- Steve
Sorry I was trying to help , I guess this conversation is now
201 - 300 of 2038 matches
Mail list logo
