On Fri, 13 Apr 2018, Thomas Huth wrote:
> Selecting CONFIG_HDMI for S390 is inappropriate - there is no real
> graphic hardware on this architecture. The drm subsystem is only
> enabled here for using the virtual graphics card "virtio-gpu". So
> it should be possible to compile
On Fri, 13 Apr 2018, Thomas Huth wrote:
> Selecting CONFIG_HDMI for S390 is inappropriate - there is no real
> graphic hardware on this architecture. The drm subsystem is only
> enabled here for using the virtual graphics card "virtio-gpu". So
> it should be possible to compile the drm subsystem
> if (unlikely(par->debug & DEBUG_WRITE_REGISTER)) {\
> va_start(args, len); \
> for (i = 0; i < len; i++) { \
> - buf[i] =
> if (unlikely(par->debug & DEBUG_WRITE_REGISTER)) {\
> va_start(args, len); \
> for (i = 0; i < len; i++) { \
> - buf[i] =
On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote:
SNIP
> - !remove_name_list_str && !purge_name_list_str &&
> - !missing_filename && !update_name_list_str))
> + opts_flag = add_name_list_str || kcore_filename ||
> +
On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote:
SNIP
> - !remove_name_list_str && !purge_name_list_str &&
> - !missing_filename && !update_name_list_str))
> + opts_flag = add_name_list_str || kcore_filename ||
> +
On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote:
SNIP
> int cmd_buildid_cache(int argc, const char **argv)
> {
> struct strlist *list;
> @@ -304,6 +324,8 @@ int cmd_buildid_cache(int argc, const char **argv)
> int ret = 0;
> int ns_id = -1;
> bool force =
On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote:
SNIP
> int cmd_buildid_cache(int argc, const char **argv)
> {
> struct strlist *list;
> @@ -304,6 +324,8 @@ int cmd_buildid_cache(int argc, const char **argv)
> int ret = 0;
> int ns_id = -1;
> bool force =
On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote:
> Perf buildid-cache allows to add/remove files into cache but there
> is no option to list all cached files. Add --list option to list
> all _valid_ cached files.
>
> Ex,
> # perf buildid-cache --add /tmp/a.out
> # perf
On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote:
> Perf buildid-cache allows to add/remove files into cache but there
> is no option to list all cached files. Add --list option to list
> all _valid_ cached files.
>
> Ex,
> # perf buildid-cache --add /tmp/a.out
> # perf
On Fri, Apr 13, 2018 at 07:38:30AM +0200, Stephan Mueller wrote:
> > The crng_init variable has three states:
> >
> > 0: The CRNG is not initialized at all
> > 1: The CRNG has a small amount of entropy, hopefully good enough for
> >early-boot, non-cryptographical use cases
> > 2: The CRNG is
On Fri, Apr 13, 2018 at 07:38:30AM +0200, Stephan Mueller wrote:
> > The crng_init variable has three states:
> >
> > 0: The CRNG is not initialized at all
> > 1: The CRNG has a small amount of entropy, hopefully good enough for
> >early-boot, non-cryptographical use cases
> > 2: The CRNG is
On Fri 13-04-18 14:14:33, Michal Hocko wrote:
[...]
> Well, this is probably a matter of taste. I will not argue. I will not
> object if Johannes is OK with your patch. But the whole thing confused
> hell out of me so I would rather un-clutter it...
In other words, this
diff --git
On Fri 13-04-18 14:14:33, Michal Hocko wrote:
[...]
> Well, this is probably a matter of taste. I will not argue. I will not
> object if Johannes is OK with your patch. But the whole thing confused
> hell out of me so I would rather un-clutter it...
In other words, this
diff --git
On Fri, 2018-04-13 at 00:06 -0700, Greg Thelen wrote:
> Allow INFINIBAND without INFINIBAND_ADDR_TRANS.
>
> Signed-off-by: Greg Thelen
> Cc: Tarick Bedeir
> ---
> drivers/infiniband/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
On Fri, 2018-04-13 at 00:06 -0700, Greg Thelen wrote:
> Allow INFINIBAND without INFINIBAND_ADDR_TRANS.
>
> Signed-off-by: Greg Thelen
> Cc: Tarick Bedeir
> ---
> drivers/infiniband/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/Kconfig
Error messages printed by console drivers might cause an infinite loop.
In particular, writing a message might produce another message that
need to be written, etc.
The obvious solution is to remove these messages. But there many
non-trivial console drivers. Also showing printk() messages is not
Error messages printed by console drivers might cause an infinite loop.
In particular, writing a message might produce another message that
need to be written, etc.
The obvious solution is to remove these messages. But there many
non-trivial console drivers. Also showing printk() messages is not
On Fri, Apr 13, 2018 at 12:47:45PM +0100, Patrick Bellasi wrote:
> In the past I remember some funny dance in cgroup callbacks when a
> task was terminating (like being moved in the root-rq just before
> exiting). But, as you say, if we always have the task_rq_lock we
> should be safe.
The
On Fri, Apr 13, 2018 at 12:47:45PM +0100, Patrick Bellasi wrote:
> In the past I remember some funny dance in cgroup callbacks when a
> task was terminating (like being moved in the root-rq just before
> exiting). But, as you say, if we always have the task_rq_lock we
> should be safe.
The
On Thu 12-04-18 12:24:24, Matthew Wilcox wrote:
> On Thu, Apr 12, 2018 at 09:54:51AM +0900, Minchan Kim wrote:
> > Matthew,
> >
> > Please Cced relevant people so they know what's going on the problem
> > they spent on much time. Everyone doesn't keep an eye on mailing list.
>
> My apologies; I
On Thu 12-04-18 12:24:24, Matthew Wilcox wrote:
> On Thu, Apr 12, 2018 at 09:54:51AM +0900, Minchan Kim wrote:
> > Matthew,
> >
> > Please Cced relevant people so they know what's going on the problem
> > they spent on much time. Everyone doesn't keep an eye on mailing list.
>
> My apologies; I
On Thu, Apr 12, 2018 at 8:15 AM, Dmitry Vyukov wrote:
> On Wed, Feb 21, 2018 at 3:53 PM, Tommi Rantala
> wrote:
>> On 20.02.2018 18:26, Neil Horman wrote:
>>>
>>> On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote:
On Tue, Feb
On Thu, Apr 12, 2018 at 8:15 AM, Dmitry Vyukov wrote:
> On Wed, Feb 21, 2018 at 3:53 PM, Tommi Rantala
> wrote:
>> On 20.02.2018 18:26, Neil Horman wrote:
>>>
>>> On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote:
On Tue, Feb 20, 2018 at 8:56 AM, Tommi Rantala
wrote:
On Tue, Apr 10, 2018 at 06:40:04PM +0300, Alexey Budankov wrote:
SNIP
> Signed-off-by: Alexey Budankov
> ---
> Changes in v2:
> - lifted restriction on frame pointer architecture so it's value is provided
> as for i386 as for x86_64 processes
>
> MAINTAINERS
On Tue, Apr 10, 2018 at 06:40:04PM +0300, Alexey Budankov wrote:
SNIP
> Signed-off-by: Alexey Budankov
> ---
> Changes in v2:
> - lifted restriction on frame pointer architecture so it's value is provided
> as for i386 as for x86_64 processes
>
> MAINTAINERS file lacks references to
On Fri, 2018-04-13 at 13:23 +0200, Paolo Bonzini wrote:
> From: KarimAllah Ahmed
>
> Update 'tsc_offset' on vmenty/vmexit of L2 guests to ensure that it always
> captures the TSC_OFFSET of the running guest whether it is the L1 or L2
> guest.
>
> Cc: Jim Mattson
On Fri, 2018-04-13 at 13:23 +0200, Paolo Bonzini wrote:
> From: KarimAllah Ahmed
>
> Update 'tsc_offset' on vmenty/vmexit of L2 guests to ensure that it always
> captures the TSC_OFFSET of the running guest whether it is the L1 or L2
> guest.
>
> Cc: Jim Mattson
> Cc: Paolo Bonzini
> Cc:
On 04/13/2018 01:09 PM, Robin Murphy wrote:
> On 13/04/18 10:45, Pierre Yves MORDRET wrote:
>> Hi Robin
>>
>> On 04/11/2018 05:14 PM, Robin Murphy wrote:
>>> On 11/04/18 15:44, Pierre-Yves MORDRET wrote:
Both buffer Transfer Length (TLEN if any) and transfer size have to be
aligned on
On 04/13/2018 01:09 PM, Robin Murphy wrote:
> On 13/04/18 10:45, Pierre Yves MORDRET wrote:
>> Hi Robin
>>
>> On 04/11/2018 05:14 PM, Robin Murphy wrote:
>>> On 11/04/18 15:44, Pierre-Yves MORDRET wrote:
Both buffer Transfer Length (TLEN if any) and transfer size have to be
aligned on
2018-04-13 14:52 GMT+09:00 Kees Cook :
> On Thu, Apr 12, 2018 at 10:06 PM, Masahiro Yamada
> wrote:
>> [Major Changes in V3]
>
> Awesome work! I don't see this pushed to your git tree? I'd like to
> test it, but I'd rather "git fetch" instead
2018-04-13 14:52 GMT+09:00 Kees Cook :
> On Thu, Apr 12, 2018 at 10:06 PM, Masahiro Yamada
> wrote:
>> [Major Changes in V3]
>
> Awesome work! I don't see this pushed to your git tree? I'd like to
> test it, but I'd rather "git fetch" instead of "git am" :)
>
> -Kees
>
I pushed this series to
On Fri, Apr 13, 2018 at 5:39 PM, Maxime Ripard
wrote:
> On Fri, Apr 13, 2018 at 05:30:04PM +0530, Jagan Teki wrote:
>> On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
>> wrote:
>> > On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard
On Fri, Apr 13, 2018 at 5:39 PM, Maxime Ripard
wrote:
> On Fri, Apr 13, 2018 at 05:30:04PM +0530, Jagan Teki wrote:
>> On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
>> wrote:
>> > On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard wrote:
>> >> Hi,
>> >>
>> >> Here is an preliminary version
- On Apr 12, 2018, at 4:07 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Apr 12, 2018 at 12:59 PM, Mathieu Desnoyers
> wrote:
>>
>> What are your concerns about page pinning ?
>
> Pretty much everything.
>
> It's the most complex part by
- On Apr 12, 2018, at 4:07 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Apr 12, 2018 at 12:59 PM, Mathieu Desnoyers
> wrote:
>>
>> What are your concerns about page pinning ?
>
> Pretty much everything.
>
> It's the most complex part by far, and the vmalloc space is a
On Fri 13-04-18 15:07:14, Kirill Tkhai wrote:
> On 13.04.2018 14:54, Michal Hocko wrote:
> > On Fri 13-04-18 14:49:32, Kirill Tkhai wrote:
> >> On 13.04.2018 14:38, Michal Hocko wrote:
> >>> On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
> > [...]
> mem_cgroup_id_put_many() unpins css, but
On Fri 13-04-18 15:07:14, Kirill Tkhai wrote:
> On 13.04.2018 14:54, Michal Hocko wrote:
> > On Fri 13-04-18 14:49:32, Kirill Tkhai wrote:
> >> On 13.04.2018 14:38, Michal Hocko wrote:
> >>> On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
> > [...]
> mem_cgroup_id_put_many() unpins css, but
Hi Wolfram, Sam,
On Fri, 13 Apr 2018 00:24:57 +0200, Wolfram Sang wrote:
> On Thu, Apr 12, 2018 at 02:33:42PM -0700, Sam Hansen wrote:
> > Currently, Documentation/i2c/dev-interface describes the use of i2c_smbus_*
> > helper routines as static inlined functions provided by linux/i2c-dev.h.
> >
Hi Wolfram, Sam,
On Fri, 13 Apr 2018 00:24:57 +0200, Wolfram Sang wrote:
> On Thu, Apr 12, 2018 at 02:33:42PM -0700, Sam Hansen wrote:
> > Currently, Documentation/i2c/dev-interface describes the use of i2c_smbus_*
> > helper routines as static inlined functions provided by linux/i2c-dev.h.
> >
On Thu, Apr 12, 2018 at 8:27 PM, Roman Gushchin wrote:
> On Thu, Apr 12, 2018 at 08:52:52AM +0200, Vlastimil Babka wrote:
>> On 04/11/2018 03:56 PM, Roman Gushchin wrote:
>> > On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote:
>> >> [+CC linux-api]
>> >>
>> >> On
On Thu, Apr 12, 2018 at 8:27 PM, Roman Gushchin wrote:
> On Thu, Apr 12, 2018 at 08:52:52AM +0200, Vlastimil Babka wrote:
>> On 04/11/2018 03:56 PM, Roman Gushchin wrote:
>> > On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote:
>> >> [+CC linux-api]
>> >>
>> >> On 03/05/2018 02:37
On 4/13/2018 5:11 PM, Michal Hocko wrote:
On Fri 13-04-18 16:57:06, Chintan Pandya wrote:
On 4/13/2018 4:39 PM, Michal Hocko wrote:
On Fri 13-04-18 16:15:26, Chintan Pandya wrote:
On 4/13/2018 4:10 PM, Anshuman Khandual wrote:
On 04/13/2018 03:47 PM, Chintan Pandya wrote:
On
On 4/13/2018 5:11 PM, Michal Hocko wrote:
On Fri 13-04-18 16:57:06, Chintan Pandya wrote:
On 4/13/2018 4:39 PM, Michal Hocko wrote:
On Fri 13-04-18 16:15:26, Chintan Pandya wrote:
On 4/13/2018 4:10 PM, Anshuman Khandual wrote:
On 04/13/2018 03:47 PM, Chintan Pandya wrote:
On
On Fri, Apr 13, 2018 at 05:30:04PM +0530, Jagan Teki wrote:
> On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
> wrote:
> > On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard wrote:
> >> Hi,
> >>
> >> Here is an preliminary version of the MIPI-DSI support for the
On Fri, Apr 13, 2018 at 05:30:04PM +0530, Jagan Teki wrote:
> On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
> wrote:
> > On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard wrote:
> >> Hi,
> >>
> >> Here is an preliminary version of the MIPI-DSI support for the Allwinner
> >> SoCs.
> >>
> >>
On 13.04.2018 14:54, Michal Hocko wrote:
> On Fri 13-04-18 14:49:32, Kirill Tkhai wrote:
>> On 13.04.2018 14:38, Michal Hocko wrote:
>>> On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
> [...]
mem_cgroup_id_put_many() unpins css, but this may be not the last
reference to the css.
On 13.04.2018 14:54, Michal Hocko wrote:
> On Fri 13-04-18 14:49:32, Kirill Tkhai wrote:
>> On 13.04.2018 14:38, Michal Hocko wrote:
>>> On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
> [...]
mem_cgroup_id_put_many() unpins css, but this may be not the last
reference to the css.
On 04/13/2018 05:03 PM, Chintan Pandya wrote:
> Client can call vunmap with some intermediate 'addr'
> which may not be the start of the VM area. Entire
> unmap code works with vm->vm_start which is proper
> but debug object API is called with 'addr'. This
> could be a problem within debug
On 04/13/2018 05:03 PM, Chintan Pandya wrote:
> Client can call vunmap with some intermediate 'addr'
> which may not be the start of the VM area. Entire
> unmap code works with vm->vm_start which is proper
> but debug object API is called with 'addr'. This
> could be a problem within debug
Hi Eric,
On Fri, Apr 13, 2018 at 11:44 AM, Auger Eric wrote:
> On 13/04/18 11:19, Geert Uytterhoeven wrote:
>> On Fri, Apr 13, 2018 at 11:14 AM, Auger Eric wrote:
>>> On 11/04/18 11:24, Geert Uytterhoeven wrote:
If a device is part of a PM
Hi Eric,
On Fri, Apr 13, 2018 at 11:44 AM, Auger Eric wrote:
> On 13/04/18 11:19, Geert Uytterhoeven wrote:
>> On Fri, Apr 13, 2018 at 11:14 AM, Auger Eric wrote:
>>> On 11/04/18 11:24, Geert Uytterhoeven wrote:
If a device is part of a PM Domain (e.g. power and/or clock domain), its
On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
wrote:
> On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard wrote:
>> Hi,
>>
>> Here is an preliminary version of the MIPI-DSI support for the Allwinner
>> SoCs.
>>
>> This controller can be found on a number of recent
On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
wrote:
> On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard wrote:
>> Hi,
>>
>> Here is an preliminary version of the MIPI-DSI support for the Allwinner
>> SoCs.
>>
>> This controller can be found on a number of recent SoCs, such as the
>> A31,
Hi Philipp,
On Fri, Apr 13, 2018 at 11:22 AM, Philipp Zabel wrote:
> On Thu, 2018-04-12 at 18:02 +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 12, 2018 at 4:10 PM, Philipp Zabel
>> wrote:
>> > On Thu, 2018-04-12 at 15:12 +0200, Geert
Hi Philipp,
On Fri, Apr 13, 2018 at 11:22 AM, Philipp Zabel wrote:
> On Thu, 2018-04-12 at 18:02 +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 12, 2018 at 4:10 PM, Philipp Zabel
>> wrote:
>> > On Thu, 2018-04-12 at 15:12 +0200, Geert Uytterhoeven wrote:
>> > > On Thu, Apr 12, 2018 at 2:36
On Fri 13-04-18 14:49:32, Kirill Tkhai wrote:
> On 13.04.2018 14:38, Michal Hocko wrote:
> > On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
[...]
> >> mem_cgroup_id_put_many() unpins css, but this may be not the last
> >> reference to the css.
> >> Thus, we release ID earlier, then all references
On Fri 13-04-18 14:49:32, Kirill Tkhai wrote:
> On 13.04.2018 14:38, Michal Hocko wrote:
> > On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
[...]
> >> mem_cgroup_id_put_many() unpins css, but this may be not the last
> >> reference to the css.
> >> Thus, we release ID earlier, then all references
On 13-Apr 12:47, Patrick Bellasi wrote:
> On 13-Apr 13:36, Peter Zijlstra wrote:
> > On Fri, Apr 13, 2018 at 12:15:10PM +0100, Patrick Bellasi wrote:
> > > On 13-Apr 10:43, Peter Zijlstra wrote:
> > > > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote:
> > > > > +static inline void
On 13-Apr 12:47, Patrick Bellasi wrote:
> On 13-Apr 13:36, Peter Zijlstra wrote:
> > On Fri, Apr 13, 2018 at 12:15:10PM +0100, Patrick Bellasi wrote:
> > > On 13-Apr 10:43, Peter Zijlstra wrote:
> > > > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote:
> > > > > +static inline void
On 13.04.2018 14:38, Michal Hocko wrote:
> On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
>> On 13.04.2018 14:20, Michal Hocko wrote:
>>> On Fri 13-04-18 14:06:40, Kirill Tkhai wrote:
On 13.04.2018 14:02, Michal Hocko wrote:
> On Fri 13-04-18 12:35:22, Kirill Tkhai wrote:
>> On
On 13.04.2018 14:38, Michal Hocko wrote:
> On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
>> On 13.04.2018 14:20, Michal Hocko wrote:
>>> On Fri 13-04-18 14:06:40, Kirill Tkhai wrote:
On 13.04.2018 14:02, Michal Hocko wrote:
> On Fri 13-04-18 12:35:22, Kirill Tkhai wrote:
>> On
On 11/04/18 15:44, Pierre-Yves MORDRET wrote:
Only 1 Hw Descriptor is allocated. Loop over required Hw descriptor for
proper allocation.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v1:
* Initial
v2:
* Fix kbuild warning
On 11/04/18 15:44, Pierre-Yves MORDRET wrote:
Only 1 Hw Descriptor is allocated. Loop over required Hw descriptor for
proper allocation.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v1:
* Initial
v2:
* Fix kbuild warning format: /0x%08x/%pad/
---
---
It's less overhead, clearer and generally neater.
Signed-off-by: Peter Rosin
---
sound/soc/codecs/tfa9879.c | 18 ++
sound/soc/codecs/tfa9879.h | 7 +--
2 files changed, 7 insertions(+), 18 deletions(-)
diff --git a/sound/soc/codecs/tfa9879.c
It's less overhead, clearer and generally neater.
Signed-off-by: Peter Rosin
---
sound/soc/codecs/max9860.c | 31 +++
sound/soc/codecs/max9860.h | 10 +-
2 files changed, 12 insertions(+), 29 deletions(-)
diff --git
It's less overhead, clearer and generally neater.
Signed-off-by: Peter Rosin
---
sound/soc/codecs/tfa9879.c | 18 ++
sound/soc/codecs/tfa9879.h | 7 +--
2 files changed, 7 insertions(+), 18 deletions(-)
diff --git a/sound/soc/codecs/tfa9879.c b/sound/soc/codecs/tfa9879.c
It's less overhead, clearer and generally neater.
Signed-off-by: Peter Rosin
---
sound/soc/codecs/max9860.c | 31 +++
sound/soc/codecs/max9860.h | 10 +-
2 files changed, 12 insertions(+), 29 deletions(-)
diff --git a/sound/soc/codecs/max9860.c
On 2018-04-13 13:19, Mark Brown wrote:
> On Thu, Apr 12, 2018 at 11:14:35PM +0200, Peter Rosin wrote:
>
>> @@ -1,3 +1,4 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> /*
>> * Driver for the MAX9860 Mono Audio Voice Codec
>> *
>
> Please don't mix C and C++ comments like this - it looks
On 2018-04-13 13:19, Mark Brown wrote:
> On Thu, Apr 12, 2018 at 11:14:35PM +0200, Peter Rosin wrote:
>
>> @@ -1,3 +1,4 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> /*
>> * Driver for the MAX9860 Mono Audio Voice Codec
>> *
>
> Please don't mix C and C++ comments like this - it looks
On 13/04/2018 13:23, Sudeep Holla wrote:
> Hi Daniel,
>
> On 05/04/18 17:16, Daniel Lezcano wrote:
>
> [...]
>
>> +/**
>> + * cpuidle_cooling_register - Idle cooling device initialization function
>> + *
>> + * This function is in charge of creating a cooling device per cluster
>> + * and
On 13/04/2018 13:23, Sudeep Holla wrote:
> Hi Daniel,
>
> On 05/04/18 17:16, Daniel Lezcano wrote:
>
> [...]
>
>> +/**
>> + * cpuidle_cooling_register - Idle cooling device initialization function
>> + *
>> + * This function is in charge of creating a cooling device per cluster
>> + * and
On 13-Apr 13:36, Peter Zijlstra wrote:
> On Fri, Apr 13, 2018 at 12:15:10PM +0100, Patrick Bellasi wrote:
> > On 13-Apr 10:43, Peter Zijlstra wrote:
> > > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote:
> > > > +static inline void uclamp_task_update(struct rq *rq, struct
> > > >
On 13-Apr 13:36, Peter Zijlstra wrote:
> On Fri, Apr 13, 2018 at 12:15:10PM +0100, Patrick Bellasi wrote:
> > On 13-Apr 10:43, Peter Zijlstra wrote:
> > > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote:
> > > > +static inline void uclamp_task_update(struct rq *rq, struct
> > > >
On 13/04/2018 13:38, Daniel Thompson wrote:
[ ... ]
>> +/*
>> + * Allocate the cpuidle cooling device with the list
>> + * of the cpus belonging to the cluster.
>> + */
>> +idle_cdev = cpuidle_cooling_alloc(topology_core_cpumask(cpu));
On 13/04/2018 13:38, Daniel Thompson wrote:
[ ... ]
>> +/*
>> + * Allocate the cpuidle cooling device with the list
>> + * of the cpus belonging to the cluster.
>> + */
>> +idle_cdev = cpuidle_cooling_alloc(topology_core_cpumask(cpu));
On Fri 13-04-18 16:57:06, Chintan Pandya wrote:
>
>
> On 4/13/2018 4:39 PM, Michal Hocko wrote:
> > On Fri 13-04-18 16:15:26, Chintan Pandya wrote:
> > >
> > >
> > > On 4/13/2018 4:10 PM, Anshuman Khandual wrote:
> > > > On 04/13/2018 03:47 PM, Chintan Pandya wrote:
> > > > >
> > > > >
> > >
On Fri 13-04-18 16:57:06, Chintan Pandya wrote:
>
>
> On 4/13/2018 4:39 PM, Michal Hocko wrote:
> > On Fri 13-04-18 16:15:26, Chintan Pandya wrote:
> > >
> > >
> > > On 4/13/2018 4:10 PM, Anshuman Khandual wrote:
> > > > On 04/13/2018 03:47 PM, Chintan Pandya wrote:
> > > > >
> > > > >
> > >
On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
> On 13.04.2018 14:20, Michal Hocko wrote:
> > On Fri 13-04-18 14:06:40, Kirill Tkhai wrote:
> >> On 13.04.2018 14:02, Michal Hocko wrote:
> >>> On Fri 13-04-18 12:35:22, Kirill Tkhai wrote:
> On 13.04.2018 11:55, Michal Hocko wrote:
> > On
On Fri 13-04-18 14:29:11, Kirill Tkhai wrote:
> On 13.04.2018 14:20, Michal Hocko wrote:
> > On Fri 13-04-18 14:06:40, Kirill Tkhai wrote:
> >> On 13.04.2018 14:02, Michal Hocko wrote:
> >>> On Fri 13-04-18 12:35:22, Kirill Tkhai wrote:
> On 13.04.2018 11:55, Michal Hocko wrote:
> > On
On Thu, Apr 12, 2018 at 02:15:30PM +0200, Dmitry Vyukov wrote:
> On Wed, Feb 21, 2018 at 3:53 PM, Tommi Rantala
> wrote:
> > On 20.02.2018 18:26, Neil Horman wrote:
> >>
> >> On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote:
> >>>
> >>> On Tue, Feb 20, 2018
On Thu, Apr 12, 2018 at 02:15:30PM +0200, Dmitry Vyukov wrote:
> On Wed, Feb 21, 2018 at 3:53 PM, Tommi Rantala
> wrote:
> > On 20.02.2018 18:26, Neil Horman wrote:
> >>
> >> On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote:
> >>>
> >>> On Tue, Feb 20, 2018 at 8:56 AM, Tommi Rantala
On Thu, Apr 05, 2018 at 06:16:43PM +0200, Daniel Lezcano wrote:
> +/**
> + * cpuidle_cooling_register - Idle cooling device initialization function
> + *
> + * This function is in charge of creating a cooling device per cluster
> + * and register it to thermal framework. For this we rely on the
>
On Thu, Apr 05, 2018 at 06:16:43PM +0200, Daniel Lezcano wrote:
> +/**
> + * cpuidle_cooling_register - Idle cooling device initialization function
> + *
> + * This function is in charge of creating a cooling device per cluster
> + * and register it to thermal framework. For this we rely on the
>
In order to reset busy HW properly, memory controller needs to be
involved, otherwise it is possible to get corrupted memory or hang machine
if HW was reset during DMA. Introduce memory client 'hot reset' that will
be used for resetting of busy HW.
Signed-off-by: Dmitry Osipenko
In order to reset busy HW properly, memory controller needs to be
involved, otherwise it is possible to get corrupted memory or hang machine
if HW was reset during DMA. Introduce memory client 'hot reset' that will
be used for resetting of busy HW.
Signed-off-by: Dmitry Osipenko
---
Define the table of memory controller hot resets for Tegra124.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra124.c | 42 +
1 file changed, 42 insertions(+)
diff --git a/drivers/memory/tegra/tegra124.c
Define the table of memory controller hot resets for Tegra124.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra124.c | 42 +
1 file changed, 42 insertions(+)
diff --git a/drivers/memory/tegra/tegra124.c b/drivers/memory/tegra/tegra124.c
index
On Fri, Apr 13, 2018 at 12:15:10PM +0100, Patrick Bellasi wrote:
> On 13-Apr 10:43, Peter Zijlstra wrote:
> > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote:
> > > +static inline void uclamp_task_update(struct rq *rq, struct task_struct
> > > *p)
> > > +{
> > > + int cpu =
On Fri, Apr 13, 2018 at 12:15:10PM +0100, Patrick Bellasi wrote:
> On 13-Apr 10:43, Peter Zijlstra wrote:
> > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote:
> > > +static inline void uclamp_task_update(struct rq *rq, struct task_struct
> > > *p)
> > > +{
> > > + int cpu =
Define the table of memory controller hot resets for Tegra20 and add
specific to Tegra20 hot reset operations.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20.c | 118 +
1 file changed, 118 insertions(+)
diff --git
Define the table of memory controller hot resets for Tegra20 and add
specific to Tegra20 hot reset operations.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20.c | 118 +
1 file changed, 118 insertions(+)
diff --git
From: Thierry Reding
Define the table of memory controller hot resets for Tegra210.
Signed-off-by: Thierry Reding
---
drivers/memory/tegra/tegra210.c | 45 +
1 file changed, 45 insertions(+)
diff --git
From: Thierry Reding
Define the table of memory controller hot resets for Tegra210.
Signed-off-by: Thierry Reding
---
drivers/memory/tegra/tegra210.c | 45 +
1 file changed, 45 insertions(+)
diff --git a/drivers/memory/tegra/tegra210.c
Define the table of memory controller hot resets for Tegra114.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra114.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/memory/tegra/tegra114.c
Define the table of memory controller hot resets for Tegra114.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra114.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/memory/tegra/tegra114.c b/drivers/memory/tegra/tegra114.c
index
Define the table of memory controller hot resets for Tegra30.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra30.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/memory/tegra/tegra30.c
Define the table of memory controller hot resets for Tegra30.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra30.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/memory/tegra/tegra30.c b/drivers/memory/tegra/tegra30.c
index
On 12 April 2018 at 20:22, Peter Zijlstra wrote:
> On Tue, Apr 10, 2018 at 02:19:50PM +0100, Morten Rasmussen wrote:
>> As said above, I see your point about completion time might suffer in
>> some cases for low utilization tasks, but I don't see how you can fix
>> that
On 12 April 2018 at 20:22, Peter Zijlstra wrote:
> On Tue, Apr 10, 2018 at 02:19:50PM +0100, Morten Rasmussen wrote:
>> As said above, I see your point about completion time might suffer in
>> some cases for low utilization tasks, but I don't see how you can fix
>> that automagically.
801 - 900 of 1298 matches
Mail list logo