In commit 37a186225a0c ("platform/chrome: cros_ec_spi: Transfer
messages at high priority") we moved transfers to a high priority
workqueue. This helped make them much more reliable.
...but, we still saw failures.
We were actually finding ourselves competing for time with dm-crypt
which also
On Wed, May 8, 2019 at 2:13 PM Aaron Lewis wrote:
>
> From: Sean Christopherson
> Date: Wed, May 8, 2019 at 11:13 AM
> To: Aaron Lewis
> Cc: Paolo Bonzini, ,
> , Peter Shier
>
> > On Wed, May 08, 2019 at 10:53:12AM -0700, Aaron Lewis wrote:
> > > nested_run_pending is also checked in
> > >
On Wed, May 15, 2019 at 07:23:22PM +0530, Parth Shah wrote:
> This patch specifies the sched domain to search for a non idle core.
>
> The select_non_idle_core searches for the non idle cores across whole
> system. But in the systems with multiple NUMA domains, the Turbo frequency
> can be
On Tue, May 14, 2019 at 01:24:37PM -0700, Nick Desaulniers wrote:
> On Tue, May 14, 2019 at 11:11 AM Kees Cook wrote:
> >
> > On Mon, May 13, 2019 at 04:50:05PM -0700, Nick Desaulniers wrote:
> > > On Mon, May 13, 2019 at 4:29 PM Nathan Chancellor
> > > wrote:
> > > >
> > > > On Mon, May 13,
On Wed, May 15, 2019 at 07:23:21PM +0530, Parth Shah wrote:
> @@ -6704,6 +6773,31 @@ static int find_energy_efficient_cpu(struct
> task_struct *p, int prev_cpu)
> return -1;
> }
>
> +#ifdef CONFIG_SCHED_SMT
> +/*
> + * Select all tasks of type 1(jitter) for task packing
> + */
> +static
On Wed, May 15, 2019 at 09:26:38AM -0700, Guenter Roeck wrote:
> On Wed, May 15, 2019 at 12:54:40PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.120 release.
> > There are 115 patches in this series, all will be posted as a response
> > to this
On Wed, May 15, 2019 at 09:06:44PM +0800, Kai-Heng Feng wrote:
> at 20:33, Greg KH wrote:
>
> > On Wed, May 15, 2019 at 07:54:58PM +0800, Kai-Heng Feng wrote:
> > > at 19:40, Greg KH wrote:
> > >
> > > > On Wed, May 15, 2019 at 07:24:01PM +0800, Kai-Heng Feng wrote:
> > > > > The rtl8821ce can
* Peter Zijlstra wrote:
> On Mon, May 13, 2019 at 01:58:44PM -0400, Len Brown wrote:
> >
> > This patch series does 4 things.
> >
> > 1. Parse the new CPUID.1F leaf to discover multi-die/package topology
> >
> > 2. Export multi-die topology inside the kernel
> >
> > 3. Update 4 places
On Wed, May 15, 2019 at 07:23:20PM +0530, Parth Shah wrote:
> The task packing on a core needs to be bounded based on its capacity. This
> patch defines a new method which acts as a tipping point for task packing.
>
> The Core capacity is the method which limits task packing above certain
>
This patch adds board HiHope RZ/G2M (the main board, powered by
the R8A774A1) and board HiHope RZ/G2 EX (the expansion board
that sits on top of the HiHope RZ/G2M). Both boards are made
by Jiangsu HopeRun Software Co., Ltd. (a.k.a. HopeRun).
Useful links:
http://hihope.org/product/detail/rzg2
Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree
vendor prefixes as "hoperun".
Website: http://www.hoperun.com/en
Signed-off-by: Fabrizio Castro
Reviewed-by: Chris Paterson
---
v1->v2:
* No change
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed,
Dear All,
this series aims at documenting the HiHope RZ/G2M platform from
HopeRun, and its corresponding expansion board.
v1->v2:
* Applied Rob's comments
Thanks,
Fab
Fabrizio Castro (2):
dt-bindings: Add vendor prefix for HopeRun
dt-bindings: arm: renesas: Add HopeRun RZ/G2[M] boards
On Wed, May 15, 2019 at 07:23:18PM +0530, Parth Shah wrote:
> +void turbo_sched_get(void)
> +{
> + spin_lock(_sched_lock);
> + if (!turbo_sched_count++)
> + static_branch_enable(&__turbo_sched_enabled);
> + spin_unlock(_sched_lock);
> +}
Muwhahaha, you didn't test this
On Wed, May 15, 2019 at 07:23:19PM +0530, Parth Shah wrote:
> Use the get/put methods to add/remove the use of TurboSched support from
> the cgroup.
Didn't anybody tell you that cgroup only interfaces are frowned upon?
On Wed, May 15, 2019 at 05:59:38PM +0200, Jinpu Wang wrote:
> Hi Greg,
>
> This patch causes build failure for me:
>
> In file included from crypto/testmgr.c:54:
> crypto/testmgr.h:16081:4: error: 'const struct cipher_testvec' has no
> member named 'ptext'
>.ptext =
On Wed, May 15, 2019 at 07:23:17PM +0530, Parth Shah wrote:
> Subject: [RFCv2 1/6] sched/core: Add manual jitter classification from cgroup
> interface
How can this be v2 ?! I've never seen v1.
> Jitter tasks are usually of less important in terms of performance
> and are short/bursty in
No change, it's just duplicate, please ignore first patch and review
second patch.
Best regards
Rayagonda
On Thu, May 9, 2019 at 9:58 PM Ray Jui wrote:
>
> Why is the email sent twice? What has changed?
>
> On 5/8/2019 9:21 PM, Rayagonda Kokatanur wrote:
> > Add multiple byte read-write
When __afs_break_callback() clears the CB_PROMISED flag, it increments
vnode->cb_break to trigger a future refetch of the status and callback -
however it also calls afs_clear_permits(), which also increments
vnode->cb_break.
Fix this by removing the increment from afs_clear_permits().
Whilst
Make certain RPC operations non-interruptible, including:
(*) Set attributes
(*) Store data
We don't want to get interrupted during a flush on close, flush on
unlock, writeback or an inode update, leaving us in a state where we
still need to do the writeback or update.
(*)
On Wed, May 15, 2019 at 12:54:40PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.120 release.
> There are 115 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
__afs_break_callback() holds vnode->lock around its call of
afs_lock_may_be_available() - which also takes that lock.
Fix this by not taking the lock in __afs_break_callback().
Also, there's no point checking the granted_locks and pending_locks queues;
it's sufficient to check lock_state, so
Fix the calculation of the expiry time of a callback promise, as obtained
from operations like FS.FetchStatus and FS.FetchData.
The time should be based on the timestamp of the first DATA packet in the
reply and the calculation needs to turn the ktime_t timestamp into a
time64_t.
Fixes:
Add wait_var_event_interruptible() to allow interruptible waits for events.
Signed-off-by: David Howells
cc: Peter Zijlstra
---
include/linux/wait_bit.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/include/linux/wait_bit.h b/include/linux/wait_bit.h
index
Allow kernel services using AF_RXRPC to indicate that a call should be
non-interruptible. This allows kafs to make things like lock-extension and
writeback data storage calls non-interruptible.
If this is set, signals will be ignored for operations on that call where
possible - such as waiting
Don't invalidate the callback promise on a directory if the
AFS_VNODE_DIR_VALID flag is not set (which indicates that the directory
contents are invalid, due to edit failure, callback break, page reclaim).
The directory will be reloaded next time the directory is accessed, so
clearing the
Make dynamic root population wait uninterruptibly for proc_cells_lock.
Signed-off-by: David Howells
---
fs/afs/dynroot.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/afs/dynroot.c b/fs/afs/dynroot.c
index 07484b5a3bbb..af1689d1f32e 100644
--- a/fs/afs/dynroot.c
Currently, once configured, AFS cells are looked up in the DNS at regular
intervals - which is a waste of resources if those cells aren't being
used. It also leads to a problem where cells preloaded, but not
configured, before the network is brought up end up effectively statically
configured
callback break counter.
The patches can be found here:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git
tag afs-fixes-20190515
David
---
David Howells (15):
afs: Fix key leak in afs_release() and afs_evict_inode()
afs: Fix incorrect error handling
Fix incorrect error handling in afs_xattr_get_acl() where there appears to
be a redundant assignment before return, but in fact the return should be a
goto to the error handling at the end of the function.
Fixes: 260f082bae6d ("afs: Get an AFS3 ACL as an xattr")
Addresses-Coverity: ("Unused
Allow used DNS resolver keys to be invalidated after use if the caller is
doing its own caching of the results. This reduces the amount of resources
required.
Fix AFS to invalidate DNS results to kill off permanent failure records
that get lodged in the resolver keyring and prevent future
When afs_update_cell() replaces the cell->vl_servers list, it uses RCU
protocol so that proc is protected, but doesn't take ->vl_servers_lock to
protect afs_start_vl_iteration() (which does actually take a shared lock).
Fix this by making afs_update_cell() take an exclusive lock when replacing
Fix it such that afs_cell records always have a VL server list record
attached, even if it's a dummy one, so that various checks can be removed.
Signed-off-by: David Howells
---
fs/afs/cell.c | 19 +++
fs/afs/proc.c |8
fs/afs/vl_list.c | 20
Fix afs_release() to go through the cleanup part of the function if
FMODE_WRITE is set rather than exiting through vfs_fsync() (which skips the
cleanup). The cleanup involves discarding the refs on the key used for
file ops and the writeback key record.
Also fix afs_evict_inode() to clean up any
afs_xattr_get_yfs() tries to free yacl, which may hold an error value (say
if yfs_fs_fetch_opaque_acl() failed and returned an error).
Fix this by allocating yacl up front (since it's a fixed-length struct,
unlike afs_acl) and passing it in to the RPC function. This also allows
the flags to be
On Tue, May 14, 2019 at 05:36:47PM +0200, Sebastian Andrzej Siewior wrote:
> On 2019-05-14 07:13:50 [-0500], Corey Minyard wrote:
> > > Corey, would it make any change which waiter is going to be woken up?
> >
> > In the application that found this, the wake order probably isn't
> > relevant.
>
On Wed, May 15 2019 at 12:12pm -0400,
Helen Koike wrote:
> Hi,
>
> On 5/13/19 10:37 PM, Mike Snitzer wrote:
> > On Mon, May 13 2019 at 3:25P -0400,
> > Helen Koike wrote:
> >
> >> The dm_early_create() function (which deals with "dm-mod.create=" kernel
> >> command line option) calls
Hello Rob,
Thank you for your feedback!
> From: Rob Herring
> Sent: 15 May 2019 14:42
> Subject: Re: [PATCH 2/2] dt-bindings: arm: renesas: Add HopeRun RZ/G2[M]
> boards
>
> On Wed, May 15, 2019 at 6:45 AM Fabrizio Castro
> wrote:
> >
> > This patch adds board HiHope RZ/G2M (the main board,
On Wed, May 15, 2019 at 04:53:15PM +0900, Masahiro Yamada wrote:
> On Wed, May 15, 2019 at 4:40 PM Masahiro Yamada
> wrote:
> >
> > In the recent build test of linux-next, Stephen saw a build error
> > caused by a broken .tmp_versions/*.mod file:
> >
> > https://lkml.org/lkml/2019/5/13/991
> >
For *-pkg targets, the LICENSES directory should be included in the
source tarball.
Signed-off-by: Masahiro Yamada
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 9542165..e5414f7 100644
--- a/Makefile
+++ b/Makefile
@@ -1016,7 +1016,7
Hi Dmitry,
On Mon, May 13, 2019 at 4:29 PM Dmitry Torokhov
wrote:
>
> Hi Ravi,
>
> On Mon, May 13, 2019 at 3:06 PM Ravi Chandra Sadineni
> wrote:
> >
> > Notify the PM core that this dev is the wake source. This helps
> > userspace daemon tracking the wake source to identify the origin of the
>
From: Naveen Kumar Parna
checkpatch.pl does not like assignment in if condition
Signed-off-by: Naveen Kumar Parna
---
Changes in v3:
The first patch has an extra space in if statement, so fixed it in v2 but
forgot add what changed from the previous version. In v3 added the
complete change
In module_add_modinfo_attrs if sysfs_create_file
fails, we forget to free allocated modinfo_attrs
and roll back the sysfs files.
Fixes: 03e88ae1b13d ("[PATCH] fix module sysfs files reference counting")
Signed-off-by: YueHaibing
---
kernel/module.c | 16 +++-
1 file changed, 15
The pull request you sent on Wed, 15 May 2019 12:13:25 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-5.2-rc1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bfbfbf7368627860dd769567599d73ad8f6d8191
Thank you!
--
Deet-doot-dot, I am
The pull request you sent on Wed, 15 May 2019 12:14:39 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> acpi-5.2-rc1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fcdec14365ec96f490cf1c8d9b618643ec88a95e
Thank you!
--
Deet-doot-dot,
The pull request you sent on Thu, 16 May 2019 00:56:47 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kconfig-v5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2bbacd1a92788ee334c7e92b765ea16ebab68dfe
Thank you!
--
On Wed, May 15, 2019 at 01:19:04PM +0200, Roberto Sassu wrote:
> On 5/15/2019 2:52 AM, Arvind Sankar wrote:
> > You can specify multiple initrd's to the boot loader, and they get
> > loaded in sequence into memory and parsed by the kernel before /init is
> > launched. Currently I believe later
On Fri, Apr 26, 2019 at 07:22:11AM +0800, Yang Shi wrote:
> The commit 6b4c9f446981 ("filemap: drop the mmap_sem for all blocking
> operations") changed when mmap_sem is dropped during filemap page fault
> and when returning VM_FAULT_RETRY.
>
> Correct the comment to reflect the change.
>
> Cc:
Hi Greg,
This patch causes build failure for me:
In file included from crypto/testmgr.c:54:
crypto/testmgr.h:16081:4: error: 'const struct cipher_testvec' has no
member named 'ptext'
.ptext = "\x6b\xc1\xbe\xe2\x2e\x40\x9f\x96"
^
crypto/testmgr.h:16089:4: error: 'const struct
On 5/15/19 8:06 AM, Kai-Heng Feng wrote:
at 20:33, Greg KH wrote:
On Wed, May 15, 2019 at 07:54:58PM +0800, Kai-Heng Feng wrote:
at 19:40, Greg KH wrote:
On Wed, May 15, 2019 at 07:24:01PM +0800, Kai-Heng Feng wrote:
The rtl8821ce can be found on many HP and Lenovo laptops.
Users have
Hi Linus,
Please pull Kconfig updates for v5.2
Thanks.
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
On 15.05.2019 15:59, Arnaldo Carvalho de Melo wrote:
> Em Wed, May 15, 2019 at 11:43:30AM +0300, Alexey Budankov escreveu:
>> On 15.05.2019 0:46, Arnaldo Carvalho de Melo wrote:
>>> Em Tue, May 14, 2019 at 05:20:41PM -0300, Arnaldo Carvalho de Melo escreveu:
Em Mon, Mar 18, 2019 at 08:44:42PM
Hi Vincent,
> On May 15, 2019, at 3:18 AM, Vincent Guittot
> wrote:
>
> Hi Song,
>
> On Tue, 14 May 2019 at 22:58, Song Liu wrote:
>>
>> Hi Vincent,
>>
>
> [snip]
>
>>>
>>> Here are some more results with both Viresh's patch and the cpu.headroom
>>> set. In these tests, the side job
On Wed, May 15, 2019 at 08:20:35AM -0700, Matthew Wilcox wrote:
> On Wed, May 15, 2019 at 05:04:06PM +0200, Greg Kroah-Hartman wrote:
> > > Greg, can you consider 6daef95b8c914866a46247232a048447fff97279 for
> > > backporting to stable? Nobody realised it was a bugfix at the time it
> > > went
This value matches what is used by the downstream Chrome OS 3.14
kernel, the 'official' kernel for veyron devices.
Signed-off-by: Matthias Kaehlcke
---
arch/arm/boot/dts/rk3288-veyron.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi
Raise the temperature of the GPU thermal trip point for speedy
to 80°C. This is the value used by the downstream Chrome OS 3.14
kernel, the 'official' kernel for speedy.
Signed-off-by: Matthias Kaehlcke
---
arch/arm/boot/dts/rk3288-veyron-speedy.dts | 4
1 file changed, 4 insertions(+)
Hi Marc,
Our situation is for guest system crash and kdump feature. The detailed steps
are as below:
1. Guest system crash.
2. One of VCPU is chosen as primary VCPU.
3. The primary VCPU sends IPIs to other VCPUs (by crash_smp_send_stop), to
request them to offline.
4. The other VCPUs
Hello, Andrew.
> An earlier version of this patch was accused of crashing the kernel:
>
> https://lists.01.org/pipermail/lkp/2019-April/010004.html
>
> does the v4 series address this?
I tried before to narrow down that crash but i did not succeed, so
i have never seen that before on my test
On Wed, May 15, 2019 at 05:04:06PM +0200, Greg Kroah-Hartman wrote:
> > Greg, can you consider 6daef95b8c914866a46247232a048447fff97279 for
> > backporting to stable? Nobody realised it was a bugfix at the time it
> > went in. I suspect there aren't too many of us running HIGHMEM kernels
> > any
On Tue, May 14, 2019 at 03:40:47PM -0700, Nathan Chancellor wrote:
> Currently, this Makefile hardcodes GNU ar, meaning that if it is not
> available, there is no way to supply a different one and the build will
> fail.
>
> $ make AR=llvm-ar CC=clang LD=ld.lld HOSTAR=llvm-ar HOSTCC=clang \
>
On Wed, May 15, 2019 at 08:02:17AM -0700, Eric Dumazet wrote:
> On Wed, May 15, 2019 at 7:43 AM Matthew Wilcox wrote:
> > You're seeing a race between page_address(page) being called twice.
> > Between those two calls, something has caused the page to be removed from
> > the page_address_map()
On Wed, May 15, 2019 at 04:51:51PM +0200, Michal Hocko wrote:
> [Cc Suren and Minchan - the email thread starts here
> 20190514131654.25463-1-oleksa...@redhat.com]
>
> On Wed 15-05-19 08:53:11, Michal Hocko wrote:
> [...]
> > I will try to comment on the interface itself later. But I have to say
On Wed, May 15, 2019 at 07:13:10PM +0530, parna.naveenku...@gmail.com wrote:
> From: Naveen Kumar Parna
>
> Fixed the checkpatch error. Used "foo *bar" instead of "foo * bar"
>
> Signed-off-by: Naveen Kumar Parna
> ---
> drivers/char/bsr.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On Wed, May 15, 2019 at 08:39:52PM +0530, parna.naveenku...@gmail.com wrote:
> From: Naveen Kumar Parna
>
> checkpatch.pl does not like assignment in if condition
>
> Signed-off-by: Naveen Kumar Parna
> ---
> drivers/char/bsr.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
If you
On Wed, May 15, 2019 at 07:47:31PM +0530, parna.naveenku...@gmail.com wrote:
> From: Naveen Kumar Parna
>
> According to checkpatch: EXPORT_SYMBOL(foo); should immediately follow its
> function/variable.
>
> This patch fixes the following checkpatch.pl issues in drivers/char/misc.c:
> WARNING:
Le 15/05/2019 à 16:16, Greg KH a écrit :
On Wed, May 15, 2019 at 01:30:42PM +, Christophe Leroy wrote:
[Backport of upstream commit b45ba4a51cde29b2939365ef0c07ad34c8321789]
On powerpc32, patch_instruction() is called by apply_feature_fixups()
which is called from early_init()
There is
On Wed, May 15, 2019 at 07:47:45AM -0700, kernelci.org bot wrote:
> stable-rc/linux-4.4.y boot: 98 boots: 1 failed, 92 passed with 3 offline, 1
> untried/unknown, 1 conflict (v4.4.179-267-gbe756dada5b7)
>
> Full Boot Summary:
>
This allows to copy pages not only to the same addreses
in another process, but also to a specified address.
Huge pages and unaligned address cases are handled
by splitting.
Signed-off-by: Kirill Tkhai
---
include/linux/huge_mm.h |6 +-
include/linux/mm.h |3 +
kernel/fork.c
Signed-off-by: Kirill Tkhai
---
include/linux/mman.h | 14 ++
mm/mmap.c| 13 -
2 files changed, 14 insertions(+), 13 deletions(-)
diff --git a/include/linux/mman.h b/include/linux/mman.h
index 4b08e9c9c538..69feb3144c12 100644
--- a/include/linux/mman.h
This adds a new syscall to map from or to another
process vma. Flag PVMMAP_FIXED may be specified,
its meaning is similar to mmap()'s MAP_FIXED.
@pid > 0 means to map from process of @pid to current,
@pid < 0 means to map from current to @pid process.
VMA are merged on destination, i.e. if
Similar to process_vm_readv() and process_vm_writev(),
add declarations of a new syscall, which will allow
to map memory from or to another process.
Signed-off-by: Kirill Tkhai
---
arch/x86/entry/syscalls/syscall_32.tbl |1 +
arch/x86/entry/syscalls/syscall_64.tbl |2 ++
This prepares the function to copy a vma between
two processes. Two new arguments are introduced.
Signed-off-by: Kirill Tkhai
---
include/linux/mm.h |4 ++--
mm/mmap.c | 33 -
mm/mremap.c|4 ++--
3 files changed, 28 insertions(+), 13
This patchset adds a new syscall, which makes possible
to clone a mapping from a process to another process.
The syscall supplements the functionality provided
by process_vm_writev() and process_vm_readv() syscalls,
and it may be useful in many situation.
For example, it allows to make a zero
From: Naveen Kumar Parna
checkpatch.pl does not like assignment in if condition
Signed-off-by: Naveen Kumar Parna
---
drivers/char/bsr.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/char/bsr.c b/drivers/char/bsr.c
index d16ba62d03a0..935d4b300340 100644
---
During probe, return the "get_irq" error value instead of -EINVAL which
allows the driver to be deferred probed if needed.
Fix also the case where of_irq_get() returns a negative value.
Note :
On failure of_irq_get() returns 0 or a negative value while
platform_get_irq() returns a negative value.
stable-rc/linux-4.19.y boot: 131 boots: 0 failed, 129 passed with 1 offline, 1
conflict (v4.19.43-114-gb5001f5eab58)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.43-114-gb5001f5eab58/
Full Build Summary:
stable-rc/linux-3.18.y boot: 59 boots: 5 failed, 51 passed with 2 offline, 1
conflict (v3.18.139-87-g06310902672a)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.139-87-g06310902672a/
Full Build Summary:
Masahiro Yamada (2):
memory: move jedec_ddr_data.c from lib/ to drivers/memory/
memory: move jedec_ddr.h from include/memory to drivers/memory/
drivers/memory/Kconfig | 8
drivers/memory/Makefile | 1 +
drivers/memory/emif.c
Now that jedec_ddr_data.c was moved from lib/ to drivers/memory/,
is included only from drivers/memory/.
Make it a local header of drivers/memory/.
While I am here, I also changed #include to
. Because CONFIG_DDR is bool, jedec_ddr_data.c is
never compiled as a module.
Signed-off-by: Masahiro
jedec_ddr_data.c exports the lpddr2_jedec_* symbols, and all of them
are only referenced from drivers/memory/{emif.c,of_memory.c}
drivers/memory/ is a better location than lib/.
I removed the Kconfig prompt "JEDEC DDR data" because it is only
select'ed by TI_EMIF, and there is no other user.
On Wed, May 15, 2019 at 07:43:52AM -0700, Matthew Wilcox wrote:
> > > W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> > >> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> > >> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> > >> noticing
On Wed, May 15, 2019 at 7:43 AM Matthew Wilcox wrote:
>
> > > W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> > >> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> > >> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> > >> noticing strange
On 05/13, Sultan Alsawaf wrote:
>
> On Fri, May 10, 2019 at 05:10:25PM +0200, Oleg Nesterov wrote:
> > I am starting to think I am ;)
> >
> > If you have task1 != task2 this code
> >
> > task_lock(task1);
> > task_lock(task2);
> >
> > should trigger print_deadlock_bug(), task1->alloc_lock
On Wed, May 15, 2019 at 02:44:33PM +0300, Dmitry Osipenko wrote:
> 15.05.2019 12:05, Mark Brown пишет:
> > On Tue, May 14, 2019 at 09:30:05PM +0300, Dmitry Osipenko wrote:
> >> I'm afraid this is just a way of abusing the OPP's. I actually already
> > There's nothing wrong with handling
Friendly ping...
在 2019/4/24 12:04, Zhiqiang Liu 写道:
>
> Friendly ping...
>
>> From: Zhiqiang Liu
>>
>> In proc_dointvec_jiffies func, the write value is only checked
>> whether it is larger than INT_MAX. If the write value is less
>> than zero, it can also be successfully writen in the data.
[Cc Suren and Minchan - the email thread starts here
20190514131654.25463-1-oleksa...@redhat.com]
On Wed 15-05-19 08:53:11, Michal Hocko wrote:
[...]
> I will try to comment on the interface itself later. But I have to say
> that I am not impressed. Abusing sysfs for per process features is
stable-rc/linux-4.4.y boot: 98 boots: 1 failed, 92 passed with 3 offline, 1
untried/unknown, 1 conflict (v4.4.179-267-gbe756dada5b7)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.179-267-gbe756dada5b7/
Full Build Summary:
On Fri 2019-04-26 14:44:45, Sergey Senozhatsky wrote:
>
> Forgot to mention that the series is still in RFC phase.
>
>
> On (04/26/19 14:33), Sergey Senozhatsky wrote:
> [..]
> > +++ b/kernel/printk/printk.c
> > @@ -2613,6 +2613,12 @@ static int __unregister_console(struct console
> >
> > W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> >> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> >> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> >> noticing strange warnings coming from 'read' syscall, when
> >> page_copy_sane()
On 05/14, Roman Gushchin wrote:
>
> I agree that "may_remain_frozen" adds a lot of ugliness, so let's fix
> the regression with the unconditional leave_frozen(true). The patch below.
> Please, let me know if it's not what you meant.
Yes, thanks, this is what I meant. Feel free to add my ACK.
>
This patch series introduces the SAI nodes on i.MX8MM EVK then
creates the wm8524 codec node and finally uses simple card machine
driver to create a sound card.
Changes since v2:
- place compatible strings one a single lines
- move GPIO pinctrl in a node of its own
- remove
i.MX8MM has one wm8524 audio codec connected with
SAI3 digital audio interface.
This patch uses simple-card machine driver in order
to enable wm8524 codec.
We need to set:
* SAI3 pinctrl configuration
* codec reset gpio pinctrl configuration
* clock hierarchy
*
i.MX8MM has 5 SAI instances with the following base
addresses according to RM.
SAI1 base address: 3001_h
SAI2 base address: 3002_h
SAI3 base address: 3003_h
SAI5 base address: 3005_h
SAI6 base address: 3006_h
Signed-off-by: Daniel Baluta
---
From: Alexander Potapenko
Date: Wed, Jan 2, 2019 at 11:09 AM
To: Jens Axboe
Cc: Andrew Morton, ,
, Andi Kleen, ,
, LKML, Linux Memory Management List,
, ,
> On Wed, Dec 19, 2018 at 2:23 PM Jens Axboe wrote:
> >
> > On 12/19/18 3:23 AM, Alexander Potapenko wrote:
> > > On Thu, Sep 13, 2018 at
If bus_register fails. On its error handling path, it has cleaned up
what it has done. There is no need to call bus_unregister again.
Otherwise, if bus_unregister is called, issues such as null-ptr-deref
will arise.
Syzkaller report this:
kobject_add_internal failed for memstick (error: -12
On Fri 2019-04-26 14:33:01, Sergey Senozhatsky wrote:
> We need to take console_sem lock when we iterate console drivers
> list. Otherwise, another CPU can concurrently modify console drivers
> list or console drivers. Current register_console() has several
> race conditions - for_each_console()
On 2019/05/14 18:19, Sergey Senozhatsky wrote:
> On (05/11/19 00:19), Tetsuo Handa wrote:
>> We are seeing syzbot reports [1] where printk() messages prior to panic()
>> are missing for unknown reason. To test whether it is due to some testcase
>> changing console loglevel, let's panic() as soon
> @@ -4348,7 +4348,9 @@ int __access_remote_vm(struct task_struct *tsk, struct
> mm_struct *mm,
> void *old_buf = buf;
> int write = gup_flags & FOLL_WRITE;
>
> - down_read(>mmap_sem);
> + if (down_read_killable(>mmap_sem))
> + return 0;
> +
I too think that
> On May 15, 2019, at 4:00 AM, Jarkko Sakkinen
> wrote:
>
>> On Wed, May 15, 2019 at 01:35:31PM +0300, Jarkko Sakkinen wrote:
>> This brings me to an open question in Andy's model: lets say that we
>> change the source for SIGSTRUCT from memory address to fd. How can the
>> policy prevent the
On Wed 15-05-19 10:51:58, Oleksandr Natalenko wrote:
> On Wed, May 15, 2019 at 10:33:21AM +0200, Michal Hocko wrote:
> > > For my current setup with 2 Firefox instances I get 100 to 200 MiB saved
> > > for the second instance depending on the amount of tabs.
> >
> > What does prevent Firefox (an
From: Roman Stratiienko
Alarmtimer interface uses only the RTC with wekeup flags enabled.
Allow to use rtc-test driver with alarmtimer interface.
Signed-off-by: Roman Stratiienko
---
Changes in v2:
Wakeup flags applied only for the RTCs with alarm support
drivers/rtc/rtc-test.c | 1 +
1
301 - 400 of 1557 matches
Mail list logo
