On Sun, 28 Oct 2018, Linus Torvalds wrote:
> So I use a Logitech MX Anywhere 2S mouse, and really like it. I have
> the scroll-wheel unlocked, because I like flicking once to scroll a
> lot.
>
> However, the new high-res scroll code means that the scroll wheel
> action is now much too sensitive.
UG: kernel hang in early-boot stage, last printk: early console in setup code
Linux version 4.19.0-rc8-12429-g68c37cc #2
Command line: ip=vm-vp-2G-10::dhcp root=/dev/ram0 user=lkp
job=/lkp/jobs/scheduled/vm-vp-2G-10/boot-1-debian-x86_64-2018-04-03.cgz-68c37ccedcde10514898f4ba3b28c0de85c590d
On Sun, Oct 28, 2018 at 10:11 PM Changbin Du wrote:
>
> This will apply GCC '-Og' optimization level which is supported
> since GCC 4.8. This optimization level offers a reasonable level
> of optimization while maintaining fast compilation and a good
> debugging experience. It is similar to '-O1'
On Mon, Oct 29, 2018 at 02:25:42PM +0200, Pekka Pessi wrote:
> Hi Thierry,
>
> From the 0/9:
> > Are you aware of any others that we need to take into account?
> We would like to use upstream driver for RCE (and probably AON and SCE)
> mailbox handling, too. Eventually.
> > This is a bit
> > of a
On Monday, October 29, 2018 2:04:13 PM CET Peter Korsgaard wrote:
> > I think that something like this could be better
> >
> > (2) usleep_range(sleep_min, sleep_min * XXX);
> >
> > But.
> > Since it is better to make this patch ready for xfer_irqless, then I will
> > definitively go for ud
Hi.
On Sun, Oct 28, 2018 at 10:14 PM Changbin Du wrote:
>
> On Sun, Oct 28, 2018 at 10:09:21PM +0900, Masahiro Yamada wrote:
> > Hi Changbin,
> >
> > On Sun, Oct 28, 2018 at 9:52 PM Changbin Du wrote:
> >
> > > >
> > > Thanks for pointing this out and kind suggestions. I have tested with your
>
Em Fri, Oct 26, 2018 at 04:11:51PM -0400, Liang, Kan escreveu:
> On 10/26/2018 3:24 PM, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Oct 26, 2018 at 03:16:29PM -0400, Liang, Kan escreveu:
> > > On 10/26/2018 3:12 PM, Arnaldo Carvalho de Melo wrote:
> > > > Em Fri, Oct 26, 2018 at 03:07:40PM -0400, L
Hi Jonathan,
On Sun, Oct 28, 2018 at 03:40:11PM +, Jonathan Cameron wrote:
> On Wed, 24 Oct 2018 08:56:33 -0500
> Rob Herring wrote:
>
> > On Tue, 23 Oct 2018 21:53:23 +0300, Oskari Lemmela wrote:
> > > The AXP803 ADC is compatible with AXP813 ADC, but add
> > > specific compatible for it.
>
On Sun, Oct 28, 2018 at 10:13 PM Changbin Du wrote:
>
> With '-Og' optimization level, GCC would not optimize a count for a loop
> as a constant value. But BUILD_BUG_ON() only accept compile-time constant
> values. Let's use __fix_to_virt() to avoid the error.
>
> arch/arm/mm/mmu.o: In function `f
Hi Miquel,
> -Original Message-
> From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> Sent: Monday, October 29, 2018 3:21 PM
> To: Naga Sureshkumar Relli
> Cc: boris.brezil...@bootlin.com; rich...@nod.at; dw...@infradead.org;
> computersforpe...@gmail.com; marek.va...@gmail.com;
> l
Hi Marc,
On Sunday 28 October 2018 07:01 PM, Marc Zyngier wrote:
Hi Lokesh,
On Fri, 26 Oct 2018 21:19:41 +0100,
Lokesh Vutla wrote:
Hi Marc,
[..snip..]
[...]
+/**
+ * ti_sci_inta_register_event() - Register a event to an interrupt aggregator
+ * @dev: Device pointer to source gener
On Mon, Oct 29, 2018 at 3:09 AM Steven Rostedt wrote:
>
> On Sun, 28 Oct 2018 13:09:42 +
> Changbin Du wrote:
>
> > The level4_kernel_pgt is only defined when X86_5LEVEL is enabled.
> > So declare check_la57_support() as inline to make sure the code
> > referring to level4_kernel_pgt is optim
> "Federico" == Federico Vaga writes:
Hi,
>> >> Where does this 10 come from?
>> >
>> > It's true, it's just a random number. It can be zero as well, and we ask
>> > the system to just sleep for that amount of time.
>> >
>> > (1) usleep_range(sleep_min, sleep_min);
>>
>> Or just u
On Sun, Oct 28, 2018 at 10:13 PM Changbin Du wrote:
>
> This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting
I fixed "This patch add ..." to "This patch adds ..."
then applied to linux-kbuild.
> this option will prevent the compiler from optimizing the kernel by
> auto-inlini
On Tue, Oct 23, 2018 at 2:37 PM Linux Kernel Mailing List
wrote:
>
> Commit: 5c83511bdb9832c86be20fb86b783356e2f58062
> Parent: 27876f3882fdd4acb3d3614a0133ecdc777fc292
> Refname:refs/heads/master
> Web:
> https://git.kernel.org/torvalds/c/5c83511bdb9832c86be20fb86b783356e2f580
On Mon, Oct 29, 2018 at 11:04:39AM +, Lee Jones wrote:
> On Fri, 26 Oct 2018, Mark Brown wrote:
> > There's no *requirement* to provide the data even if you're using the
> > cache (and the cache support is entirely optional), there's just costs
> > to not providing it in terms of what features
On 2018-10-29 8:18 a.m., Thomas-Mich Richter wrote:
> Yes, mistake on my side...
> but it is the same type of error , regardless if 6 or 7 characters are
> compared:
>
> strncmp("cpmu_cf", "cpum_cf_diag", 7)
>
> returns 0 when it should not. The device names of both PMUs are different.
On 10/29/2018 06:02 PM, John Garry wrote:
> On 29/10/2018 12:16, Will Deacon wrote:
>> On Mon, Oct 29, 2018 at 12:14:09PM +, John Garry wrote:
>>> On 29/10/2018 11:25, Will Deacon wrote:
On Fri, Oct 26, 2018 at 09:57:47PM +0800, John Garry wrote:
> Currently it is acceptable to set
On Mon, Oct 29, 2018 at 12:25 AM Olof Johansson wrote:
>
> Hi Rob,
>
> On Fri, Oct 26, 2018 at 9:07 AM Rob Herring wrote:
> >
> > Linus,
> >
> > Please pull DT updates for 4.20. A bit bigger than normal as I've been
> > busy this cycle. There's a few things with dependencies and a few
> > things
On Mon, Oct 29, 2018 at 01:16:59PM +0100, Geert Uytterhoeven wrote:
> I can confirm syd.git.kernel.org and ord.git.kernel.org have it, but
> fra.git.kernel.org (my default) hasn't.
The Frankfurt frontend lost the VPN connection to our main infra. I'm
checking why the alerts for that didn't fire pr
On Mon, 29. Oct 20:41, Stephen Rothwell wrote:
> Hi Damian,
>
> On Mon, 29 Oct 2018 07:33:19 +0100 Damian Tometzki
> wrote:
> >
> > on the site isnt available the new linux-next ?
> > Only the old one.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
> It seems to
On Mon, 2018-10-29 at 12:56 +1100, NeilBrown wrote:
> On Fri, Oct 26 2018, Jeff Layton wrote:
>
> > On Wed, 2018-10-24 at 09:43 +1100, NeilBrown wrote:
> > > This took longer that I had wanted, due to various reasons - sorry.
> > > And I'm now posting it in a merge window, which is not ideal. I d
* Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 29, 2018 at 09:28:54AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Fri, Oct 26, 2018 at 06:58:39PM +0100, Colin King escreveu:
> > > From: Colin Ian King
> > >
> > > Trivial fix to a spelling mistake of the error access name EACCESS,
> > >
On 29/10/18 11:04, Lee Jones wrote:
On Fri, 26 Oct 2018, Mark Brown wrote:
On Fri, Oct 26, 2018 at 09:00:51AM +0100, Lee Jones wrote:
On Thu, 25 Oct 2018, Richard Fitzgerald wrote:
Largely the point. How long do you think it would take to populate the
cache if you had to read thousands of re
* Arnaldo Carvalho de Melo wrote:
> Em Fri, Oct 26, 2018 at 06:58:39PM +0100, Colin King escreveu:
> > From: Colin Ian King
> >
> > Trivial fix to a spelling mistake of the error access name EACCESS,
> > rename to EACCES
>
> Thanks, applied.
>
> And I also took the chance to fix another spe
On Mon, Oct 29, 2018 at 2:45 PM Maxime Ripard wrote:
>
> On Fri, Oct 26, 2018 at 08:13:19PM +0530, Jagan Teki wrote:
> > This series fixed the issues related to work DSI on 2-lane panel
> > which is reported on previous version[1].
> >
> > Few comments from previous version still in discussion, bu
Em Mon, Oct 29, 2018 at 09:28:54AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Oct 26, 2018 at 06:58:39PM +0100, Colin King escreveu:
> > From: Colin Ian King
> >
> > Trivial fix to a spelling mistake of the error access name EACCESS,
> > rename to EACCES
>
> Thanks, applied.
>
> And I
On 29/10/2018 12:28, Arnaldo Carvalho de Melo wrote:
> Em Fri, Oct 26, 2018 at 06:58:39PM +0100, Colin King escreveu:
>> From: Colin Ian King
>>
>> Trivial fix to a spelling mistake of the error access name EACCESS,
>> rename to EACCES
>
> Thanks, applied.
>
> And I also took the chance to fix a
On 29/10/2018 12:16, Will Deacon wrote:
On Mon, Oct 29, 2018 at 12:14:09PM +, John Garry wrote:
On 29/10/2018 11:25, Will Deacon wrote:
On Fri, Oct 26, 2018 at 09:57:47PM +0800, John Garry wrote:
Currently it is acceptable to set the distance between 2 separate nodes to
LOCAL_DISTANCE.
Re
Em Fri, Oct 26, 2018 at 06:58:39PM +0100, Colin King escreveu:
> From: Colin Ian King
>
> Trivial fix to a spelling mistake of the error access name EACCESS,
> rename to EACCES
Thanks, applied.
And I also took the chance to fix another spelling mistake, on this same
line:
-* -EACCESS
Em Sat, Oct 27, 2018 at 08:58:30PM -0700, David Miller escreveu:
>
> If I run perf top with a "make -j128" kernel build, I get ring buffer event
> processing timeouts which results in:
>
> ui__warning("Too slow to read ring buffer.\n"
> "Please try increasi
On 2018/10/28 2:06, Sergei Shtylyov wrote:
> On 27.10.2018 12:58, Yu Chen wrote:
>
>> This patch adds binding documentation to support usb hub and usb
>> data role switch of Hisilicon HiKey&HiKey960 Board.
>>
>> Cc: Rob Herring
>> Cc: Mark Rutland
>> Cc: John Stultz
>> Cc: Binghui Wang
>> Si
Hi Thierry,
From the 0/9:
Are you aware of any others that we need to take into account?
We would like to use upstream driver for RCE (and probably AON and SCE)
mailbox handling, too. Eventually.
This is a bit
of a problem because the mailbox driver doesn't really know anything
about the direc
Hi Arnd,
On Mon, Oct 29, 2018 at 12:27 PM Arnd Bergmann wrote:
> On Mon, Oct 29, 2018 at 11:26 AM Geert Uytterhoeven
> wrote:
> > On Mon, Oct 29, 2018 at 10:45 AM Arnd Bergmann wrote:
> > > One more general comment: I think this may well be the last new CPU
> > > architecture we ever add to the
On 10/26, Kees Cook wrote:
>
> On Thu, Oct 25, 2018 at 2:01 PM, Oleg Nesterov wrote:
> > On 10/25, Oleg Nesterov wrote:
> >> perhaps it needs some changes too. I even have a vague feeling that I have
> >> already
> >> blamed this function some time ago...
> >
> > Heh, yes, 3 years ago ;)
> >
> >
On 10/26/2018 05:04 PM, Sébastien Boisvert wrote:
> On 2018-10-23 11:16 a.m., Thomas Richter wrote:
>> On s390 the CPU Measurement Facility for counters now supports
>> 2 PMUs named cpum_cf (CPU Measurement Facility for counters) and
>> cpum_cf_diag (CPU Measurement Facility for diagnostic counters
> >
> > i tried it from diffrent localtion and different systems the same sitation.
> > My last tag what i
> > see is: linux-next-next-20181019.tar.gz
>
> so, I see:
>
> $ dig -tcname +short git.kernel.org
> syd.git.kernel.org.
> $ git ls-remote
>
0-Day tests found compilation error on x86.
Driver won't compile on x86_64 as "of_match_ptr" is
not found. Add missing include
At some point this fix was lost. So re-apply it.
Signed-off-by: Matti Vaittinen
---
drivers/regulator/bd718x7-regulator.c | 1 +
1 file changed, 1 insertion(+)
diff -
On Mon, Oct 29, 2018 at 12:14:09PM +, John Garry wrote:
> On 29/10/2018 11:25, Will Deacon wrote:
> >On Fri, Oct 26, 2018 at 09:57:47PM +0800, John Garry wrote:
> >>Currently it is acceptable to set the distance between 2 separate nodes to
> >>LOCAL_DISTANCE.
> >>
> >>Reject this as it is inval
Depends on:
http://lists.infradead.org/pipermail/linux-riscv/2018-October/001931.html
Why we don't have HAVE_SYSCALL_TRACEPOINTS in arch/riscv/Kconfig?
Signed-off-by: David Abdurachmanov
---
arch/riscv/kernel/ptrace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/risc
On 29/10/2018 11:25, Will Deacon wrote:
Hi John,
Hi Will,
On Fri, Oct 26, 2018 at 09:57:47PM +0800, John Garry wrote:
Currently it is acceptable to set the distance between 2 separate nodes to
LOCAL_DISTANCE.
Reject this as it is invalid.
This change avoids a crash reported in [1].
[1] h
On 10/29/18, Will Deacon wrote:
> On Mon, Oct 15, 2018 at 01:16:00PM +0200, Anders Roxell wrote:
>> -static int __kprobes patch_text(kprobe_opcode_t *addr, u32 opcode)
>> +void *alloc_insn_page(void)
>> {
>> -void *addrs[1];
>> -u32 insns[1];
>> +void *page;
>>
>> -addrs[0] = (vo
sitation.
> My last tag what i
> see is: linux-next-next-20181019.tar.gz
so, I see:
$ dig -tcname +short git.kernel.org
syd.git.kernel.org.
$ git ls-remote
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git | grep
20181029
0e2adec0725178efbb0b7019ee0198d93ba54843 re
Hi Anders,
On Mon, Oct 15, 2018 at 01:16:00PM +0200, Anders Roxell wrote:
> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
> pages")
> has successfully identified code that leaves a page with W+X
> permissions.
>
> [3.245140] arm64/mm: Found insecure W+X mapping
On Sun, Oct 14, 2018 at 8:54 PM Hans de Goede wrote:
>
> The Image Signal Processor found on Cherry Trail devices is brought up in
> D0 state on devices which have camera sensors attached to it. The ISP will
> not enter D3 state again without some massaging of its registers beforehand
> and the IS
Dear RT folks!
I'm pleased to announce the v4.18.16-rt9 patch set.
Changes since v4.18.16-rt8:
- The RCU fix, which was introduced in v4.18.7-rt5, leads to a lockdep
warning during CPU hotplug. After a discussion with upstream it was
suggested to revert the change that lead to the pro
On Sat, Oct 20, 2018 at 1:21 PM Hans de Goede wrote:
>
> Add min-x and min-y settings now that we've support for this and for some
> models also update the width/height settings with slighly more accurate
> values.
>
> This fixes touches along the edges registering at the wrong coordinates.
>
> Wh
On 29/10/18 11:04, Lee Jones wrote:
On Fri, 26 Oct 2018, Mark Brown wrote:
On Fri, Oct 26, 2018 at 09:00:51AM +0100, Lee Jones wrote:
On Thu, 25 Oct 2018, Richard Fitzgerald wrote:
Largely the point. How long do you think it would take to populate the
cache if you had to read thousands of re
On 10/23/2018 05:34 PM, Igor Stoppa wrote:
> Prevent leaks of protected memory to userspace.
> The protection from overwrited from userspace is already available, once
> the memory is write protected.
>
> Signed-off-by: Igor Stoppa
> CC: Kees Cook
> CC: Chris von Recklinghausen
> CC: linux...@kv
Commit-ID: 1df02354b42f3f4504b6287c54a8cfbe1533719f
Gitweb: https://git.kernel.org/tip/1df02354b42f3f4504b6287c54a8cfbe1533719f
Author: Colin Ian King
AuthorDate: Fri, 26 Oct 2018 18:58:39 +0100
Committer: Ingo Molnar
CommitDate: Mon, 29 Oct 2018 07:21:07 +0100
perf/headers: Fix spelli
Commit-ID: a68d75081aeccfb169575bea6f452a5a12b9f49b
Gitweb: https://git.kernel.org/tip/a68d75081aeccfb169575bea6f452a5a12b9f49b
Author: Muchun Song
AuthorDate: Sat, 27 Oct 2018 11:05:17 +0800
Committer: Ingo Molnar
CommitDate: Mon, 29 Oct 2018 07:18:04 +0100
sched/rt: Update comment in
Commit-ID: 2022cceb4e30f1bb4c84d40ffa705aa8d8d68adb
Gitweb: https://git.kernel.org/tip/2022cceb4e30f1bb4c84d40ffa705aa8d8d68adb
Author: Rasmus Villemoes
AuthorDate: Sat, 27 Oct 2018 00:20:04 +0200
Committer: Ingo Molnar
CommitDate: Mon, 29 Oct 2018 07:19:26 +0100
x86/traps: Use format
Hi John,
On Fri, Oct 26, 2018 at 09:57:47PM +0800, John Garry wrote:
> Currently it is acceptable to set the distance between 2 separate nodes to
> LOCAL_DISTANCE.
>
> Reject this as it is invalid.
>
> This change avoids a crash reported in [1].
>
> [1] https://www.spinics.net/lists/arm-kernel/
Commit-ID: 0e96f31ea4249b1e94e266fe4dff908c2983a9b3
Gitweb: https://git.kernel.org/tip/0e96f31ea4249b1e94e266fe4dff908c2983a9b3
Author: Jordan Borgner
AuthorDate: Sun, 28 Oct 2018 12:58:28 +
Committer: Ingo Molnar
CommitDate: Mon, 29 Oct 2018 07:13:28 +0100
x86: Clean up 'sizeof x'
Hi Andrey, Andrew,
On Mon, Oct 29, 2018 at 11:16:15AM +, Andrey Ryabinin wrote:
> On 10/29/2018 01:29 PM, Will Deacon wrote:
> > On Thu, Sep 20, 2018 at 04:56:30PM +0300, Andrey Ryabinin wrote:
> >> ARM64 has asm implementation of memchr(), memcmp(), str[r]chr(),
> >> str[n]cmp(), str[n]len().
On Mon, Oct 29, 2018 at 10:23:07AM +0100, Arnd Bergmann wrote:
> On Mon, Oct 29, 2018 at 2:21 AM Paul E. McKenney
> wrote:
> >
> > On Mon, Oct 29, 2018 at 12:10:03AM +0100, Andrea Parri wrote:
> > > Hopefully, with Paul's proper email address this time,
> > >
> > > Andrea
> > >
> > > On Mon, Oc
On Mon, Oct 29, 2018 at 11:26 AM Geert Uytterhoeven
wrote:
>
> On Mon, Oct 29, 2018 at 10:45 AM Arnd Bergmann wrote:
> > One more general comment: I think this may well be the last new CPU
> > architecture we ever add to the kernel. Both nds32 and c-sky are made
> > by companies that also work on
Hi Paul and all,
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Paul E. McKenney
> Sent: Thursday, August 30, 2018 01:21
> To: linux-kernel@vger.kernel.org
> Cc: mi...@kernel.org; jiangshan...@gmail.com; dipan...@
Hi,
On 10/26, Enke Chen wrote:
>
> This is really a good idea given that "parent" is declared as RCU-protected.
> Just a bit odd, though, that the "parent" has not been accessed this way in
> the code base.
It is acccessed when possible,
> So just to confirm: the revised code would look like the
On 10/29/2018 01:29 PM, Will Deacon wrote:
> On Thu, Sep 20, 2018 at 04:56:30PM +0300, Andrey Ryabinin wrote:
>> ARM64 has asm implementation of memchr(), memcmp(), str[r]chr(),
>> str[n]cmp(), str[n]len(). KASAN don't see memory accesses in asm
>> code, thus it can potentially miss many bugs.
>>
Hi Miquel,
On 2018/10/29 17:47, Miquel Raynal wrote:
> Hi Jianxin,
>
> Jianxin Pan wrote
> on Thu, 20 Sep 2018 16:50:49 +0800:
>
>> From: Liang Yang
>>
>> Add initial support for the Amlogic NAND flash controller which found
>> in the Meson-GXBB/GXL/AXG SoCs.
>>
>> Signed-off-by: Liang Yang
>
On Fri, 26 Oct 2018, Mark Brown wrote:
> On Fri, Oct 26, 2018 at 09:00:51AM +0100, Lee Jones wrote:
> > On Thu, 25 Oct 2018, Richard Fitzgerald wrote:
>
> > > Largely the point. How long do you think it would take to populate the
> > > cache if you had to read thousands of registers over I2C? Boot
Hello,
On Mon, Oct 29, 2018 at 11:08:34AM +0100, Michal Hocko wrote:
> This seems like a separate issue which should better be debugged. Please
> open a new thread describing the problem and the state of the node.
Yes, in my view it should be evaluated separately too, because it's
overall less co
On Mon, Oct 29, 2018 at 02:55:58PM +0530, Ashish Mhetre wrote:
> From: Alex Van Brunt
>
> Accessed bit is used to age a page and in generic implementation there is
> flush_tlb while clearing the accessed bit.
> Flushing a TLB is overhead on ARM64 as access flag faults don't get
> translation tabl
When I compile the 4.19.0 Linux kernel, I get this build error:
[root@f28 linux]# fgrep -r CONFIG_ACPI .config
# CONFIG_ACPI is not set
[root@f28 linux]#
[root@f28 linux]# make
CALLscripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC drivers/cpufreq/in
Hello,
We currently have several servers reporting faulty memory through MCE.
Example dmesg output:
[Mi Aug 22 13:54:47 2018] mce: [Hardware Error]: Machine check events logged
[Mi Aug 22 13:54:47 2018] mce: [Hardware Error]: CPU 12: Machine Check:
0 Bank 7: cc027c010091
[Mi Aug 22 13:54:47
Hi Stefan
On Sun, 28 Oct 2018 at 08:31, Stefan Wahren wrote:
>
> Hi Dave,
>
> > Dave Stevenson hat am 26. Oktober 2018 um
> > 19:15 geschrieben:
> >
> >
> > Thanks Stefan.
> > I've picked up your latest patches which mean I can get the driver
> > loaded via the (almost) approved method.
> > I d
On Mon, Oct 22, 2018 at 11:38:43PM +0530, Prateek Patel wrote:
> From: Sri Krishna chowdary
>
> Kmemleak scan can be cpu intensive and can stall user tasks at times.
> To prevent this, add config DEBUG_KMEMLEAK_AUTO_SCAN to enable/disable
> auto scan on boot up.
> Also protect first_run with DEBU
On Mon, Oct 29, 2018 at 12:04:22PM +0200, Pekka Pessi wrote:
> Hi Thierry,
>
> There is typically one entity (aux cpu or a VM running on CCPLEX) owning the
> "empty" or producer side of mailbox (iow, waking up on empty) and another
> entity owning the "full" or consumer side of mailbox (waking up
Hi David,
On Mon, 29 Oct 2018 09:21:20 + David Howells wrote:
>
> I think these changes should cover them all.
Yep, that fixes the build for me, thanks.
Tested-by: Stephen Rothwell
--
Cheers,
Stephen Rothwell
pgpUP0DRJWa3r.pgp
Description: OpenPGP digital signature
On Thu, Sep 20, 2018 at 04:56:29PM +0300, Andrey Ryabinin wrote:
> Since WEAK() supposed to be used instead of ENTRY() to define weak
> symbols, but unlike ENTRY() it doesn't have ALIGN directive.
> It seems there is no actual reason to not have, so let's add
> ALIGN to WEAK() too.
>
> Signed-off-
On Thu, Sep 20, 2018 at 04:56:30PM +0300, Andrey Ryabinin wrote:
> ARM64 has asm implementation of memchr(), memcmp(), str[r]chr(),
> str[n]cmp(), str[n]len(). KASAN don't see memory accesses in asm
> code, thus it can potentially miss many bugs.
>
> Ifdef out __HAVE_ARCH_* defines of these functi
On Mon, Oct 29, 2018 at 10:45 AM Arnd Bergmann wrote:
> One more general comment: I think this may well be the last new CPU
> architecture we ever add to the kernel. Both nds32 and c-sky are made
> by companies that also work on risc-v, and generally speaking risc-v
> seems to be killing off any o
On 29/10/2018 10:31, andy.t...@nxp.com wrote:
> From: Yuantian Tang
>
> The QorIQ Layerscape SoC has several thermal sensors but the current
> driver only supports one.
>
> Massage the code to be sensor oriented and allow the support for
> multiple sensors.
>
> Signed-off-by: Yuantian Tang
> -
On 2018-10-27 14:06, Miguel Ojeda wrote:
> Hi Rasmus,
>
> On Sat, Oct 27, 2018 at 1:24 AM Rasmus Villemoes
> wrote:
>>
>> +/*
>> + * Optional
>
> I did quick check and gcc >= 4.1, clang >= 3.0, icc >= 13 compilers
> seem to support it (or at least recognize it, even if they just ignore
> it), so
On Sun, Oct 28, 2018 at 11:31 PM Wolfram Sang wrote:
>
> On Fri, Oct 19, 2018 at 09:59:58AM +0100, Charles Keepax wrote:
> > The IRQ will be mapped in i2c_device_probe only if client->irq is zero and
> > i2c_device_remove does not clear this. When rebinding an I2C device,
> > whos IRQ provider has
Reorganize get_fdt lookup loop, clearly showing that:
- Nothing is done for table entries that do not have fdt_guid
- Once an entry with fdt_guid is found, break out of the loop
No functional changes.
Signed-off-by: Julien Thierry
Suggested-by: Joe Perches
Cc: Ard Biesheuvel
---
drivers/firmw
My Beloved,
I am writing this mail to you with heavy tears in my eyes and great sorrow in
my heart. As I informed you earlier, I am (Mrs.) Sharon Smith from Uzbekistan
and a widow to late Martin Smith; I am 63 years old, suffering from long time
Cancer of the breast. From all indications my
On Sun, Oct 28, 2018 at 11:30 PM Wolfram Sang wrote:
>
> On Fri, Oct 19, 2018 at 09:59:57AM +0100, Charles Keepax wrote:
> > irq_create_mapping calls irq_find_mapping internally and will use the
> > found mapping if one exists, so there is no need to manually call this
> > from i2c_smbus_host_noti
On Mon, Oct 29, 2018 at 7:06 PM Tomasz Figa wrote:
>
> Hi Stanimir,
>
> On Mon, Oct 29, 2018 at 6:45 PM Stanimir Varbanov
> wrote:
> >
> > Hi Tomasz,
> >
> > On 10/22/2018 05:48 PM, Tomasz Figa wrote:
> > > Due to complexity of the video decoding process, the V4L2 drivers of
> > > stateful decode
On Mon, Oct 29, 2018 at 11:04:06AM +0200, Pekka Pessi wrote:
> Hi Thierry,
>
> What is the use case for the mailbox driver? What kind of entity will be
> there consuming sent messages and sending messages to kernel?
This is currently only used for the TCU. I'm sure there could be other
cases, but
In the initial commit [1], I added differential outputs of the codec as
separate `+` and `-` widgets:
OUTL+
OUTR+
OUTL-
OUTR-
Later, in the commit [2], I added a control to switch the outputs between
differential and single-ended modes. Having this control, the `+` and `-`
separation in widgets s
DAC may be switched between differential and single-ended output.
Signed-off-by: Kirill Marinushkin
---
sound/soc/codecs/pcm3060.c | 9 +
sound/soc/codecs/pcm3060.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/sound/soc/codecs/pcm3060.c b/sound/soc/codecs/pcm3060.c
index 494d9d
On Mon 29-10-18 20:42:53, Balbir Singh wrote:
> On Mon, Oct 29, 2018 at 10:00:35AM +0100, Michal Hocko wrote:
[...]
> > These hugetlb allocations might be disruptive and that is an expected
> > behavior because this is an explicit requirement from an admin to
> > pre-allocate large pages for the fu
On Thu, Oct 18, 2018 at 08:17:10PM -0400, Doug Ledford wrote:
> On Thu, 2018-10-18 at 14:01 +0300, Leon Romanovsky wrote:
> > On Thu, Oct 18, 2018 at 10:02:58AM +0200, Gustavo A. R. Silva wrote:
> > > Cast *max_num_sg* to u64 in order to give the compiler complete
> > > information about the proper
Hi Thierry,
There is typically one entity (aux cpu or a VM running on CCPLEX) owning
the "empty" or producer side of mailbox (iow, waking up on empty) and
another entity owning the "full" or consumer side of mailbox (waking up
on full). An entity should not muck with the interrupts used by the
On 29/10/2018 09:25, Ashish Mhetre wrote:
> From: Alex Van Brunt
>
> Accessed bit is used to age a page and in generic implementation there is
> flush_tlb while clearing the accessed bit.
> Flushing a TLB is overhead on ARM64 as access flag faults don't get
> translation table entries cached in
On Fri, Oct 19, 2018 at 02:22:53PM +0100, Jon Hunter wrote:
> From: Jonathan Hunter
>
> The tps6586x driver creates an irqchip that is used by its various child
> devices for managing interrupts. The tps6586x-rtc device is one of its
> children that uses the tps6586x irqchip. When using the tps65
Hi Naga,
Naga Sureshkumar Relli wrote on
Tue, 25 Sep 2018 17:50:28 +0530:
> This patch series adds the basic driver support for Arasan NAND Flash
> controller.
> We are reinitiating the patch series by fixing the comments given by Miquel
> and Boris.
> Major changes are exec_op() implementatio
Hello Dear
Do you have the passion for humanitarian welfare?
Can you devote your time and be totally committed and devoted
to run multi-million pounds humanitarian charity project sponsored
totally by me; with an incentive/compensation accrual to you for
your time and effort and at no cost to yo
On Sun, Oct 28, 2018 at 6:07 PM Al Viro wrote:
>
> On Thu, Sep 13, 2018 at 12:29:02PM +0200, Arnd Bergmann wrote:
>
> > I was hoping that the _ptrarg suffix gives enough warning here,
> > but maybe not. I was careful to only use it in cases that I
> > checked are safe, either using only pointer ar
Hi Jianxin,
Jianxin Pan wrote
on Thu, 20 Sep 2018 16:50:49 +0800:
> From: Liang Yang
>
> Add initial support for the Amlogic NAND flash controller which found
> in the Meson-GXBB/GXL/AXG SoCs.
>
> Signed-off-by: Liang Yang
> Signed-off-by: Yixun Lan
> Signed-off-by: Jianxin Pan
> ---
I lo
On Mon, Oct 29, 2018 at 8:30 AM Boris Brezillon
wrote:
> On Sun, 28 Oct 2018 19:13:26 -0700 Kees Cook wrote:
> > On Fri, Oct 12, 2018 at 2:22 AM, Boris Brezillon
> > wrote:
> > > On Fri, 12 Oct 2018 11:19:52 +0200 Arnd Bergmann wrote:
> > > > On Fri, Oct 12, 2018 at 11:16 AM Boris Brezillon
>
On Mon, Oct 29, 2018 at 11:40:41AM +0200, Matti Vaittinen wrote:
> Should I just create another patch to you where this inclusion is done again
> or is there some better way to handle this? Can you cherry pick or
> re-apply the commit
Just send another patch, it's easiest.
signature.asc
Descrip
On Sun, Oct 28, 2018 at 10:11 PM Linus Torvalds
wrote:
>
> Arnd,
> I was kind of hoping/expecting to get an explicit ack for this from
> you, since it's a new architecture.
>
> Good to merge?
Yes.
For the pull request (in case you want to add it to the merge changelog):
I did a thorough review
For all 96Boards, the following standard is used for onboard LEDs.
green:user1 default-trigger: heartbeat
green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
green:user3 default-trigger: mmc1 (SD-card)
green:user4 default-trigger: none, panic-indicator
yellow:wlan default-trigger
For all 96Boards, the following standard is used for onboard LEDs.
green:user1 default-trigger: heartbeat
green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
green:user3 default-trigger: mmc1 (SD-card)
green:user4 default-trigger: none, panic-indicator
yellow:wlan default-trigger
For all 96Boards, the following standard is used for onboard LEDs.
green:user1 default-trigger: heartbeat
green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
green:user3 default-trigger: mmc1 (SD-card)
green:user4 default-trigger: none, panic-indicator
yellow:wlan default-trigger
This patchset standardizes the onboard LEDs on 96Boards by maintaining
common labels and triggers as below:
green:user1 default-trigger: heartbeat
green:user2 default-trigger: mmc0/disk-activity (onboard-storage)
green:user3 default-trigger: mmc1 (SD card)
green:user4 default-trigger: none, pa
Add on-board LED support for Rock960 board based on the following
standard used by rest of the 96Boards:
green:user1 default-trigger: heartbeat
green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
green:user3 default-trigger: mmc1 (SD-card)
green:user4 default-trigger: none, panic-
401 - 500 of 572 matches
Mail list logo