On 6/25/19 10:39 AM, Waiman Long wrote:
> When the handoff bit is set by a writer, no other tasks other than
> the setting writer itself is allowed to acquire the lock. If the
> to-be-handoff'ed writer goes to sleep, there will be a wakeup latency
> period where the lock is free, but no one can
Fievel is a Chromebox and Tiger a Chromebase with a 10" display and
touchscreen. Tiger and Fievel are based on the same board.
Signed-off-by: Matthias Kaehlcke
---
Changes in v3:
- patch added to the series
---
.../devicetree/bindings/arm/rockchip.yaml | 30 +++
1 file
Commit-ID: a1dc0446d64966dc0ae756aebdc449f335742c13
Gitweb: https://git.kernel.org/tip/a1dc0446d64966dc0ae756aebdc449f335742c13
Author: Qian Cai
AuthorDate: Fri, 19 Jul 2019 21:23:19 -0400
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:05 +0200
sched/core: Silence a warning
The pull request you sent on Wed, 24 Jul 2019 13:34:03 -0700 (PDT):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
> tags/riscv/for-v5.3-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a51edf751b660f3fc1d0724bc4cb839bdaf5576c
Thank you!
--
The pull request you sent on Thu, 25 Jul 2019 11:26:29 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-5.3-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6789f873ed373319cbf83b56455baf00769bb79a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Wed, 24 Jul 2019 15:47:11 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
> ktest-v5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/da3cc2e6f168fd52630892f4672f2f26bd217198
Thank you!
--
Deet-doot-dot,
Commit-ID: a07db5c0865799ebed1f88be0df50c581fb65029
Gitweb: https://git.kernel.org/tip/a07db5c0865799ebed1f88be0df50c581fb65029
Author: Juri Lelli
AuthorDate: Fri, 19 Jul 2019 08:34:55 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:05 +0200
sched/core: Fix CPU
Commit-ID: 710da3c8ea7dfbd327920afd3831d8c82c42789d
Gitweb: https://git.kernel.org/tip/710da3c8ea7dfbd327920afd3831d8c82c42789d
Author: Juri Lelli
AuthorDate: Fri, 19 Jul 2019 16:00:00 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:04 +0200
sched/core: Prevent race
Commit-ID: 1a763fd7c6335e3122c1cc09576ef6c99ada4267
Gitweb: https://git.kernel.org/tip/1a763fd7c6335e3122c1cc09576ef6c99ada4267
Author: Juri Lelli
AuthorDate: Fri, 19 Jul 2019 15:59:59 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:03 +0200
rcu/tree: Call
+Rajat
> -Original Message-
> From: Kai-Heng Feng
> Sent: Thursday, July 25, 2019 9:03 AM
> To: Rafael J. Wysocki
> Cc: Keith Busch; Christoph Hellwig; Sagi Grimberg; linux-
> n...@lists.infradead.org; Limonciello, Mario; Linux PM; LKML
> Subject: Re: [Regression] Commit "nvme/pci: Use
Hi Chanwoo,
On 7/24/19 12:24 PM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 19. 7. 24. 오후 7:15, Lukasz Luba wrote:
>> Hi Chanwoo,
>>
>> Could you have a look a this patch, please?
>> This patch has been rewritten accorifing to your suggestion.
>> Krzysztof tried to apply 5/5 DT patch on his current
Commit-ID: d74b27d63a8bebe2fe634944e4ebdc7b10db7a39
Gitweb: https://git.kernel.org/tip/d74b27d63a8bebe2fe634944e4ebdc7b10db7a39
Author: Juri Lelli
AuthorDate: Fri, 19 Jul 2019 15:59:58 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:03 +0200
cgroup/cpuset: Change
Commit-ID: 1243dc518c9da467da6635313a2dbb41b8ffc275
Gitweb: https://git.kernel.org/tip/1243dc518c9da467da6635313a2dbb41b8ffc275
Author: Juri Lelli
AuthorDate: Fri, 19 Jul 2019 15:59:57 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:02 +0200
cgroup/cpuset: Convert
Commit-ID: 59d06cea1198d665ba11f7e8c5f45b00ff2e4812
Gitweb: https://git.kernel.org/tip/59d06cea1198d665ba11f7e8c5f45b00ff2e4812
Author: Juri Lelli
AuthorDate: Fri, 19 Jul 2019 15:59:56 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:02 +0200
sched/deadline: Fix
Em Thu, 25 Jul 2019 11:17:55 -0300
Ezequiel Garcia escreveu:
> In order to introduce support for RK3399 VP8 decoding,
> move some common VP8 code. This will be reused by
> the RK3399 implementation, reducing code duplication.
>
> Signed-off-by: Ezequiel Garcia
> ---
>
Commit-ID: f9a25f776d780bfa3279f0b6e5f5cf3224997976
Gitweb: https://git.kernel.org/tip/f9a25f776d780bfa3279f0b6e5f5cf3224997976
Author: Mathieu Poirier
AuthorDate: Fri, 19 Jul 2019 15:59:55 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:55:01 +0200
cpusets: Rebuild root
Commit-ID: 4b211f2b129dd1f6a6956bbc76e2f232c1ec3ad8
Gitweb: https://git.kernel.org/tip/4b211f2b129dd1f6a6956bbc76e2f232c1ec3ad8
Author: Mathieu Poirier
AuthorDate: Fri, 19 Jul 2019 15:59:54 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:57 +0200
sched/core: Streamle
On Thu, Jul 25, 2019 at 06:10:37PM +0200, Paolo Bonzini wrote:
> On 25/07/19 18:09, Sean Christopherson wrote:
> >> This investigation confirms it is a new test code failure on stable-rc
> >> 5.2.3
> > No, it only confirms that kvm-unit-tests/master fails on 5.2.*. To confirm
> > a new failure
Hi Lee,
> On Thu, 18 Jul 2019, Lukasz Majewski wrote:
>
> > From: Sascha Hauer
> >
> > The mc34708 has an improved adc. The older variants will always
> > convert a fixed order of channels. The mc34708 can do up to eight
> > conversions in arbitrary channel order. Currently this extended
> >
Commit-ID: c22645f4c8f021fb1c5e7189eb1f968132cc0844
Gitweb: https://git.kernel.org/tip/c22645f4c8f021fb1c5e7189eb1f968132cc0844
Author: Mathieu Poirier
AuthorDate: Fri, 19 Jul 2019 15:59:53 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:57 +0200
sched/topology: Add
Commit-ID: 60e17f5cef838e9ca7946ced208ceddcec6c315d
Gitweb: https://git.kernel.org/tip/60e17f5cef838e9ca7946ced208ceddcec6c315d
Author: Viresh Kumar
AuthorDate: Tue, 4 Jun 2019 12:31:52 +0530
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:56 +0200
sched/fair: Introduce
Commit-ID: e0e8d4911ed2695b12c3a01c15634000ede9bc73
Gitweb: https://git.kernel.org/tip/e0e8d4911ed2695b12c3a01c15634000ede9bc73
Author: Wanpeng Li
AuthorDate: Fri, 28 Jun 2019 16:51:41 +0800
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:55 +0200
sched/isolation: Prefer
Commit-ID: 65d74e91694e1afac40c96fb64a9ef120757729e
Gitweb: https://git.kernel.org/tip/65d74e91694e1afac40c96fb64a9ef120757729e
Author: Yi Wang
AuthorDate: Fri, 5 Jul 2019 12:35:07 +0800
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:55 +0200
sched/stats: Fix unlikely() use
Tony will start to officially maintain EDAC trees. Also, we'll
be using a single tree for the EDAC development.
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 783569e3c4b4..7c22905b5aba
Commit-ID: 3c29e651e16dd3b3179cfb2d055ee9538e37515c
Gitweb: https://git.kernel.org/tip/3c29e651e16dd3b3179cfb2d055ee9538e37515c
Author: Viresh Kumar
AuthorDate: Wed, 26 Jun 2019 10:36:30 +0530
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:54 +0200
sched/fair: Fall back to
Commit-ID: 7b3c92b85a65c2db1f542265bc98e1f9e3056eba
Gitweb: https://git.kernel.org/tip/7b3c92b85a65c2db1f542265bc98e1f9e3056eba
Author: Matthew Wilcox (Oracle)
AuthorDate: Thu, 4 Jul 2019 15:13:23 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:54 +0200
sched/core:
On Thu, 2019-07-25 at 11:16 -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 25, 2019 at 08:05:30AM -0700, Alexander Duyck wrote:
> > On Thu, 2019-07-25 at 07:35 -0400, Nitesh Narayan Lal wrote:
> > > On 7/24/19 6:03 PM, Alexander Duyck wrote:
> > > > On Wed, 2019-07-24 at 17:38 -0400, Michael S.
Commit-ID: 43e9f7f231e40e4534fc3a735da152911a085c16
Gitweb: https://git.kernel.org/tip/43e9f7f231e40e4534fc3a735da152911a085c16
Author: Viresh Kumar
AuthorDate: Wed, 26 Jun 2019 10:36:29 +0530
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:53 +0200
sched/fair: Start
Commit-ID: 84ec3a0787086fcd25f284f59b3aa01fd6fc0a5d
Gitweb: https://git.kernel.org/tip/84ec3a0787086fcd25f284f59b3aa01fd6fc0a5d
Author: Paul E. McKenney
AuthorDate: Tue, 25 Jun 2019 09:52:38 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:53 +0200
time/tick-broadcast:
Commit-ID: 9434f9f5d117302cc7ddf038e7879f6871dc7a81
Gitweb: https://git.kernel.org/tip/9434f9f5d117302cc7ddf038e7879f6871dc7a81
Author: Valentin Schneider
AuthorDate: Mon, 15 Jul 2019 11:25:08 +0100
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:52 +0200
sched/fair: Change
Commit-ID: f6cad8df6b30a5d2bbbd2e698f74b4cafb9fb82b
Gitweb: https://git.kernel.org/tip/f6cad8df6b30a5d2bbbd2e698f74b4cafb9fb82b
Author: Vincent Guittot
AuthorDate: Mon, 1 Jul 2019 17:47:02 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:52 +0200
sched/fair: Fix
On 07/25, Christian Brauner wrote:
>
> The key is that you want to be able to create child processes in a
> shared library without the main programing having to know about this so
> that it can use P_ALL and never get stuff from the library.
OK, thanks...
in this case you should probablu pass 0
Commit-ID: b34920d4ce6e6fc9424c20a4be98676eb543122f
Gitweb: https://git.kernel.org/tip/b34920d4ce6e6fc9424c20a4be98676eb543122f
Author: Valentin Schneider
AuthorDate: Mon, 15 Jul 2019 11:25:07 +0100
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:51 +0200
sched/fair: Move
Commit-ID: d35927a144641700c8328d707d1c89d305b4ecb8
Gitweb: https://git.kernel.org/tip/d35927a144641700c8328d707d1c89d305b4ecb8
Author: Valentin Schneider
AuthorDate: Mon, 15 Jul 2019 11:25:06 +0100
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:51:51 +0200
sched/fair: Move
Commit-ID: 8c779229d0f4fe83ead90bdcbbf08b02989aa200
Gitweb: https://git.kernel.org/tip/8c779229d0f4fe83ead90bdcbbf08b02989aa200
Author: Bart Van Assche
AuthorDate: Mon, 22 Jul 2019 11:24:43 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:43:28 +0200
locking/lockdep:
On 25/07/19 18:09, Sean Christopherson wrote:
>> This investigation confirms it is a new test code failure on stable-rc 5.2.3
> No, it only confirms that kvm-unit-tests/master fails on 5.2.*. To confirm
> a new failure in 5.2.3 you would need to show a test that passes on 5.2.2
> and fails on
Commit-ID: 12593b7467f9130b64a6d4b6a26ed4ec217b6784
Gitweb: https://git.kernel.org/tip/12593b7467f9130b64a6d4b6a26ed4ec217b6784
Author: Bart Van Assche
AuthorDate: Mon, 22 Jul 2019 11:24:42 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:43:27 +0200
locking/lockdep:
On Thu, Jul 25, 2019 at 07:35:13PM +0530, Naresh Kamboju wrote:
> Paolo,
>
> On Thu, 25 Jul 2019 at 19:17, Paolo Bonzini wrote:
> >
> > On 25/07/19 13:34, Greg Kroah-Hartman wrote:
> > > Any chance you can run 'git bisect' to find the offending patch? Or
> > > just try reverting a few, you can
Commit-ID: a2970421640bd9b6a78f2685d7750a791abdfd4e
Gitweb: https://git.kernel.org/tip/a2970421640bd9b6a78f2685d7750a791abdfd4e
Author: Bart Van Assche
AuthorDate: Mon, 22 Jul 2019 11:24:41 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:43:26 +0200
stacktrace: Constify
On Fri, Jul 26, 2019 at 01:14:26AM +1000, Daniel Axtens wrote:
> Mark Rutland writes:
> > On Thu, Jul 25, 2019 at 09:53:08AM +0200, Dmitry Vyukov wrote:
> >> FTR, Daniel just mailed:
> >>
> >> [PATCH 0/3] kasan: support backing vmalloc space with real shadow memory
> >>
Commit-ID: 364f6afc4f5537b79cf454eb35cae92920676075
Gitweb: https://git.kernel.org/tip/364f6afc4f5537b79cf454eb35cae92920676075
Author: Bart Van Assche
AuthorDate: Mon, 22 Jul 2019 11:24:40 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:43:26 +0200
locking/lockdep: Make
Commit-ID: 4ce54af8b33d3e21ca935fc1b89b58cbba956051
Gitweb: https://git.kernel.org/tip/4ce54af8b33d3e21ca935fc1b89b58cbba956051
Author: Leonard Crestez
AuthorDate: Wed, 24 Jul 2019 15:53:24 +0300
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:41:31 +0200
perf/core: Fix
Commit-ID: 5ea3f6fb37b79da33ac9211df336fd2b9f47c39f
Gitweb: https://git.kernel.org/tip/5ea3f6fb37b79da33ac9211df336fd2b9f47c39f
Author: Zhenzhong Duan
AuthorDate: Thu, 25 Jul 2019 10:39:26 +0800
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:41:30 +0200
perf/x86: Apply more
Commit-ID: 3b238a64c3009fed36eaea1af629d9377759d87d
Gitweb: https://git.kernel.org/tip/3b238a64c3009fed36eaea1af629d9377759d87d
Author: Yunying Sun
AuthorDate: Wed, 24 Jul 2019 16:29:32 +0800
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:41:30 +0200
perf/x86/intel: Fix
Commit-ID: 3d0c3953601d250175c7684ec0d9df612061dae5
Gitweb: https://git.kernel.org/tip/3d0c3953601d250175c7684ec0d9df612061dae5
Author: Kan Liang
AuthorDate: Tue, 23 Jul 2019 13:04:29 -0700
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:41:29 +0200
perf/x86/intel: Fix SLOTS
Commit-ID: 6c11c6e3d5e9e5caf8686cd6a5e4552cfc3ea326
Gitweb: https://git.kernel.org/tip/6c11c6e3d5e9e5caf8686cd6a5e4552cfc3ea326
Author: Sebastian Andrzej Siewior
AuthorDate: Wed, 3 Jul 2019 11:21:26 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:39:27 +0200
Commit-ID: 30a35f79faadfeb1b89a7fdb3875f14063519041
Gitweb: https://git.kernel.org/tip/30a35f79faadfeb1b89a7fdb3875f14063519041
Author: Arnd Bergmann
AuthorDate: Fri, 28 Jun 2019 12:29:03 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:39:26 +0200
locking/lockdep: Clean
Commit-ID: 68037aa78208f34bda4e5cd76c357f718b838cbb
Gitweb: https://git.kernel.org/tip/68037aa78208f34bda4e5cd76c357f718b838cbb
Author: Arnd Bergmann
AuthorDate: Mon, 15 Jul 2019 11:27:49 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:39:25 +0200
locking/lockdep: Hide
This patch introduces MHP_MEMMAP_ON_MEMORY flag,
and prepares the callers that add memory to take a "flags" parameter.
This "flags" parameter will be evaluated later on in Patch#3
to init mhp_restrictions struct.
The callers are:
add_memory
__add_memory
add_memory_resource
Unfortunately, we do
When hot-removing memory, we need to be careful about two things:
1) Memory range must be memory_block aligned. This is what
check_hotplug_memory_range() checks for.
2) If a range was hot-added using MHP_MEMMAP_ON_MEMORY, we need to check
whether the caller is removing memory with the same
Here we go with v3.
v3 -> v2:
* Rewrite about vmemmap pages handling.
Prior to this version, I was (ab)using hugepages fields
from struct page, while here I am officially adding a new
sub-page type with the fields I need.
* Drop
Physical memory hotadd has to allocate a memmap (struct page array) for
the newly added memory section. Currently, alloc_pages_node() is used
for those allocations.
This has some disadvantages:
a) an existing memory is consumed for that purpose
(~2MB per 128MB memory section on x86_64)
b)
It seems that we have some users out there that want to expose all
hotpluggable memory to userspace, so this implements a toggling mechanism
for those users who want to disable it.
By default, vmemmap pages mechanism is enabled.
Signed-off-by: Oscar Salvador
---
drivers/base/memory.c
This patch introduces a new Vmemmap page-type.
It also introduces some functions to ease the handling of vmemmap pages:
- vmemmap_nr_sections: Returns the number of sections that used vmemmap.
- vmemmap_nr_pages: Allows us to retrieve the amount of vmemmap pages
derivated from any
On 2019-07-25 5:50 a.m., Christoph Hellwig wrote:
> On Wed, Jul 24, 2019 at 10:06:22AM -0600, Logan Gunthorpe wrote:
>> Yes. This is the downside of dealing only with a phys_addr_t: we have to
>> look up against it. Unfortunately, I believe it's possible for different
>> BARs on a device to be
Commit-ID: e1b98fa316648420d0434d9ff5b92ad6609ba6c3
Gitweb: https://git.kernel.org/tip/e1b98fa316648420d0434d9ff5b92ad6609ba6c3
Author: Jan Stancek
AuthorDate: Thu, 18 Jul 2019 10:51:25 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:39:23 +0200
locking/rwsem: Add missing
On 2019-07-25 12:10 a.m., Christoph Hellwig wrote:
> On Wed, Jul 24, 2019 at 09:58:59AM -0600, Logan Gunthorpe wrote:
>>
>>
>> On 2019-07-24 12:32 a.m., Christoph Hellwig wrote:
struct dev_pagemap *pgmap = sg_page(sg)->pgmap;
+ struct pci_dev *client;
+ int dist;
+
On Thu, 25 Jul 2019 at 07:56, Ingo Molnar wrote:
>
>
> * Ingo Molnar wrote:
>
> >
> > * Juri Lelli wrote:
> >
> > > When the topology of root domains is modified by CPUset or CPUhotplug
> > > operations information about the current deadline bandwidth held in the
> > > root domain is lost.
> >
Commit-ID: 78134300579a45f527ca173ec8fdb4701b69f16e
Gitweb: https://git.kernel.org/tip/78134300579a45f527ca173ec8fdb4701b69f16e
Author: Waiman Long
AuthorDate: Sat, 20 Jul 2019 11:04:10 -0400
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:39:22 +0200
locking/rwsem: Don't call
Commit-ID: cb361d8cdef69990f6b4504dc1fd9a594d983c97
Gitweb: https://git.kernel.org/tip/cb361d8cdef69990f6b4504dc1fd9a594d983c97
Author: Jann Horn
AuthorDate: Tue, 16 Jul 2019 17:20:47 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:37:05 +0200
sched/fair: Use RCU
On Thu, Jul 25, 2019 at 1:53 AM David Hildenbrand wrote:
>
> On 24.07.19 19:03, Alexander Duyck wrote:
> > From: Alexander Duyck
> > /*
> > + * PageHinted() is an alias for Offline, however it is not meant to be an
> > + * exclusive value. It should be combined with PageBuddy() when seen as
Commit-ID: 16d51a590a8ce3befb1308e0e7ab77f3b661af33
Gitweb: https://git.kernel.org/tip/16d51a590a8ce3befb1308e0e7ab77f3b661af33
Author: Jann Horn
AuthorDate: Tue, 16 Jul 2019 17:20:45 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Jul 2019 15:37:04 +0200
sched/fair: Don't free
The perf.data-file-format documentation incorrectly says the
HEADER_TOTAL_MEM results are in bytes. The results are in kilobytes
(perf reads the value from /proc/meminfo)
Signed-off-by: Vince Weaver
diff --git a/tools/perf/Documentation/perf.data-file-format.txt
On Thu, Jul 25, 2019 at 10:56 AM Dafna Hirschfeld
wrote:
>
> From: Gary Bisson
>
> i.MX 8Quad is a quad (4x) Cortex-A53 processor with powerful
> graphic and multimedia features.
Instead of describing the SoC, it would be better to describe the
i.MX8M nitrogen board instead.
On Thu, 25 Jul 2019 10:27:33 +0200,
Jia-Ju Bai wrote:
>
> In build_adc_controls(), there is an if statement on line 773 to check
> whether ak->adc_info is NULL:
> if (! ak->adc_info ||
> ! ak->adc_info[mixer_ch].switch_name)
>
> When ak->adc_info is NULL, it is used on line
Hi Rafael,
On 25-07-19 12:07, Rafael J. Wysocki wrote:
Hi Hans,
This is similar to a problem I reported some time ago:
https://lore.kernel.org/lkml/2268131.Lc39eCoc3j@kreacher/
and the device affected by it is the same.
The symptom is simply that the mouse just doesn't work (no reaction).
On Thu, 25 Jul 2019 04:09:24 +0200,
Chuhong Yuan wrote:
>
> Instead of using kmalloc + memcpy, use kmemdup
> to simplify the code.
>
> Signed-off-by: Chuhong Yuan
Applied, thanks.
Takashi
On Thu, 2019-07-25 at 15:04 +, David Laight wrote:
> From: Qian Cai
> > Sent: 25 July 2019 15:39
> >
> > There are many of those warnings.
> >
> > In file included from ./arch/powerpc/include/asm/paca.h:15,
> > from ./arch/powerpc/include/asm/current.h:13,
> >
On Fri, Jul 26, 2019 at 12:27 AM Jan Kiszka wrote:
>
> On 25.07.19 17:18, Masahiro Yamada wrote:
> > Hi Jan,
> >
> > On Thu, Jul 25, 2019 at 5:39 PM Jan Kiszka wrote:
> >>>
> >>
> >> This affects also external modules builds: I have patterns here that do
> >>
> >> [Makefile]
> >> subdir-y :=
On 25/07/19 13:49, Vitaly Kuznetsov wrote:
> Few patches were recently marked for stable@ but commits are not
> backportable as-is and require a few tweaks. Here is 5.1 stable backport.
>
> [PATCH2 of the series applies as-is, I have it here for completeness]
>
> Jan Kiszka (1):
> KVM: nVMX:
On 25/07/19 14:04, Vitaly Kuznetsov wrote:
> Few patches were recently marked for stable@ but commits are not
> backportable as-is and require a few tweaks. Here is 5.2 stable backport.
>
> [PATCHes 2/3 of the series apply as-is, I have them here for completeness]
>
> Jan Kiszka (1):
> KVM:
If the particular version of clang a user has doesn't enable
-Werror=unknown-warning-option by default, even though it is the
default[1], then make sure to pass the option to the Kconfig cc-option
command so that testing options from Kconfig files works properly.
Otherwise, depending on the
On Fri, Jul 26, 2019 at 12:36 AM Philipp Zabel wrote:
>
> On Thu, 2019-07-25 at 11:17 -0300, Ezequiel Garcia wrote:
> > From: Francois Buergisser
> >
> > The Hantro codec is typically used in platforms with an IOMMU,
> > so we need to set a proper DMA segment size.
>
> ... to make sure the
Quoting Nathan Chancellor (2019-07-24 22:18:57)
> Hi Stephen,
>
> Was the second Kbuild in the subject line supposed to be Kconfig?
Sure. I'll change it to Kconfig.
>
> On Wed, Jul 24, 2019 at 04:50:30PM -0700, Stephen Boyd wrote:
> > If the particular version of clang a user has doesn't
Hi,
On Thu, Jul 25, 2019 at 8:18 AM Lina Iyer wrote:
>
> On Wed, Jul 24 2019 at 17:28 -0600, Doug Anderson wrote:
> >Hi,
> >
> >On Wed, Jul 24, 2019 at 1:36 PM Lina Iyer wrote:
> >>
> >> On Wed, Jul 24 2019 at 13:38 -0600, Stephen Boyd wrote:
> >> >Quoting Lina Iyer (2019-07-24 07:52:51)
> >>
On Thu, 2019-07-25 at 11:17 -0300, Ezequiel Garcia wrote:
> From: Francois Buergisser
>
> The Hantro codec is typically used in platforms with an IOMMU,
> so we need to set a proper DMA segment size.
... to make sure the DMA-mapping subsystem produces contiguous mappings?
> Devices without an
On 7/24/19 1:14 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.2.3 release.
There are 413 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 7/24/19 1:15 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.1.20 release.
There are 371 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 25.07.19 17:18, Masahiro Yamada wrote:
> Hi Jan,
>
> On Thu, Jul 25, 2019 at 5:39 PM Jan Kiszka wrote:
>>>
>>
>> This affects also external modules builds: I have patterns here that do
>>
>> [Makefile]
>> subdir-y := some-module
>>
>> [some-module/Makefile]
>> obj-m := some-module.o
>>
>> and
Add regulators coupler for Tegra30 SoCs that performs voltage balancing
of a coupled regulators and thus provides voltage scaling functionality.
There are 2 coupled regulators on all Tegra30 SoCs: CORE and CPU. The
coupled regulator voltages shall be in a range of 300mV from each other
and CORE
Hello,
The voltage regulators need to be coupled on NVIDIA Tegra20 and Tegra30
SoCs in order to provide voltage scaling functionality in a generic way.
All necessary regulator-core patches that added support for the regulators
coupling are already have been merge into mainline kernel. This series
There is voltage coupling between three regulators on Tegra20 boards and
between two on Tegra30. The voltage coupling is a SoC-level feature and
thus it is mandatory and common for all of the Tegra boards.
Signed-off-by: Dmitry Osipenko
---
.../nvidia,tegra-regulators-coupling.txt | 65
Add regulators coupler for Tegra20 SoCs that performs voltage balancing
of a coupled regulators and thus provides voltage scaling functionality.
There are 3 coupled regulators on all Tegra20 SoCs: CORE, RTC and CPU.
The CORE and RTC voltages shall be in range of 170mV from each other and
they
Hi,
I am having trouble keeping up.
Here is what I have so far:
On 2019.07.24 04:43 Viresh Kumar wrote:
> On 23-07-19, 12:27, Rafael J. Wysocki wrote:
>> On Tue, Jul 23, 2019 at 11:15 AM Viresh Kumar
>> wrote:
>>> Though there is one difference between intel_cpufreq and acpi_cpufreq,
>>>
Hi Jan,
On Thu, Jul 25, 2019 at 5:39 PM Jan Kiszka wrote:
> >
>
> This affects also external modules builds: I have patterns here that do
>
> [Makefile]
> subdir-y := some-module
>
> [some-module/Makefile]
> obj-m := some-module.o
>
> and since this patch, the final some-module.ko is no longer
On Wed, Jul 24 2019 at 17:28 -0600, Doug Anderson wrote:
Hi,
On Wed, Jul 24, 2019 at 1:36 PM Lina Iyer wrote:
On Wed, Jul 24 2019 at 13:38 -0600, Stephen Boyd wrote:
>Quoting Lina Iyer (2019-07-24 07:52:51)
>> On Tue, Jul 23 2019 at 14:11 -0600, Stephen Boyd wrote:
>> >Quoting Lina Iyer
On Thu, Jul 25, 2019 at 08:05:30AM -0700, Alexander Duyck wrote:
> On Thu, 2019-07-25 at 07:35 -0400, Nitesh Narayan Lal wrote:
> > On 7/24/19 6:03 PM, Alexander Duyck wrote:
> > > On Wed, 2019-07-24 at 17:38 -0400, Michael S. Tsirkin wrote:
> > > > On Wed, Jul 24, 2019 at 10:12:10AM -0700,
Hi,
On 25.07.2019 16:53, Chanwoo Choi wrote:
> 2019년 7월 25일 (목) 오후 11:19, Kamil Konieczny
> 님이 작성:
>>
>> Hi Chanwoo,
>>
>> On 25.07.2019 12:17, Chanwoo Choi wrote:
>>> Hi Kamil,
>>>
>>> Looks good to me. But, I have some comment. Please check them.
>>
>> Thank you for review, please see answers
From: Thor Thayer
In preparation for adding newer V2 parts that use a FIFO,
reorganize altera_cvp_chk_error() and change the write
function to block based.
V2 parts have a block size matching the FIFO while older
V1 parts write a 32 bit word at a time.
Signed-off-by: Thor Thayer
---
v2 Remove
From: Thor Thayer
Newer Intel FPGAs have different Vendor Specific offsets than
legacy parts. Use PCI discovery to find the CvP registers.
Since the register positions remain the same, change the hard
coded address to a more flexible way of indexing registers
from the offset.
Adding new PCI read
From: Thor Thayer
Add Stratix10 specific functions that use a credit mechanism
to throttle data to the CvP FIFOs. Add a private structure
with function pointers for V1 vs V2 functions.
Signed-off-by: Thor Thayer
---
v2 Remove inline function declaration
Reverse Christmas Tree format for
From: Thor Thayer
Newer versions (V2) of Altera/Intel FPGAs CvP have different PCI
Vendor Specific Capability offsets than the older (V1) Altera/FPGAs.
Most of the CvP registers and their bitfields remain the same
between both the older parts and the newer parts.
This patchset implements
Mark Rutland writes:
> On Thu, Jul 25, 2019 at 09:53:08AM +0200, Dmitry Vyukov wrote:
>> On Wed, Jul 24, 2019 at 1:21 PM Mark Rutland wrote:
>> >
>> > On Wed, Jul 24, 2019 at 11:11:49AM +0200, Dmitry Vyukov wrote:
>> > > On Tue, Jul 23, 2019 at 6:41 PM Mark Rutland
>> > > wrote:
>> > > >
>> >
From: Jon Hunter
Date: Jul/25/2019, 15:25:59 (UTC+00:00)
>
> On 25/07/2019 14:26, Jose Abreu wrote:
>
> ...
>
> > Well, I wasn't expecting that :/
> >
> > Per documentation of barriers I think we should set descriptor fields
> > and then barrier and finally ownership to HW so that remaining
25.07.2019 18:00, Piotr Sroka пишет:
> Add new Cadence NAND driver to MTD subsystem
>
> Signed-off-by: Piotr Sroka
> ---
> Changes for v5:
> - fix "ecc config strength" field size
> - remove unused macros
> - fix address of timing2 register
> - add guard for accessing data_control_size register
On 7/25/19 4:56 PM, Benjamin Gaignard wrote:
> Le jeu. 25 juil. 2019 à 13:40, Hans Verkuil a écrit :
>>
>> On 7/2/19 5:52 PM, Hugues Fruchet wrote:
>>> Add support of several sub-devices within pipeline instead
>>> of a single one.
>>> This allows to support a CSI-2 camera sensor connected
>>>
Hi,
This patch has the same problem as I mentioned on v3.
We need to discuss it on v3[1]. Please check my reply.
[1] [PATCH v3 3/5] devfreq: exynos-bus: convert to use dev_pm_opp_set_rate()
2019년 7월 25일 (목) 오후 11:46, 님이 작성:
>
> Reuse opp core code for setting bus clock and voltage. As a side
>
Hi,
On 25.07.2019 16:59, Chanwoo Choi wrote:
> Hi,
>
> You are missing my Acked tag.
I changed code, so I can not add your Ack in v4.
Please send new Ack for this patch.
> 2019년 7월 25일 (목) 오후 11:44, 님이 작성:
>>
>> Regulators should be enabled before clocks to avoid h/w hang. This
>> require
Jan Kiszka reported a module build regression; since commit ff9b45c55b26
("kbuild: modpost: read modules.order instead of $(MODVERDIR)/*.mod"),
a module is no longer built in the following pattern:
[Makefile]
subdir-y := some-module
[some-module/Makefile]
obj-m := some-module.o
You can
On Thu, 2019-07-25 at 07:35 -0400, Nitesh Narayan Lal wrote:
> On 7/24/19 6:03 PM, Alexander Duyck wrote:
> > On Wed, 2019-07-24 at 17:38 -0400, Michael S. Tsirkin wrote:
> > > On Wed, Jul 24, 2019 at 10:12:10AM -0700, Alexander Duyck wrote:
> > > > From: Alexander Duyck
> > > >
> > > > Add
501 - 600 of 1107 matches
Mail list logo