Adding a -i flag which will use the kernels's idle
page tracking to mark pages idle. As the tool already
prints the idle flag if set, subsequent runs will show
which pages have been accessed since last run.
Signed-off-by: Christian Hansen
---
tools/vm/page-types.c | 47 +
Hi Sricharan,
On 06/01/2018 11:46 AM, Sricharan R wrote:
Hi Bjorn,
Thanks for this much needed consolidation.
On 5/23/2018 10:50 AM, Bjorn Andersson wrote:
Shared between all Hexagon V5 based remoteprocs is the handling of the 5
interrupts and the SMP2P stop request, so break this out into
On 6/1/18 8:17 AM, Guenter Roeck wrote:
On 06/01/2018 03:25 AM, Mark Brown wrote:
On Thu, May 24, 2018 at 12:49:21PM -0700, Guenter Roeck wrote:
From: Guenter Roeck
Commit dc31e741db49 ("ASoC: topology: ABI - Add the types for BE
DAI") introduced sound topology files version 5. Initially, thi
The RISC-V implementation seems to be quite clean regarding
sparse annotations. There is anyway three small glitches
which are corrected by this series.
Note: the 3rd patch may need another solution.
Luc Van Oostenryck (3):
riscv: use NULL instead of a plain 0
riscv: no __user for probe_kerne
In is_valid_bugaddr(), probe_kernel_address() is called with
the PC casted to (bug_inst_t __user *) but this function
only take a plain void* as argument, not a __user pointer.
Fix this by removing the unnneded __user in the cast.
Signed-off-by: Luc Van Oostenryck
---
arch/riscv/kernel/traps.c
sbi_remote_sfence_vma() & sbi_remote_fence_i() takes
a pointer as first argument but some macros call them with
a plain 0 which, while legal C, is frowned upon in the kernel.
Change this by replacing the 0 by NULL.
Signed-off-by: Luc Van Oostenryck
---
arch/riscv/include/asm/cacheflush.h | 2 +-
__copy_user() is a function, written in assembly, used to copy
memory between kernel & user space. As such its to & from args
may both take a user pointer or a kernel pointer.
However the prototype for this function declare these two args
as 'void __user *', which is no more & no less correct than
On Fri, Jun 01, 2018 at 10:19:57AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 01, 2018 at 11:56:48AM +0200, Jiri Olsa escreveu:
> > The compilation is broken if there's no slang support:
> >
> > builtin-annotate.c: In function ‘hists__find_annotations’:
> > builtin-annotate.c:344:10:
On Fri, Jun 01 2018 at 10:09am -0400,
Martin K. Petersen wrote:
>
> Good morning Mike,
>
> > This notion that only native NVMe multipath can be successful is utter
> > bullshit. And the mere fact that I've gotten such a reaction from a
> > select few speaks to some serious control issues.
>
>
Michal Hocko writes:
> On Fri 01-06-18 09:32:42, Eric W. Biederman wrote:
>> Michal Hocko writes:
> [...]
>> > Group leader exiting early without tearing down the whole thread
>> > group should be quite rare as well. No question that somebody might do
>> > that on purpose though...
>>
>> The gr
On Tue, May 29, 2018 at 03:21:48PM +0200, Miklos Szeredi wrote:
> Hi Al,
>
> I'm sending this pull request to you instead of Linus, because a bigger than
> usual chunk involves the VFS.
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git for-viro
>
> This
Hi,
On Fri, 01 Jun 2018 07:38:42 -0700 dvh...@infradead.org wrote:
>
> Stephen, are the tests you use available publicly?
I use the script below when I am fetching trees. You don't want the
"gitk" invocation if you are doing this automatically, of course. The
script just takes a commit range.
On 06/01/2018 10:12 AM, Andy Shevchenko wrote:
> On Fri, Jun 1, 2018 at 6:01 PM, Alexandru Gagniuc
> wrote:
>> PCIe downtraining happens when both the device and PCIe port are
>> capable of a larger bus width or higher speed than negotiated.
>> Downtraining might be indicative of other problems i
Hi,
On Fri 01-06-18 11:56:19, Stephen Rothwell wrote:
> Today's linux-next merge of the vfs tree got a conflict in:
>
> include/linux/fs.h
>
> between commit:
>
> 29aca8b3f7cd ("fsnotify: introduce prototype struct fsnotify_obj")
>
> from the ext3 tree and commit:
>
> d9a08a9e616b ("fs:
On Wednesday, May 30, 2018 9:29:24 AM CEST Linus Walleij wrote:
> On Wed, May 30, 2018 at 7:07 AM, Stephen Rothwell
wrote:
> > Hi all,
> >
> > Today's linux-next merge of the regulator tree got a conflict in:
> > arch/arm/mach-omap1/board-ams-delta.c
> >
> > between commit:
> > 0486738928bf
Thomas,
This is the (quite small, for once) set of irqchip updates for
4.18. On the menu, bunch of cleanups and new feature for the stm32
irqchip, and sSupport for the Meson-AXG GPIO irqchip.
Please pull,
M.
The following changes since commit 48bda43eabb8d086204f543cf8bbad696b8c6391:
On 06/01/2018 10:10 AM, Sinan Kaya wrote:
> On 6/1/2018 11:06 AM, Alex G. wrote:
>> On 06/01/2018 10:03 AM, Sinan Kaya wrote:
>>> On 6/1/2018 11:01 AM, Alexandru Gagniuc wrote:
+ /* Multi-function PCIe share the same link/status. */
+ if (PCI_FUNC(dev->devfn) != 0)
+ re
move feature-fixups related stuff from synch.h to synch-ftr.h
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/atomic.h | 1 +
arch/powerpc/include/asm/barrier.h| 1 +
arch/powerpc/include/asm/bitops.h | 1 +
arch/powerpc/include/asm
On Fri, Jun 01, 2018 at 04:10:56PM +0900, Byungchul Park wrote:
> > On Thu, May 31, 2018 at 11:12:55PM -0700, Joel Fernandes wrote:
> > > On Mon, Jan 08, 2018 at 03:14:41PM +0900, byungchul park wrote:
> > > > Currently, migrating tasks to cpu0 unconditionally happens when the
> > > > heap is empty
On Fri, Jun 01, 2018 at 10:19:58AM -0500, Pierre-Louis Bossart wrote:
> On 6/1/18 8:17 AM, Guenter Roeck wrote:
> >On 06/01/2018 03:25 AM, Mark Brown wrote:
> >>On Thu, May 24, 2018 at 12:49:21PM -0700, Guenter Roeck wrote:
> >>>From: Guenter Roeck
> >>>
> >>>Commit dc31e741db49 ("ASoC: topology:
On Fri, 2018-05-25 at 02:11:44 UTC, Thiago Jung Bauermann wrote:
> This test exercises read and write access to the AMR, IAMR and UAMOR.
>
> Signed-off-by: Thiago Jung Bauermann
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1f7256e7dddef49acf9f6c9fe3f935
cheers
On 06/01, Christian Brauner wrote:
>
> may_ptrace_stop() already behaves like a boolean function. Let's actually
> declare it as such too.
OK. Then probably this patch should only make it return bool and do nothing
else?
> - if (unlikely(current->mm->core_state) &&
> - unlikely(curre
On 5/31/2018 11:58 PM, Konstantin Khlebnikov wrote:
On Thu, May 31, 2018 at 9:05 PM, Eric W. Biederman
wrote:
Nagarathnam Muthusamy writes:
Ping? Any additional comments on this patch?
Konstantin's v5 no.
I am uncomfortable with unnecessary flexibility. I don't want to
encourage
On Fri, Jun 01, 2018 at 05:56:12PM +0200, Oleg Nesterov wrote:
> On 06/01, Christian Brauner wrote:
> >
> > may_ptrace_stop() already behaves like a boolean function. Let's actually
> > declare it as such too.
>
> OK. Then probably this patch should only make it return bool and do nothing
> else?
Hi,
can someone tell me what this exactly means?
What is the root cause for this?
GNU binutils/ld?
Compiler?
Curently I test with clang-7.
VirtualBox and compiler incompatible?
Steps to reproduce the failure...
root# modprobe -v vboxdrv
insmod /lib/modules/4.14.47-1-iniza-llvmlinux/updates/dkms
Changes from v1
lkml.kernel.org/r/20180524211135.27760-1-d...@stgolabs.net
- patch 2 is reworked a bit based on the commments from Herbert Xu.
o upon failure, retry immediately with GFP_NOFAIL (simpler)
o the caller now passes the needed semantics, not bucket_table_alloc().
o we consider min
Now that we know that rhashtable_init() will not fail, we
can get rid of a lot of the unnecessary cleanup paths when
the call errored out.
Signed-off-by: Davidlohr Bueso
---
ipc/msg.c | 9 -
ipc/namespace.c | 20
ipc/sem.c | 10 --
ipc/shm.c
In sysvipc we have an ids->tables_initialized regarding the
rhashtable, introduced in:
0cfb6aee70b (ipc: optimize semget/shmget/msgget for lots of keys).
It's there, specifically, to prevent nil pointer dereferences,
from using an uninitialized api. Considering how rhashtable_init()
can fail
Update the test module as such.
Signed-off-by: Davidlohr Bueso
---
lib/test_rhashtable.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/lib/test_rhashtable.c b/lib/test_rhashtable.c
index f4000c137dbe..a894eb0407f0 100644
--- a/lib/test_rhashtable.c
+++ b/lib/test_rhash
For the purpose of making rhashtable_init() unable to fail,
we can replace the returning -EINVAL with WARN_ONs whenever
the caller passes bogus parameters during initialization.
Signed-off-by: Davidlohr Bueso
---
lib/rhashtable.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
di
rhashtable_init() may fail due to -ENOMEM, thus making the
entire api unusable. This patch removes this scenario,
however unlikely. In order to guarantee memory allocation,
this patch always ends up doing GFP_KERNEL|__GFP_NOFAIL
for both the tbl as well as alloc_bucket_spinlocks().
Upon the first
Em Fri, Jun 01, 2018 at 05:21:55PM +0200, Jiri Olsa escreveu:
> On Fri, Jun 01, 2018 at 10:19:57AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Jun 01, 2018 at 11:56:48AM +0200, Jiri Olsa escreveu:
> > > Adding the missing argument to hist_entry__tui_annotate function.
> > Thanks, I think I
On 06/01, Christian Brauner wrote:
>
> The goto is not needed and does not add any clarity. Simply return -EINVAL
> on unexpected sigset_t struct size directly.
Agreed, sys_rt_sigaction() looks just ugly and mixes goto/return on failure,
ACK
linux/kernel.h isn't needed by asm/atomic.h and will result in circular
dependencies when the asm-generic atomic bitops are built around the
tomic_long_t interface.
Remove the broad include and replace it with linux/compiler.h for
READ_ONCE etc and asm/irqflags.h for arch_local_irq_save etc.
Cc:
asm-generic/bitops/lock.h is shortly going to be built on top of the
atomic_long_* API, which introduces a nasty circular dependency for
m68k where linux/atomic.h pulls in linux/bitops.h via:
linux/atomic.h
asm/atomic.h
linux/irqflags.h
asm/irqflags.h
linux/
The asm-generic/bitops/{atomic,lock}.h implementations are built around
the atomic-fetch ops, which we implement efficiently for both LSE and
LL/SC systems. Use that instead of our hand-rolled, out-of-line bitops.S.
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/bitops.h | 14 ++--
ar
asm-generic/bitops/ext2-atomic-setbit.h provides the ext2 atomic bitop
definitions, so we don't need to define our own.
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/bitops.h | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/arm64/include/asm/bitops.h b/arch/
The sh implementation of asm/cmpxchg-xchg.h pulls in linux/bitops.h
so that it can refer to BITS_PER_BYTE. It also transitively relies on
this pulling in linux/compiler.h for READ_ONCE.
Replace the #include with linux/bits.h and linux/compiler.h
Signed-off-by: Will Deacon
---
arch/sh/include/as
Hi all,
This patch series has previously been posted in RFC form here:
RFCv1: https://www.spinics.net/lists/arm-kernel/msg634719.html
RFCv2: https://www.spinics.net/lists/arm-kernel/msg636875.html
v1: https://www.spinics.net/lists/arm-kernel/msg655262.html
The only change since v1 is th
The openrisc implementation of asm/cmpxchg.h pulls in linux/bitops.h
so that it can refer to BITS_PER_BYTE. It also transitively relies on
this pulling in linux/compiler.h for READ_ONCE.
Replace the #include with linux/bits.h and linux/compiler.h
Signed-off-by: Will Deacon
---
arch/openrisc/inc
In preparation for implementing the asm-generic atomic bitops in terms
of atomic_long_*, we need to prevent asm/atomic.h implementations from
pulling in linux/bitops.h. A common reason for this include is for the
BITS_PER_BYTE definition, so move this and some other BIT and masking
macros into a ne
The atomic bitops can actually be implemented pretty efficiently using
the atomic_* ops, rather than explicit use of spinlocks.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Signed-off-by: Will Deacon
---
include/asm-generic/bitops/atomic.h | 188 +++-
1 file changed, 33 i
The lock bitops can be implemented more efficiently using the atomic_fetch_*
ops, which provide finer-grained control over the memory ordering semantics
than the bitops.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Signed-off-by: Will Deacon
---
include/asm-generic/bitops/lock.h | 68 +++
On Fri, Jun 01, 2018 at 09:01:21AM -0700, Davidlohr Bueso wrote:
> For the purpose of making rhashtable_init() unable to fail,
> we can replace the returning -EINVAL with WARN_ONs whenever
> the caller passes bogus parameters during initialization.
>
> Signed-off-by: Davidlohr Bueso
> ---
> lib/
On Fri, Jun 01, 2018 at 08:50:37AM -0400, Hugo Lefeuvre wrote:
> Add a rw semaphore fixing potential NULL pointer dereferences in the
> pi433 driver.
Unless you can measure the performance difference, do not use a rw
semaphore, just use a normal mutex please. Odds are it will be faster
in the end
Hi Peter and Petr,
Thanks for your suggestions, will try to find a cleaner and less hacky way,
and it may take some time as dealing with all kinds of TSC is tricky :)
- Feng
On Thu, May 31, 2018 at 05:52:10PM +0200, Peter Zijlstra wrote:
> On Thu, May 31, 2018 at 03:55:42PM +0200, Petr Mladek wr
On 5/31/2018 8:32 PM, Brian Norris wrote:
> This compatible property was documented before the driver was renamed to
> "SBS" (see commit e57f1b68c406 ("devicetree-bindings: Propagate
> bq20z75->sbs rename to dt bindings")). The driver has continued to
> support this property as an alternative to "s
On Fri, Jun 01, 2018 at 02:16:00PM +0100, Suzuki K Poulose wrote:
> Before we updat the bindings, document the current graph bindings
s/updat/update
> and usage of additional properties.
>
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
> ---
> .../devicetree/bindings/arm/coresight.tx
NAGARATHNAM MUTHUSAMY writes:
> On 5/31/2018 11:58 PM, Konstantin Khlebnikov wrote:
>> On Thu, May 31, 2018 at 9:05 PM, Eric W. Biederman
>> wrote:
>>> Nagarathnam Muthusamy writes:
>>>
Ping? Any additional comments on this patch?
>>> Konstantin's v5 no.
>>>
>>>I am uncomfortable with
On 01.06.2018 18:55, NAGARATHNAM MUTHUSAMY wrote:
On 5/31/2018 11:58 PM, Konstantin Khlebnikov wrote:
On Thu, May 31, 2018 at 9:05 PM, Eric W. Biederman
wrote:
Nagarathnam Muthusamy writes:
Ping? Any additional comments on this patch?
Konstantin's v5 no.
I am uncomfortable with unnec
On Thu, 2018-05-31 at 07:29 -0400, Jeff Layton wrote:
> From: Jeff Layton
>
> v2: don't modify sync_fs op prototype, handle errors at vfs layer
>
> The syncfs system call returns an int error code, but in general it does
> not return errors when an inode fails writeback. It will return an error
On 06/01, Christian Brauner wrote:
>
> has_pending_signals() already behaves like a boolean function. Let's
> actually declare it as such too.
But this patch does more.
> - case 4: ready = signal->sig[3] &~ blocked->sig[3];
> - ready |= signal->sig[2] &~ blocked->sig[2];
> -
On 06/01/2018 08:26 AM, Miklos Szeredi wrote:
> On Tue, May 29, 2018 at 03:21:48PM +0200, Miklos Szeredi wrote:
>> Hi Al,
>>
>> I'm sending this pull request to you instead of Linus, because a bigger than
>> usual chunk involves the VFS.
>>
>> Please pull from:
>>
>> git://git.kernel.org/pub/scm/
On 6/1/2018 1:56 AM, CHANDAN VN wrote:
> Hi
>
>
>> On 5/31/2018 9:11 AM, Tejun Heo wrote:
>> On Thu, May 31, 2018 at 09:04:25AM -0700, Casey Schaufler wrote:
On 5/31/2018 8:39 AM, Tejun Heo wrote:
> (cc'ing more security folks and copying whole body)
>
> So, I'm sure the patc
On Thu, May 31, 2018 at 10:46:07AM +0200, Juri Lelli wrote:
> On 30/05/18 17:46, Quentin Perret wrote:
> > So I understand why we want to got to max freq when a RT task is running,
> > but I think there are use cases where we might want to be more conservative
> > and use the util_avg of the RT rq
Hi!
> > So you have serial line + pm + protocol type. Nothing GNSS specific
> > really, it would be useful to (for example) say this is modem with AT
> > commands. Or this is QMI modem.
>
> It's a matter of finding the right abstraction level. A user space
> location service will now have easy ac
On 06/01, Christian Brauner wrote:
>
> security_task_kill() already behaves like a boolean function. Let's
> actually declare it as such too.
The subject/changelog is wrong, this patch changes sigkill_pending()
> Signed-off-by: Christian Brauner
> ---
> v1->v2:
> * unchanged
> v0->v1:
> * patch
>> I agree that the fix can be done simply by using "false" for
>> smack_inode_getsecurity(), but what happens with kernfs_node_setsecdata()
>> and smack_inode_notifysecctx(). kernfs_node_setsecdata() is probably
>>ignorable
>> but smack_inode_notifysecctx() is sending the "ctx" to
>>smack_ino
MPI headers contain definitions for huge number of non-existing functions.
Most part of these functions was removed in 2012 by Dmitry Kasatkin
commit 7cf4206a99d1 ("Remove unused code from MPI library")
commit 9e235dcaf4f6 ("Revert "crypto: GnuPG based MPI lib - additional ...")
commit bc95eeadf5c6
On 06/01, Christian Brauner wrote:
>
> do_sigpending() returned 0 unconditionally so it doesn't make sense to have
> it return at all. This allows us to simplify a bunch of syscall callers.
Agreed, ACK
Hi Fabien,
Many thanks for the patch.
2018-05-30 5:17 GMT+02:00 Fabien Parent :
> When a port is connected but acting as a source, its 'online' and
> 'status' properties are identical to a port that is not connected. This
> makes it tedious for userspace to know for sure whether a port is
> conne
Quoting Amit Nischal (2018-05-28 23:07:46)
> There are certain clocks which needs to be always enabled for system
> operation. Remove support for such clocks from the clock driver and
> enable them explicitly gcc driver probe. Also fix the target name in
> kernel configuration description for SDM84
Hi Sibi,
On 6/1/2018 8:48 PM, Sibi S wrote:
> Hi Sricharan,
>
> On 06/01/2018 11:46 AM, Sricharan R wrote:
>> Hi Bjorn,
>> Thanks for this much needed consolidation.
>>
>> On 5/23/2018 10:50 AM, Bjorn Andersson wrote:
>>> Shared between all Hexagon V5 based remoteprocs is the handling of the 5
/commits/Akshay-Adiga/powernv-cpuidle-Add-support-for-new-idle-state-device-tree-format/20180601-202708
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-allmodconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce
2018-05-30 5:17 GMT+02:00 Fabien Parent :
> A new more command has been added to the ChromeOS embedded controller
> that allows to get the number of charger port count. Unlike
> EC_CMD_USB_PD_PORTS, this new command also includes the dedicated
> port if present.
>
> This command will be used to exp
On 6/1/2018 9:29 AM, CHANDAN VN wrote:
>>> I agree that the fix can be done simply by using "false" for
>>> smack_inode_getsecurity(), but what happens with kernfs_node_setsecdata()
>>> and smack_inode_notifysecctx(). kernfs_node_setsecdata() is probably
>>> ignorable
>>> but smack_inode_noti
On Sat, Jun 02, 2018 at 01:26:46AM +1000, Stephen Rothwell wrote:
> Hi,
>
> On Fri, 01 Jun 2018 07:38:42 -0700 dvh...@infradead.org wrote:
> >
> > Stephen, are the tests you use available publicly?
>
> I use the script below when I am fetching trees. You don't want the
> "gitk" invocation if you
Hi Linus,
Third pull request for -rc
Just 3 small last minute regressions that were found in the last week. The
Broadcom fix is a bit big for rc7, but since it is fixing driver crash
regressions that were merged via netdev into rc1, I am sending it.
The following changes since commit 55ba49cbcef
On Fri, Jun 01, 2018 at 11:20:39AM +0300, Andy Shevchenko wrote:
> On Fri, Jun 1, 2018 at 6:23 AM, Kai-Heng Feng
> wrote:
> > There are two new events generated by dell-wmi, rfkill and fn-lock, from
> > Dell Systems.
> >
> > When Fn-lock hotkey gets pressed to switch to function mode:
> > [85951.5
Hello, Eric.
On Fri, Jun 01, 2018 at 09:53:09AM -0500, Eric W. Biederman wrote:
>
> From a userspace perspective the cgroup of a mm is determined by which
> the cgroup the task belongs too. As practically an mm can only belong to
> a single memory cgroup having multiple tasks with the same mm in
On Sun, May 27, 2018 at 05:34:45PM +0200, Greg Kroah-Hartman wrote:
> On Sun, May 27, 2018 at 03:22:06PM +, Vadim Pasternak wrote:
> >
> >
> > > -Original Message-
> > > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > > Sent: Sunday, May 27, 2018 6:14 PM
> > > To: Vadim Pasterna
On Sat, 02 Jun 2018, Herbert Xu wrote:
On Fri, Jun 01, 2018 at 09:01:21AM -0700, Davidlohr Bueso wrote:
For the purpose of making rhashtable_init() unable to fail,
we can replace the returning -EINVAL with WARN_ONs whenever
the caller passes bogus parameters during initialization.
Signed-off-b
On Fri, Jun 01, 2018 at 09:53:47AM -0700, Davidlohr Bueso wrote:
>
> Curious, are these users setting up the param structure dynamically
> or something that they can pass along bogus values?
>
> If that's the case then yes, I definitely agree.
It's just a quality of implementation issue. This is
On Thu, May 31, 2018 at 9:05 PM, Levin wrote:
> Hi Rob,
>
>
> On 2018-05-31 10:45 PM, Rob Herring wrote:
>>
>> On Wed, May 30, 2018 at 10:27 PM, wrote:
>>>
>>> From: Levin Du
>>>
>>> In Rockchip RK3328, the output only GPIO_MUTE pin, originally for codec
>>> mute control, can also be used for g
On Fri, Jun 1, 2018 at 6:18 PM, Randy Dunlap wrote:
> On 06/01/2018 08:26 AM, Miklos Szeredi wrote:
>> On Tue, May 29, 2018 at 03:21:48PM +0200, Miklos Szeredi wrote:
>>> Hi Al,
>>>
>>> I'm sending this pull request to you instead of Linus, because a bigger than
>>> usual chunk involves the VFS.
>
Hello,
On Fri, Jun 01, 2018 at 09:25:32AM +, Hatayama, Daisuke wrote:
> kernfs_dir_pos() checks if a kernfs_node object given as one of its
> arguments is still active and if so returns it, or returns a
> kernfs_node object that is most equal (possibly smaller and larger) to
> the given object
On Fri, Jun 01, 2018 at 10:19:58AM -0500, Pierre-Louis Bossart wrote:
> I wanted to ack this patch but the Intel validation folks asked for a couple
> of days to finish their tests on a variety of Chromebooks (e.g. Lars) and
> double-check which models used the v4 topology. There is an internal th
On Sat, 02 Jun 2018, Herbert Xu wrote:
On Fri, Jun 01, 2018 at 09:53:47AM -0700, Davidlohr Bueso wrote:
Curious, are these users setting up the param structure dynamically
or something that they can pass along bogus values?
If that's the case then yes, I definitely agree.
It's just a qualit
Quoting Matti Vaittinen (2018-06-01 00:31:56)
> First of all - Thanks for looking at this!
>
> On Thu, May 31, 2018 at 08:10:39AM -0700, Stephen Boyd wrote:
> > Quoting Matti Vaittinen (2018-05-30 01:43:19)
> > > diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> > > index 41492e980ef4..4b04
The patch
ASoC: topology: Move v4 manifest header data structures to uapi
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: topology: Improve backwards compatibility with v4 topology files
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the n
The patch
ASoC: topology: Move skl-tplg-interface.h to uapi
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sen
Quoting Sricharan R (2018-06-01 06:20:37)
> Hi Stephen,
>
> On 5/31/2018 1:11 PM, Stephen Boyd wrote:
> >
> > Ok. One general comment is that it would be nice if the bindings for all
> > the nodes that are introduced included 'clocks' properties and also
> > maybe 'clock-names' properties for the
On Fri, Jun 01, 2018 at 06:17:05AM -0700, Guenter Roeck wrote:
> Other than that, there was a question if this is a Linux issue or
> a Chromebook issue (it appears that only Chromebooks shipped with
> v4 configuration files). I took that as rhetorical since upstream
> kernels (at least v4.4 and v4
On Wed, May 30, 2018 at 11:50 PM Nick Desaulniers
wrote:
> Will do further testing and cut a patch set tomorrow.
https://lkml.org/lkml/2018/6/1/679
(sorry, should have re-cc-ed everyone from this thread, will try to
re-add when there's feedback)
--
Thanks,
~Nick Desaulniers
On Fri, Jun 1, 2018 at 1:58 AM, Stephen Rothwell wrote:
> Hi Dan,
>
> Today's linux-next merge of the nvdimm tree got a conflict in:
>
> drivers/dax/super.c
>
> between commits:
>
> ba23cba9b3bd ("fs: allow per-device dax status checking for filesystems")
> 80660f20252d ("dax: change bdev_da
Hi Pavel,
> Am 01.06.2018 um 18:26 schrieb Pavel Machek :
>
> NMEA would not be my first choice, really. I'd propose something very
> similar to existing /dev/input/eventX, but with wider data types.
Since even Rome wasn't built in a day, my first choice is NMEA, but I am
open to anything on hig
On 01-Jun 18:23, Peter Zijlstra wrote:
> On Thu, May 31, 2018 at 10:46:07AM +0200, Juri Lelli wrote:
> > On 30/05/18 17:46, Quentin Perret wrote:
>
> > > So I understand why we want to got to max freq when a RT task is running,
> > > but I think there are use cases where we might want to be more
This driver was originally submitted for the TI BQ20Z75 battery IC
(commit a7640bfa10c5 ("power_supply: Add driver for TI BQ20Z75 gas gauge
IC")) and later renamed to express generic SBS support. While it's
mostly true that this driver implemented a standard SBS command set, it
takes liberties with
This compatible property was documented before the driver was renamed to
"SBS" (see commit e57f1b68c406 ("devicetree-bindings: Propagate
bq20z75->sbs rename to dt bindings")). The driver has continued to
support this property as an alternative to "sbs,sbs-battery", and
because we've noticed there a
On Fri, Jun 1, 2018 at 1:25 AM, Matti Vaittinen
wrote:
> On Thu, May 31, 2018 at 09:07:24AM -0500, Rob Herring wrote:
>> On Thu, May 31, 2018 at 5:23 AM, Matti Vaittinen
>> wrote:
>> > On Thu, May 31, 2018 at 10:17:17AM +0300, Matti Vaittinen wrote:
>> >> On Wed, May 30, 2018 at 10:01:29PM -0500,
On Fri, Jun 01, 2018 at 10:23:59AM -0700, Brian Norris wrote:
> This driver was originally submitted for the TI BQ20Z75 battery IC
> (commit a7640bfa10c5 ("power_supply: Add driver for TI BQ20Z75 gas gauge
> IC")) and later renamed to express generic SBS support. While it's
> mostly true that this
On Fri, Jun 01, 2018 at 10:24:00AM -0700, Brian Norris wrote:
> This compatible property was documented before the driver was renamed to
> "SBS" (see commit e57f1b68c406 ("devicetree-bindings: Propagate
> bq20z75->sbs rename to dt bindings")). The driver has continued to
> support this property as
On Fri, Jun 01, 2018 at 06:26:25PM +0200, Oleg Nesterov wrote:
> On 06/01, Christian Brauner wrote:
> >
> > security_task_kill() already behaves like a boolean function. Let's
> > actually declare it as such too.
>
> The subject/changelog is wrong, this patch changes sigkill_pending()
I'll add a
On Fri, Jun 01, 2018 at 03:53:07PM +0200, Vincent Guittot wrote:
> > >> >> The example with a RT task described in the cover letter can be
> > >> >> run with a DL task and will give similar results.
> > >
> > > In the cover letter you says:
> > >
> > >A rt-app use case which creates an always r
Fix memory leak in smack_inode_getsecctx
The implementation of smack_inode_getsecctx() made
incorrect assumptions about how Smack presents a security
context. Smack does not need to allocate memory to support
security contexts, so "releasing" a Smack context is a no-op.
The code made an unnecessar
On Fri, Jun 01, 2018 at 06:16:58PM +0200, Oleg Nesterov wrote:
> On 06/01, Christian Brauner wrote:
> >
> > has_pending_signals() already behaves like a boolean function. Let's
> > actually declare it as such too.
>
> But this patch does more.
>
> > - case 4: ready = signal->sig[3] &~ blocked-
Sorry Florian, I had a couple issues with my email client yesterday and
I'm not sure if you have received my reply.
Please see my reply inline.
On 5/31/2018 3:16 PM, Florian Fainelli wrote:
On 05/31/2018 10:24 AM, Ray Jui wrote:
On 5/31/2018 1:22 AM, Clément Péron wrote:
Hi Rai,
On Wed,
Hi Rob,
On 5/31/2018 9:25 AM, Rob Herring wrote:
On Fri, May 25, 2018 at 09:45:16AM -0700, Ray Jui wrote:
Update and add Stingray clock definitions and tables so they match the
binding document and the latest ASIC datasheet
Signed-off-by: Pramod Kumar
Signed-off-by: Ray Jui
---
drivers/clk
On Fri, Jun 1, 2018 at 6:01 PM, Sedat Dilek wrote:
> Hi,
>
> can someone tell me what this exactly means?
>
> What is the root cause for this?
> GNU binutils/ld?
> Compiler?
> Curently I test with clang-7.
> VirtualBox and compiler incompatible?
>
> Steps to reproduce the failure...
>
> root# modp
301 - 400 of 524 matches
Mail list logo
