Sergei Shtylyov wrote:
> > When commit 0d12f8a4027d021c9cc942f09f38d28288020c5d moved to keeping the
>
>scripts/checkpatch.pl now enforces the common commit citing style as for
> the Fixes: tag and the patch description, you need to specify the summary
Sergei Shtylyov wrote:
> > When commit 0d12f8a4027d021c9cc942f09f38d28288020c5d moved to keeping the
>
>scripts/checkpatch.pl now enforces the common commit citing style as for
> the Fixes: tag and the patch description, you need to specify the summary too.
I've now added a "Fixes:" line
David Miller wrote:
> Wouldn't it be better to just code the proc stuff to walk whatever
> table the rest of the stack uses to hold all of the connections
> as TCP et al. do?
There won't be "a table" that the rest of the stack uses. There will be more
than one. Service
David Miller wrote:
> Wouldn't it be better to just code the proc stuff to walk whatever
> table the rest of the stack uses to hold all of the connections
> as TCP et al. do?
There won't be "a table" that the rest of the stack uses. There will be more
than one. Service conns and client conns
David Miller wrote:
> I don't see anything in this patch dealing with refcount helper functions.
Good point. I split that part out and you took it already. Will amend.
David
David Miller wrote:
> I don't see anything in this patch dealing with refcount helper functions.
Good point. I split that part out and you took it already. Will amend.
David
On Jul 5, 2016, at 2:08 PM, Al Viro wrote:
> On Tue, Jul 05, 2016 at 12:33:09PM -0400, Oleg Drokin wrote:
>
>> This also makes me question the whole thing some more. We are definitely in
>> lookup
>> when this hits, so the dentry is already new, yet it does not check off as
>> d_in_lookup().
On Jul 5, 2016, at 2:08 PM, Al Viro wrote:
> On Tue, Jul 05, 2016 at 12:33:09PM -0400, Oleg Drokin wrote:
>
>> This also makes me question the whole thing some more. We are definitely in
>> lookup
>> when this hits, so the dentry is already new, yet it does not check off as
>> d_in_lookup().
I submitted this fedora bugzilla recently:
https://bugzilla.redhat.com/show_bug.cgi?id=1352325
Among other things, it shows a Windows 10 KVM virtual machine
causing strange side effects back on the fedora 24 host, which
sure seems like the sort of thing that might be a security issue.
After
I submitted this fedora bugzilla recently:
https://bugzilla.redhat.com/show_bug.cgi?id=1352325
Among other things, it shows a Windows 10 KVM virtual machine
causing strange side effects back on the fedora 24 host, which
sure seems like the sort of thing that might be a security issue.
After
On Tue, 5 Jul 2016 20:45:17 +0200
Borislav Petkov wrote:
> On Tue, Jul 05, 2016 at 02:26:48PM -0400, Steven Rostedt wrote:
> > > + if (rs->missed)
> > > + printk(KERN_WARNING "%s: %d output lines suppressed due to
> > > ratelimiting\n",
> > > +
On Tue, 5 Jul 2016 20:45:17 +0200
Borislav Petkov wrote:
> On Tue, Jul 05, 2016 at 02:26:48PM -0400, Steven Rostedt wrote:
> > > + if (rs->missed)
> > > + printk(KERN_WARNING "%s: %d output lines suppressed due to
> > > ratelimiting\n",
> > > +current->comm, rs->missed);
Hi,
[auto build test WARNING on clk/clk-next]
[also build test WARNING on next-20160705]
[cannot apply to v4.7-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Abhilash-Kesavan/Add-CPU-clock
Hi,
[auto build test WARNING on clk/clk-next]
[also build test WARNING on next-20160705]
[cannot apply to v4.7-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Abhilash-Kesavan/Add-CPU-clock
Sometimes drivers may call this API and expect it to fail because
the extcon they're looking for is optional. Let's move these
prints to debug level so it doesn't look like there's a problem
when there isn't one.
Signed-off-by: Stephen Boyd
---
drivers/extcon/extcon.c |
Sometimes drivers may call this API and expect it to fail because
the extcon they're looking for is optional. Let's move these
prints to debug level so it doesn't look like there's a problem
when there isn't one.
Signed-off-by: Stephen Boyd
---
drivers/extcon/extcon.c | 4 ++--
1 file changed,
On Mon, Jul 04, 2016 at 10:45:02AM -0700, Guenter Roeck wrote:
> On 07/04/2016 10:11 AM, Heikki Krogerus wrote:
> [ ... ]
>
> > > > We should not forget also that the userspace can never rely on those
> > > > details because of the fact that they simply will not always be
> > > > available.
> > >
On Mon, Jul 04, 2016 at 10:45:02AM -0700, Guenter Roeck wrote:
> On 07/04/2016 10:11 AM, Heikki Krogerus wrote:
> [ ... ]
>
> > > > We should not forget also that the userspace can never rely on those
> > > > details because of the fact that they simply will not always be
> > > > available.
> > >
On Tue, Jul 05, 2016 at 02:26:48PM -0400, Steven Rostedt wrote:
> > + if (rs->missed)
> > + printk(KERN_WARNING "%s: %d output lines suppressed due to
> > ratelimiting\n",
> > + current->comm, rs->missed);
>
> Is the comm important?
Yes, we wanna dump the task name
On Tue, Jul 05, 2016 at 02:26:48PM -0400, Steven Rostedt wrote:
> > + if (rs->missed)
> > + printk(KERN_WARNING "%s: %d output lines suppressed due to
> > ratelimiting\n",
> > + current->comm, rs->missed);
>
> Is the comm important?
Yes, we wanna dump the task name
On 05.07.2016 19:32, Linus Torvalds wrote:
> On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
>> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>>
>>> - if (rsp->msix->cpuid != smp_processor_id()) {
>>> + if (rsp->msix &&
On 05.07.2016 19:32, Linus Torvalds wrote:
> On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
>> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>>
>>> - if (rsp->msix->cpuid != smp_processor_id()) {
>>> + if (rsp->msix && (rsp->msix->cpuid != smp_processor_id())) {
>>
>> Did
From: Paul Gortmaker
Date: Mon, 4 Jul 2016 17:50:58 -0400
> The Kconfig controlling build of this code is currently:
>
> drivers/connector/Kconfig:config PROC_EVENTS
> drivers/connector/Kconfig: bool "Report process events to userspace"
>
> ...meaning that it
From: Paul Gortmaker
Date: Mon, 4 Jul 2016 17:50:58 -0400
> The Kconfig controlling build of this code is currently:
>
> drivers/connector/Kconfig:config PROC_EVENTS
> drivers/connector/Kconfig: bool "Report process events to userspace"
>
> ...meaning that it currently is not being built
On Tue, Jul 05, 2016 at 03:55:23PM +0200, Andreas Färber wrote:
> Hi Fabio,
>
> Am 05.07.2016 um 14:04 schrieb Fabio Estevam:
> > On Tue, Jul 5, 2016 at 1:04 AM, Andreas Färber wrote:
> >
> >> +/dts-v1/;
> >> +
> >> +#include "imx6sx-udoo-neo.dtsi"
> >> +
> >> +/ {
> >> +
On Tue, Jul 05, 2016 at 03:55:23PM +0200, Andreas Färber wrote:
> Hi Fabio,
>
> Am 05.07.2016 um 14:04 schrieb Fabio Estevam:
> > On Tue, Jul 5, 2016 at 1:04 AM, Andreas Färber wrote:
> >
> >> +/dts-v1/;
> >> +
> >> +#include "imx6sx-udoo-neo.dtsi"
> >> +
> >> +/ {
> >> + model = "UDOO
On 05/07/2016 at 10:40:22 -0500, Rob Herring wrote :
> >> > + - compatible: Should be "atmel,tcb-free-running-timer"
> >> > + - reg: Should contain the TCB channels to be used. If the
> >> > + counter width is 16 bits (at91rm9200-tcb), two consecutive
> >> > + channels are needed.
On 05/07/2016 at 10:40:22 -0500, Rob Herring wrote :
> >> > + - compatible: Should be "atmel,tcb-free-running-timer"
> >> > + - reg: Should contain the TCB channels to be used. If the
> >> > + counter width is 16 bits (at91rm9200-tcb), two consecutive
> >> > + channels are needed.
On Mon, 4 Jul 2016 16:24:51 +0200
Borislav Petkov wrote:
> From: Borislav Petkov
>
> Extend the ratelimiting facility to print the amount of suppressed lines
> when it is being released.
>
> Separated from a previous patch by Linus.
>
> Also, make the
On Mon, 4 Jul 2016 16:24:51 +0200
Borislav Petkov wrote:
> From: Borislav Petkov
>
> Extend the ratelimiting facility to print the amount of suppressed lines
> when it is being released.
>
> Separated from a previous patch by Linus.
>
> Also, make the ON_RELEASE image not use "callbacks" as
On Jul 5, 2016, at 1:42 PM, Al Viro wrote:
> On Tue, Jul 05, 2016 at 11:21:32AM -0400, Oleg Drokin wrote:
>>> ...
>>> - if (d_unhashed(*de)) {
>>> + if (d_in_lookup(*de)) {
>>>struct dentry *alias;
>>>
>>>alias = ll_splice_alias(inode, *de);
>>
>>
On Jul 5, 2016, at 1:42 PM, Al Viro wrote:
> On Tue, Jul 05, 2016 at 11:21:32AM -0400, Oleg Drokin wrote:
>>> ...
>>> - if (d_unhashed(*de)) {
>>> + if (d_in_lookup(*de)) {
>>>struct dentry *alias;
>>>
>>>alias = ll_splice_alias(inode, *de);
>>
>>
On Tue, Jul 05, 2016 at 12:33:09PM -0400, Oleg Drokin wrote:
> This also makes me question the whole thing some more. We are definitely in
> lookup
> when this hits, so the dentry is already new, yet it does not check off as
> d_in_lookup(). That also means that by skipping the ll_splice_alias
On Tue, Jul 05, 2016 at 12:33:09PM -0400, Oleg Drokin wrote:
> This also makes me question the whole thing some more. We are definitely in
> lookup
> when this hits, so the dentry is already new, yet it does not check off as
> d_in_lookup(). That also means that by skipping the ll_splice_alias
Hi Frank,
> On Jul 5, 2016, at 17:24 , Frank Rowand wrote:
>
> On 07/05/16 01:31, Mark Brown wrote:
>> On Mon, Jul 04, 2016 at 01:58:53PM -0700, Frank Rowand wrote:
>>
>>> On the other hand, I have no previous detailed knowledge of the beagle
>>> family.
>>
>> This is
Hi Frank,
> On Jul 5, 2016, at 17:24 , Frank Rowand wrote:
>
> On 07/05/16 01:31, Mark Brown wrote:
>> On Mon, Jul 04, 2016 at 01:58:53PM -0700, Frank Rowand wrote:
>>
>>> On the other hand, I have no previous detailed knowledge of the beagle
>>> family.
>>
>> This is in no way specific to
Hi Frank,
Sorry for taking a bit to reply, had to grok it well first.
> On Jul 3, 2016, at 02:55 , frowand.l...@gmail.com wrote:
>
> From: Frank Rowand
>
> Hi All,
>
> This is version 2 of this email.
>
> Changes from version 1:
>
> - some rewording of the text
>
Hi Frank,
Sorry for taking a bit to reply, had to grok it well first.
> On Jul 3, 2016, at 02:55 , frowand.l...@gmail.com wrote:
>
> From: Frank Rowand
>
> Hi All,
>
> This is version 2 of this email.
>
> Changes from version 1:
>
> - some rewording of the text
> - removed new
Hi Mark,
> On Jul 5, 2016, at 11:31 , Mark Brown wrote:
>
> On Mon, Jul 04, 2016 at 01:58:53PM -0700, Frank Rowand wrote:
>
>> On the other hand, I have no previous detailed knowledge of the beagle
>> family.
>
> This is in no way specific to the BeagleBones, there's
Hi Mark,
> On Jul 5, 2016, at 11:31 , Mark Brown wrote:
>
> On Mon, Jul 04, 2016 at 01:58:53PM -0700, Frank Rowand wrote:
>
>> On the other hand, I have no previous detailed knowledge of the beagle
>> family.
>
> This is in no way specific to the BeagleBones, there's plenty of other
> boards
Eric,
On Sun, Jul 03, 2016 at 05:45:36PM -0700, Eric Anholt wrote:
> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>
> are available in the git repository at:
>
> https://github.com/anholt/linux tags/bcm2835-arm64-next-2016-07-03
>
> for you to fetch changes up to
Eric,
On Sun, Jul 03, 2016 at 05:45:36PM -0700, Eric Anholt wrote:
> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>
> are available in the git repository at:
>
> https://github.com/anholt/linux tags/bcm2835-arm64-next-2016-07-03
>
> for you to fetch changes up to
On Tue, Jul 05, 2016 at 10:25:12AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 05, 2016 at 01:53:03PM +1000, Stephen Rothwell wrote:
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c
> > b/drivers/gpu/drm/i915/i915_gem.c
> > index d3502c0603e5..1f91f187b2a8 100644
> > ---
On Tue, Jul 05, 2016 at 10:25:12AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 05, 2016 at 01:53:03PM +1000, Stephen Rothwell wrote:
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c
> > b/drivers/gpu/drm/i915/i915_gem.c
> > index d3502c0603e5..1f91f187b2a8 100644
> > ---
On Tue, 5 Jul 2016, Frederic Weisbecker wrote:
> > >>That's true, but I'd argue the behavior in that case should be that you
> > >>can
> > >>raise that kind of exception validly (so you can debug), and then you
> > >>should
> > >>quiesce on return to userspace so the application doesn't see
Hi Jon,
I hope you don't mind. I'm merging those three patches on my tree
(for now, they're on an experimental tree that I can easily rebase, if
needed). If OK for you, my plan is to merge it on a separate branch,
together with the other patches for Documentation/linux_tv.
They actually apply
On Tue, 5 Jul 2016, Frederic Weisbecker wrote:
> > >>That's true, but I'd argue the behavior in that case should be that you
> > >>can
> > >>raise that kind of exception validly (so you can debug), and then you
> > >>should
> > >>quiesce on return to userspace so the application doesn't see
Hi Jon,
I hope you don't mind. I'm merging those three patches on my tree
(for now, they're on an experimental tree that I can easily rebase, if
needed). If OK for you, my plan is to merge it on a separate branch,
together with the other patches for Documentation/linux_tv.
They actually apply
Hello.
On 07/05/2016 04:12 PM, David Howells wrote:
When a jumbo packet is being split up and processed, the crypto checksum
for each split-out packet is in the jumbo header and needs placing in the
reconstructed packet header.
When commit 0d12f8a4027d021c9cc942f09f38d28288020c5d moved to
Hello.
On 07/05/2016 04:12 PM, David Howells wrote:
When a jumbo packet is being split up and processed, the crypto checksum
for each split-out packet is in the jumbo header and needs placing in the
reconstructed packet header.
When commit 0d12f8a4027d021c9cc942f09f38d28288020c5d moved to
On Wed, Jul 06, 2016 at 12:53:57AM +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on miklos-vfs/overlayfs-next]
> [also build test ERROR on v4.7-rc6 next-20160705]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve th
On Wed, Jul 06, 2016 at 12:53:57AM +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on miklos-vfs/overlayfs-next]
> [also build test ERROR on v4.7-rc6 next-20160705]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve th
On Tue, Jul 05, 2016 at 11:21:32AM -0400, Oleg Drokin wrote:
> > ...
> > - if (d_unhashed(*de)) {
> > + if (d_in_lookup(*de)) {
> > struct dentry *alias;
> >
> > alias = ll_splice_alias(inode, *de);
>
> This breaks Lustre because we now might progress
On Tue, Jul 05, 2016 at 11:21:32AM -0400, Oleg Drokin wrote:
> > ...
> > - if (d_unhashed(*de)) {
> > + if (d_in_lookup(*de)) {
> > struct dentry *alias;
> >
> > alias = ll_splice_alias(inode, *de);
>
> This breaks Lustre because we now might progress
From: Hayes Wang
Date: Tue, 5 Jul 2016 16:11:46 +0800
> The RTL8152 doesn't have U1U2 and U2P3 features, so use different
> runtime functions for RTL812 and RTL8153 by adding autosuspend_en()
> to rtl_ops.
>
> Signed-off-by: Hayes Wang
Applied,
From: Hayes Wang
Date: Tue, 5 Jul 2016 16:11:46 +0800
> The RTL8152 doesn't have U1U2 and U2P3 features, so use different
> runtime functions for RTL812 and RTL8153 by adding autosuspend_en()
> to rtl_ops.
>
> Signed-off-by: Hayes Wang
Applied, thanks.
Bad things happen if a guest using the TSC deadline timer is migrated.
The guest doesn't re-calibrate the TSC after migration, and the
TSC frequency can and will change unless your processor supports TSC
scaling (on Intel this is only Skylake) or your data center is perfectly
homogeneous.
The
On 07/03/2016 07:23 PM, Yijing Wang wrote:
Cache_sb is not used in cache_alloc, and we have copied
sb info to cache->sb already, remove it.
Added this, and 2-3/3 for 4.8, thanks.
--
Jens Axboe
Bad things happen if a guest using the TSC deadline timer is migrated.
The guest doesn't re-calibrate the TSC after migration, and the
TSC frequency can and will change unless your processor supports TSC
scaling (on Intel this is only Skylake) or your data center is perfectly
homogeneous.
The
On 07/03/2016 07:23 PM, Yijing Wang wrote:
Cache_sb is not used in cache_alloc, and we have copied
sb info to cache->sb already, remove it.
Added this, and 2-3/3 for 4.8, thanks.
--
Jens Axboe
On Tue, 2016-07-05 at 10:17 -0700, Cong Wang wrote:
> On Tue, Jul 5, 2016 at 4:59 AM, Dmitry Vyukov wrote:
> > other info that might help us debug this:
> > Possible unsafe locking scenario:
> >
> >CPU0
> >
> > lock(slock-AF_INET);
> >
> >
On Tue, 2016-07-05 at 10:17 -0700, Cong Wang wrote:
> On Tue, Jul 5, 2016 at 4:59 AM, Dmitry Vyukov wrote:
> > other info that might help us debug this:
> > Possible unsafe locking scenario:
> >
> >CPU0
> >
> > lock(slock-AF_INET);
> >
> > lock(slock-AF_INET);
> >
>
On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>
>> - if (rsp->msix->cpuid != smp_processor_id()) {
>> + if (rsp->msix && (rsp->msix->cpuid != smp_processor_id())) {
>
> Did
On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>
>> - if (rsp->msix->cpuid != smp_processor_id()) {
>> + if (rsp->msix && (rsp->msix->cpuid != smp_processor_id())) {
>
> Did this wind up going into an official commit
Hi,
[auto build test WARNING on miklos-vfs/overlayfs-next]
[also build test WARNING on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Vivek-Goyal/Overlayfs-SELinux
Hi,
[auto build test WARNING on miklos-vfs/overlayfs-next]
[also build test WARNING on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Vivek-Goyal/Overlayfs-SELinux
On Mon, Jun 27, 2016 at 5:54 PM, Franklin S Cooper Jr wrote:
> Occasionally there are times you need to tweak a chained S/G list while
> maintaining the original list. This function will duplicate the passed
> in chained S/G list and return a pointer to the cloned copy.
>
> The
On Mon, Jun 27, 2016 at 5:54 PM, Franklin S Cooper Jr wrote:
> Occasionally there are times you need to tweak a chained S/G list while
> maintaining the original list. This function will duplicate the passed
> in chained S/G list and return a pointer to the cloned copy.
>
> The function also
From: David Howells
Date: Tue, 05 Jul 2016 14:12:54 +0100
> The main connection list is used for two independent purposes: primarily it
> is used to find connections to reap and secondarily it is used to list
> connections in procfs.
>
> Split the procfs list out from the
On Tue, Jul 5, 2016 at 4:59 AM, Dmitry Vyukov wrote:
> other info that might help us debug this:
> Possible unsafe locking scenario:
>
>CPU0
>
> lock(slock-AF_INET);
>
> lock(slock-AF_INET);
>
> *** DEADLOCK ***
>
> 1 lock held by
From: David Howells
Date: Tue, 05 Jul 2016 14:12:54 +0100
> The main connection list is used for two independent purposes: primarily it
> is used to find connections to reap and secondarily it is used to list
> connections in procfs.
>
> Split the procfs list out from the reap list. This
On Tue, Jul 5, 2016 at 4:59 AM, Dmitry Vyukov wrote:
> other info that might help us debug this:
> Possible unsafe locking scenario:
>
>CPU0
>
> lock(slock-AF_INET);
>
> lock(slock-AF_INET);
>
> *** DEADLOCK ***
>
> 1 lock held by syz-executor/354:
> #0:
> > + * Note: functions like richacl_allowed_to_who(),
> > +richacl_group_class_allowed(),
> > + * and richacl_compute_max_masks() iterate through the entire acl in
> > +reverse
> > + * order as an optimization.
> > + *
> > + * In the standard algorithm, aces are considered in forward order.
> >
> > + * Note: functions like richacl_allowed_to_who(),
> > +richacl_group_class_allowed(),
> > + * and richacl_compute_max_masks() iterate through the entire acl in
> > +reverse
> > + * order as an optimization.
> > + *
> > + * In the standard algorithm, aces are considered in forward order.
> >
From: David Howells
Date: Tue, 05 Jul 2016 14:12:47 +0100
> Provide refcount helper functions for connections so that the code doesn't
> touch conn->usage directly.
>
> Also provide queueing helper functions so that the queueing of local and
> connection objects can be
From: David Howells
Date: Tue, 05 Jul 2016 14:12:47 +0100
> Provide refcount helper functions for connections so that the code doesn't
> touch conn->usage directly.
>
> Also provide queueing helper functions so that the queueing of local and
> connection objects can be fixed later.
>
>
This patch adds DT binding documentation for Exnos5433 based TM2
and TM2E boards sound subsystem.
Signed-off-by: Sylwester Nawrocki
Acked-by: Rob Herring
---
Changes since v2:
- none.
Changes since initial version:
- dropped clocks, clock-names
This patch adds the sound machine driver for TM2 and TM2E board.
Speaker and headphone playback, Main Mic capture, Bluetooth,
Voice call and external accessory are supported.
Signed-off-by: Inha Song
[k.kozlowski: rebased on 4.1]
Signed-off-by: Krzysztof Kozlowski
This patch adds DT binding documentation for Exnos5433 based TM2
and TM2E boards sound subsystem.
Signed-off-by: Sylwester Nawrocki
Acked-by: Rob Herring
---
Changes since v2:
- none.
Changes since initial version:
- dropped clocks, clock-names properties, instead properties from
the CODEC
This patch adds the sound machine driver for TM2 and TM2E board.
Speaker and headphone playback, Main Mic capture, Bluetooth,
Voice call and external accessory are supported.
Signed-off-by: Inha Song
[k.kozlowski: rebased on 4.1]
Signed-off-by: Krzysztof Kozlowski
[s.nawrocki: rebased to 4.7,
This patch adds common driver for the Top block of the Samsung Exynos
SoC Low Power Audio Subsystem. This is a minimal driver which prepares
resources for IP blocks like I2S, audio DMA and UART and exposes a regmap
for the Top block registers. Also system power ops are added to ensure
the Audio
This patch adds common driver for the Top block of the Samsung Exynos
SoC Low Power Audio Subsystem. This is a minimal driver which prepares
resources for IP blocks like I2S, audio DMA and UART and exposes a regmap
for the Top block registers. Also system power ops are added to ensure
the Audio
This patch adds documentation of the DT bindings for the Samsung
Exynos SoC Low Power Audio Subsystem.
Signed-off-by: Sylwester Nawrocki
---
There were few rather significant additions since v3 and I had to drop tags:
Acked-by: Rob Herring
Acked-by:
This patch adds documentation of the DT bindings for the Samsung
Exynos SoC Low Power Audio Subsystem.
Signed-off-by: Sylwester Nawrocki
---
There were few rather significant additions since v3 and I had to drop tags:
Acked-by: Rob Herring
Acked-by: Krzysztof Kozlowski
Changes since v3:
-
On 05/07/16 17:59, Sebastian Frias wrote:
> Hi Marc,
>
> On 07/05/2016 06:48 PM, Marc Zyngier wrote:
>>> I already did something like that, you can see it here:
>>>
>>> https://marc.info/?l=linux-kernel=146592235919308=2
>>>
>>> the problem with that code is that it cannot handle more than 24
On 05/07/16 17:59, Sebastian Frias wrote:
> Hi Marc,
>
> On 07/05/2016 06:48 PM, Marc Zyngier wrote:
>>> I already did something like that, you can see it here:
>>>
>>> https://marc.info/?l=linux-kernel=146592235919308=2
>>>
>>> the problem with that code is that it cannot handle more than 24
This patch series adds a MFD driver for Samsung Exynos5433 SoC Low Power
Audio Subsystem and an ASoC machine driver for Exynos5433 based TM2/TM2E
boards.
The changes since v3 are listed in individual patches, the main change
was rewriting LPASS driver as a MFD driver. It seems much better now
as
This patch series adds a MFD driver for Samsung Exynos5433 SoC Low Power
Audio Subsystem and an ASoC machine driver for Exynos5433 based TM2/TM2E
boards.
The changes since v3 are listed in individual patches, the main change
was rewriting LPASS driver as a MFD driver. It seems much better now
as
On Tue 05 Jul 09:18 PDT 2016, Arvind Yadav wrote:
Your subject line should be a short and descriptive summary, followed by
an empty line and then potentially a longer description motivating your
patch. Please read section #14 of Documentation/SubmittingPatches.
> Signed-off-by: Arvind Yadav
On Tue 05 Jul 09:18 PDT 2016, Arvind Yadav wrote:
Your subject line should be a short and descriptive summary, followed by
an empty line and then potentially a longer description motivating your
patch. Please read section #14 of Documentation/SubmittingPatches.
> Signed-off-by: Arvind Yadav
>
Apply for a loan at 3% reply to this Email for more Info
Apply for a loan at 3% reply to this Email for more Info
Hi Marc,
On 07/05/2016 06:48 PM, Marc Zyngier wrote:
>> I already did something like that, you can see it here:
>>
>> https://marc.info/?l=linux-kernel=146592235919308=2
>>
>> the problem with that code is that it cannot handle more than 24 IRQs (the
>> number of outputs of the router), because
Hi Marc,
On 07/05/2016 06:48 PM, Marc Zyngier wrote:
>> I already did something like that, you can see it here:
>>
>> https://marc.info/?l=linux-kernel=146592235919308=2
>>
>> the problem with that code is that it cannot handle more than 24 IRQs (the
>> number of outputs of the router), because
On 05/07/16 12:47, Steven Rostedt wrote:
> On Tue, 5 Jul 2016 15:39:33 +0100
> Juri Lelli wrote:
>
> return;
> > > >
> > > > /*
> > > > +* Use the scheduling parameters of the top pi-waiter task,
> > > > +* if we have one from which we
On 05/07/16 12:47, Steven Rostedt wrote:
> On Tue, 5 Jul 2016 15:39:33 +0100
> Juri Lelli wrote:
>
> return;
> > > >
> > > > /*
> > > > +* Use the scheduling parameters of the top pi-waiter task,
> > > > +* if we have one from which we can inherit a
Hi,
[auto build test ERROR on miklos-vfs/overlayfs-next]
[also build test ERROR on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Vivek-Goyal/Overlayfs-SELinux-Support
Hi,
[auto build test ERROR on miklos-vfs/overlayfs-next]
[also build test ERROR on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Vivek-Goyal/Overlayfs-SELinux-Support
On Mon, 4 Jul 2016 14:49:52 +0800
Ganesh Mahendran wrote:
> This patch changes trace_zsmalloc_compact_start[end] to
> trace_zs_compact_start[end] to keep function naming consistent
> with others in zsmalloc
>
> Also this patch remove pages_total_compacted
On Mon, 4 Jul 2016 14:49:52 +0800
Ganesh Mahendran wrote:
> This patch changes trace_zsmalloc_compact_start[end] to
> trace_zs_compact_start[end] to keep function naming consistent
> with others in zsmalloc
>
> Also this patch remove pages_total_compacted information which
> may not really
401 - 500 of 1352 matches
Mail list logo