4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 298bc15b2079c324e82d0a6fda39c3d762af7282 ]
Move the out-of-order and duplicate ACK packet check to before the call to
rxrpc_input_ackinfo() so that the receive window size and MTU si
On Fri, Oct 19, 2018 at 07:30:16PM +0900, Masahiro Yamada wrote:
>
> Arnd, Olof,
>
> I know it is very late in this development cycle.
>
> If possible, could you directly apply these two patches
> to your ARM-SoC, aiming for the upcoming v4.20-rc1 MW?
>
> If not, I can wait for v4.21-rc1.
Hi,
On Fri, Oct 05, 2018 at 09:33:28AM -0700, Kees Cook wrote:
> On Fri, Oct 5, 2018 at 9:15 AM, Arnd Bergmann wrote:
> > Testing randconfig builds found an instance of a VLA that was
> > missed when determining that we have removed them all:
> >
> > arch/arm/plat-orion/mpp.c: In function 'orion_mpp_c
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 5ba6b4aa9a410c5e2c6417df52b5e2118ea9b467 ]
The driver currently silently accepts unsupported Wake-on-LAN modes
(other than WAKE_PHY or WAKE_MAGIC) without reporting that to the user,
On Fri, Nov 2, 2018 at 7:27 PM Sean Christopherson
wrote:
> On Fri, Nov 02, 2018 at 10:48:38AM -0700, Andy Lutomirski wrote:
> > This whole mechanism seems very complicated, and it's not clear
> > exactly what behavior user code wants.
>
> No argument there. That's why I like the approach of dump
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit d85536cde91fcfed6fb8d983783bd2b92c843939 ]
Add missing prepare/unprepare operations for fbi->clk,
this fixes following kernel warning:
[ cut here ]
WARNI
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 1222a16014888ed9733c11e221730d4a8196222b ]
Use array_index_nospec() to sanitize i with respect to speculation.
Note that the user doesn't control i directly, but can make it out
of
This is the start of the stable review cycle for the 4.14.79 release.
There are 143 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 by Sun Nov 4 18:27:59 UTC 2018.
Anything recei
On Fri, Nov 02, 2018 at 05:16:51PM +, Marc Zyngier wrote:
> When switching to the new iovec accessors, a negation got subtly
> dropped, leading to 9p being remarkably broken (here with kvmtool):
>
> [7.430941] VFS: Mounted root (9p filesystem) on device 0:15.
> [7.432080] devtmpfs: mou
Hello All,
Στις 2018-11-02 01:04, Atish Patra έγραψε:
This patch series adds the cpu topology for RISC-V. It contains
both the DT binding and actual source code. It has been tested on
QEMU & Unleashed board.
The idea is based on cpu-map in ARM with changes related to how
we define SMT systems.
Hi Thomas,
this is a late pull request for the c-sky clocksource and clockevent.
These are new drivers, they passed the review process several times for
the c-sky architecture.
- Add the per cpu timer for the c-sky architecture (Guo Ren)
- Add the global timer for the c-sky architecture (Guo
Greg, are you picking up this patch?
Would be nice to have in v4.19.1.
On Tue, 23 Oct 2018, Nicolas Pitre wrote:
> On Tue, 23 Oct 2018, Mikulas Patocka wrote:
>
> > If you run aptitude on framebuffer console, the display is corrupted. The
> > corruption is caused by the commit d8ae7242. The pa
From: Guo Ren
Dt-bingdings doc for C-SKY SMP system setting.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
Signed-off-by: Daniel Lezcano
---
.../devicetree/bindings/timer/csky,mptimer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/de
From: Guo Ren
The driver is for C-SKY SMP timer. It only supports oneshot event
and 32bit overflow for clocksource. Per cpu core has one timer and
all timers share one clock-counter-input from the same clocksource.
This use mfcr&mtcr instructions to access the regs.
Signed-off-by: Guo Ren
Cc:
From: Guo Ren
The driver is for gx6605s SOC system timer and there are two
same timers in gx6605s. We use one for clkevt and another one for
clksrc.
The timer is mmio map to access, so we need give mmio address in dts.
The counter at 0x0 offset is clock event.
The counter at 0x40 offset is clo
From: Guo Ren
Dt-bindings doc for gx6605s SOC's system timer.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
Signed-off-by: Daniel Lezcano
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentation/
From: Linus Torvalds
commit 51d7b120418e99d6b3bf8df9eb3cc31e8171dee4 upstream ported to
3.18.y
In commit c4004b02f8e5b ("x86: remove the kernel code/data/bss resources
from /proc/iomem") I was hoping to remove the phyiscal kernel address
data from /proc/iomem entirely, but that had to be reverte
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Karsten Graul
[ Upstream commit fb692ec4117f6fd25044cfb5720d6b79d400dc65 ]
The pointer to the link group is unset in the smc connection structure
right before the call to smc_buf_unuse. Provid
On Fri, Nov 02, 2018 at 03:09:14PM -0400, Nicolas Pitre wrote:
> Greg, are you picking up this patch?
>
> Would be nice to have in v4.19.1.
4.19.1-rc1 is already out. My queue is _huge_ give me some time to
catch up...
greg k-h
On Thu, Nov 1, 2018 at 10:07 AM Alexey Skidanov
wrote:
> On 11/1/18 18:48, Stephen Bates wrote:
> >>I use gen_pool_first_fit_align() as pool allocation algorithm allocating
> >>buffers with requested alignment. But if a chunk base address is not
> >>aligned to the requested alignment(
* Mathieu Desnoyers:
> Basically, the use-cases targeted are those where some cores on the
> system support a larger instruction set than others. So for instance,
> some cores could use a faster atomic add instruction than others,
> which should rely on a slower fallback. This is also the same sto
On Wed, Jul 18, 2018 at 4:17 PM, Tetsuo Handa
wrote:
> On 2018/07/18 23:11, Dmitry Vyukov wrote:
>> On Wed, Jul 18, 2018 at 3:35 PM, Tetsuo Handa
>> wrote:
>> This seems to be related to 9p. After rerunning the log I got:
>>
>> root@syzkaller:~# ps afxu | grep syz
>> root 1825
On Fri, Nov 2, 2018 at 8:12 AM Mathieu Desnoyers
wrote:
>
> Hi Richard,
>
> I stumbled on these articles:
>
> -
> https://medium.com/@jadr2ddude/a-big-little-problem-a-tale-of-big-little-gone-wrong-e7778ce744bb
> - https://www.mono-project.com/news/2016/09/12/arm64-icache/
>
> and discussed them
Hi,
This is V8 of the "KASLR feature to randomize each loadable module" patchset.
The purpose is to increase the randomization and also to make the modules
randomized in relation to each other instead of just the base, so that if one
module leaks the location of the others can't be inferred.
This
This changes the behavior of the KASLR logic for allocating memory for the text
sections of loadable modules. It randomizes the location of each module text
section with about 17 bits of entropy in typical use. This is enabled on X86_64
only. For 32 bit, the behavior is unchanged.
It refactors exi
Add debugfs file "modfraginfo" for providing info on module space fragmentation.
This can be used for determining if loadable module randomization is causing any
problems for extreme module loading situations, like huge numbers of modules or
extremely large modules.
Sample output when KASLR is ena
This adds a test module in lib/, and a script in kselftest that does
benchmarking on the allocation of memory in the module space. Performance here
would have some small impact on kernel module insertions, BPF JIT insertions
and kprobes. In the case of KASLR features for the module space, this modu
On Thu, Jul 26, 2018 at 11:12 AM, Miklos Szeredi wrote:
> On Thu, Jul 26, 2018 at 10:44 AM, Miklos Szeredi wrote:
>> On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote:
>>> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote:
>
>>> Maybe more waits in fuse need to be interruptible? E.g. re
Create __vmalloc_node_try_addr function that tries to allocate at a specific
address without triggering any lazy purging. In order to support this behavior
a try_addr argument was plugged into several of the static helpers.
This also changes logic in __get_vm_area_node to be faster in cases where
On Thu, Nov 1, 2018 at 2:21 AM João Paulo Rechi Vita wrote:
>
> Asus laptops have a hotkey function on the F7 key to turn the display
> backlight OFF, labeled with a screen with a X inside, as shown on
> https://dlcdnimgs.asus.com/websites/global/products/Xep1ZcSY8dyWXK11/images/keyboard.png
>
> T
On Fri, Nov 02, 2018 at 06:48:23PM +0100, Michal Hocko wrote:
> On Fri 02-11-18 17:25:58, Roman Gushchin wrote:
> > On Fri, Nov 02, 2018 at 05:51:47PM +0100, Michal Hocko wrote:
> > > On Fri 02-11-18 16:22:41, Roman Gushchin wrote:
> [...]
> > > > 2) We do forget to scan the last page in the LRU li
The current x86 page fault handler allows stack access below the stack
pointer if it is no more than 64k+256 bytes. Any access beyond the 64k+
limit will cause a segmentation fault.
The gcc -fstack-check option generates code to probe the stack for
large stack allocation to see if the stack is acc
On Fri, Nov 02, 2018 at 04:07:01AM +, Al Viro wrote:
> On Thu, Nov 01, 2018 at 11:59:23PM +, David Howells wrote:
>
> > (*) mount-api-core. These are the internal-only patches that add the
> > fs_context, the legacy wrapper and the security hooks and make certain
> > filesystem
Hi,
On 11/2/18 4:38 PM, Arnd Bergmann wrote:
With the new CONFIG_CC_OPTIMIZE_FOR_DEBUGGING option, we get a link
error in the vboxguest driver, when that fails to optimize out the
call to the compat handler:
drivers/virt/vboxguest/vboxguest_core.o: In function `vbg_ioctl_hgcm_call':
vboxguest_c
On 11/2/18 12:40 PM, Waiman Long wrote:
> The 64k+ limit check is kind of arbitrary. So the check is now removed
> to just let expand_stack() decide if a segmentation fault should happen.
With the 64k check removed, what's the next limit that we bump into? Is
it just the stack_guard_gap space abo
On Wed, Oct 31, 2018 at 11:22:59AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 30, 2018 at 03:21:23PM -0700, Joel Fernandes wrote:
> > On Tue, Oct 30, 2018 at 05:58:00AM -0700, Paul E. McKenney wrote:
> > > On Mon, Oct 29, 2018 at 08:44:52PM -0700, Joel Fernandes wrote:
> > > > On Mon, Oct 29, 201
On 11/02/2018 03:44 PM, Dave Hansen wrote:
> On 11/2/18 12:40 PM, Waiman Long wrote:
>> The 64k+ limit check is kind of arbitrary. So the check is now removed
>> to just let expand_stack() decide if a segmentation fault should happen.
> With the 64k check removed, what's the next limit that we bump
Hi Greg,
On Fri, Nov 2, 2018 at 6:53 PM Greg Kroah-Hartman
wrote:
>
> 4.14-stable review patch. If anyone has any objections, please let me know.
It seems this has already been reverted upstream:
9bf4e370048d ("ARM: dts: tegra20: Revert "Fix ULPI regression on Tegra20"")
--
Regards
Sudip
On Fri, Nov 2, 2018 at 11:01 AM, Joel Fernandes wrote:
> On Thu, Nov 01, 2018 at 04:52:00PM -0700, Kees Cook wrote:
>> The actual number of bytes stored in a PRZ is smaller than the
>> bytes requested by platform data, since there is a header on each
>> PRZ. Additionally, if ECC is enabled, there
Hi Greg,
On Fri, Nov 2, 2018 at 6:52 PM Greg Kroah-Hartman
wrote:
>
> 4.14-stable review patch. If anyone has any objections, please let me know.
There is another upstream patch which fixes this one.
e3ca34880652 ("net/mlx5: Fix build break when CONFIG_SMP=n")
--
Regards
Sudip
On Thu, Nov 01, 2018 at 11:15:18PM -0700, Joel Fernandes wrote:
> On Thu, Nov 01, 2018 at 09:13:07AM -0700, Paul E. McKenney wrote:
> > > > > BTW I do want to discuss about this smp_mb patch above with you at
> > > > > LPC if you
> > > > > had time, even though we are removing it from the document
[trimming cc list]
On 2018-11-01 23:57, Kees Cook wrote:
> On Thu, Nov 1, 2018 at 3:06 PM, Rasmus Villemoes
> wrote:
>> referring to an anonymous object in .rodata; one gets code gen like
>>
>> +: 31 c0 xor%eax,%eax
>> +: 48 b8 61 63 70 69 2dmovabs $0x7570632d6
On Fri, Nov 2, 2018 at 12:50 PM Waiman Long wrote:
>
> On 11/02/2018 03:44 PM, Dave Hansen wrote:
> > On 11/2/18 12:40 PM, Waiman Long wrote:
> >> The 64k+ limit check is kind of arbitrary. So the check is now removed
> >> to just let expand_stack() decide if a segmentation fault should happen.
>
On Fri, Oct 26, 2018 at 07:48:35AM -0700, Paul E. McKenney wrote:
> On Fri, Oct 26, 2018 at 04:00:53AM +, Krein, Dennis wrote:
> > I have a patch attached that fixes the problem for us. I also tried a
> > version with an smb_mb() call added at end of rcu_segcblist_enqueue()
> > - but that turn
On Fri, Nov 2, 2018 at 3:04 PM Daniel Walker wrote:
> Do you have any thought on how to implement it ? I was think abstracting the
> endian functions in the nodelist.h
Yes, see what UFS does.
> static inline jint16_t cpu_to_je16(jint16_t x) {
> if (check_big_endian()) {
>
Hi Greg,
On Fri, Nov 2, 2018 at 6:51 PM Greg Kroah-Hartman
wrote:
>
> 4.14-stable review patch. If anyone has any objections, please let me know.
This has been fixed by another upstream commit:
7ee18d677989 ("x86/power: Make restore_processor_context() sane")
You can not directly apply it, wil
Am Freitag, 2. November 2018, 16:39:24 CET schrieb Arnd Bergmann:
> Having two shash descriptors on the stack cause a very significant kernel
> stack usage that can cross the warning threshold:
>
> fs/ubifs/replay.c: In function 'authenticate_sleb':
> fs/ubifs/replay.c:633:1: error: the frame size
On 11/02/2018 04:11 PM, Andy Lutomirski wrote:
> On Fri, Nov 2, 2018 at 12:50 PM Waiman Long wrote:
>> On 11/02/2018 03:44 PM, Dave Hansen wrote:
>>> On 11/2/18 12:40 PM, Waiman Long wrote:
The 64k+ limit check is kind of arbitrary. So the check is now removed
to just let expand_stack()
On 11/2/18 6:09 AM, Rob Herring wrote:
On Thu, Nov 1, 2018 at 6:04 PM Atish Patra wrote:
Define a RISC-V cpu topology. This is based on cpu-map in ARM world.
But it doesn't need a separate thread node for defining SMT systems.
Multiple cpu phandle properties can be parsed to identify the sibli
On Fri, Nov 2, 2018 at 11:32 AM, Joel Fernandes wrote:
> On Thu, Nov 01, 2018 at 04:51:59PM -0700, Kees Cook wrote:
>> Since commit 70ad35db3321 ("pstore: Convert console write to use
>> ->write_buf"), the console writer does not use the preallocated crash
>> dump buffer any more, so there is no r
Hi,
On Fri, Nov 2, 2018 at 11:35 AM Stephen Boyd wrote:
>
> We need to enable runtime PM on this i2c controller before populating
> child devices with i2c_add_adapter(). Otherwise, if a child device uses
> runtime PM and stays runtime PM enabled we'll get the following warning
> at boot.
>
> Ena
On Fri, Nov 2, 2018 at 1:09 PM, Rasmus Villemoes
wrote:
> That's a bit too naive. At the very least, you must exclude static
> stuff, i.e. restrict to actual auto variables. Otherwise you're making
> things worse (a "static const char []" just occupies some space in
> .rodata, a "static const char
On Mon 2018-09-10 13:20:33, Lubomir Rintel wrote:
> s/whold/whole/.
>
> Jiri Kosina
Missing "Cc:"?
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> diff --git
> a/Documentation/devicetree/bindings/interrupt-controller/mrvl,intc.txt
> b/Documentation/devicetree/bindings/interrupt-c
On Fri, Nov 02, 2018 at 08:33:25PM +, Krein, Dennis wrote:
> Yes it's fine with me to sign off on this. I have done extensive
> additional testing with the patch in my repro setup and have run well
> over 100 hours with no problem. The repro setup with rcutorture and the
> inotify app typical
Quoting Amit Nischal (2018-08-12 23:33:05)
> diff --git a/drivers/clk/qcom/clk-rcg2.c b/drivers/clk/qcom/clk-rcg2.c
> index 52208d4..a57ce00 100644
> --- a/drivers/clk/qcom/clk-rcg2.c
> +++ b/drivers/clk/qcom/clk-rcg2.c
> @@ -866,7 +866,7 @@ static int clk_rcg2_shared_set_rate_and_parent(struct
>
On 11/2/18 8:50 AM, Sudeep Holla wrote:
On Fri, Nov 02, 2018 at 10:11:38AM -0500, Rob Herring wrote:
On Fri, Nov 2, 2018 at 8:31 AM Sudeep Holla wrote:
On Fri, Nov 02, 2018 at 08:09:39AM -0500, Rob Herring wrote:
On Thu, Nov 1, 2018 at 6:04 PM Atish Patra wrote:
Define a RISC-V cpu topolo
Automatic const char[] variables cause unnecessary code
generation. For example, the this_mod variable leads to
3f04: 48 b8 5f 5f 74 68 69 73 5f 6d movabs $0x6d5f736968745f5f,%rax
# __this_m
3f0e: 4c 8d 44 24 02 lea0x2(%rsp),%r8
3f13: 48 8d 7c
On 11/2/18 9:17 PM, Daniel Mentz wrote:
> On Thu, Nov 1, 2018 at 10:07 AM Alexey Skidanov
> wrote:
>> On 11/1/18 18:48, Stephen Bates wrote:
I use gen_pool_first_fit_align() as pool allocation algorithm allocating
buffers with requested alignment. But if a chunk base address is
Quoting Doug Anderson (2018-11-02 13:43:25)
> Thanks for the fix. It looks good, but can you also swap the
> pm_runtime_disable() and i2c_del_adapter() calls in geni_i2c_remove()
> to match?
>
Good catch. Will resend with that.
We need to enable runtime PM on this i2c controller before populating
child devices with i2c_add_adapter(). Otherwise, if a child device uses
runtime PM and stays runtime PM enabled we'll get the following warning
at boot.
Enabling runtime PM for inactive device (a98000.i2c) with active children
Hi,
On Fri, Nov 2, 2018 at 1:57 PM Stephen Boyd wrote:
>
> We need to enable runtime PM on this i2c controller before populating
> child devices with i2c_add_adapter(). Otherwise, if a child device uses
> runtime PM and stays runtime PM enabled we'll get the following warning
> at boot.
>
> Enab
Since __LINE__ is part of the symbol created by __ADDRESSABLE, almost
any change causes those symbols to disappear and get reincarnated, e.g.
add/remove: 4/4 grow/shrink: 0/3 up/down: 32/-171 (-139)
Function old new delta
__addressable_tracing_set_default_
Daniel,
On Fri, 2 Nov 2018, Daniel Lezcano wrote:
> this is a late pull request for the c-sky clocksource and clockevent.
> These are new drivers, they passed the review process several times for
> the c-sky architecture.
>
> - Add the per cpu timer for the c-sky architecture (Guo Ren)
>
> -
On Fri, Oct 26, 2018 at 5:29 AM Kirill A. Shutemov
wrote:
>
> On 5-level paging LDT remap area is placed in the middle of
> KASLR randomization region and it can overlap with direct mapping,
> vmalloc or vmap area.
>
> Let's move LDT just before direct mapping which makes it safe for KASLR.
> This
On Fri, Oct 26, 2018 at 5:29 AM Kirill A. Shutemov
wrote:
>
> Commit
>
> 9bae3197e15d ("x86/ldt: Split out sanity check in map_ldt_struct()")
>
> moved page table syncing into a separate funtion. pgd variable is now
> unsed in map_ldt_struct().
Reviewed-by: Andy Lutomirski
On Fri, Nov 2, 2018 at 3:53 PM Atish Patra wrote:
>
> On 11/2/18 8:50 AM, Sudeep Holla wrote:
> > On Fri, Nov 02, 2018 at 10:11:38AM -0500, Rob Herring wrote:
> >> On Fri, Nov 2, 2018 at 8:31 AM Sudeep Holla wrote:
> >>>
> >>> On Fri, Nov 02, 2018 at 08:09:39AM -0500, Rob Herring wrote:
> On
On 11/2/18 11:59 AM, Nick Kossifidis wrote:
Hello All,
Στις 2018-11-02 01:04, Atish Patra έγραψε:
This patch series adds the cpu topology for RISC-V. It contains
both the DT binding and actual source code. It has been tested on
QEMU & Unleashed board.
The idea is based on cpu-map in ARM with c
On Fri, Nov 02, 2018 at 09:15:06PM +0100, Richard Weinberger wrote:
> On Fri, Nov 2, 2018 at 3:04 PM Daniel Walker wrote:
> > Do you have any thought on how to implement it ? I was think abstracting the
> > endian functions in the nodelist.h
>
> Yes, see what UFS does.
>
> > static inline jint16
On Fri, Nov 2, 2018 at 1:55 PM Alexey Skidanov
wrote:
>
>
>
> On 11/2/18 9:17 PM, Daniel Mentz wrote:
> > On Thu, Nov 1, 2018 at 10:07 AM Alexey Skidanov
> > wrote:
> >> On 11/1/18 18:48, Stephen Bates wrote:
> I use gen_pool_first_fit_align() as pool allocation algorithm
> allocat
Am Freitag, 2. November 2018, 22:14:44 CET schrieb Daniel Walker:
> > Make it a mount option and store the endianness mode in the super block.
>
> It's actually a mkfs option currently. I'm not sure how that factors in,
>
> from the mkfs.jffs2 man page,
>
>-l, --little-endian
>
On Mon, Feb 5, 2018 at 2:31 AM Andrey Ryabinin wrote:
>
> On 02/05/2018 01:15 PM, Arnd Bergmann wrote:
> > On Mon, Feb 5, 2018 at 10:02 AM, Andrey Ryabinin
> > wrote:
> >>
> >>
> >> On 02/02/2018 06:47 PM, Arnd Bergmann wrote:
> >>> gcc-8 complains about the prototype for this function:
> >>>
> >
Dear Friend,
I know that this mail will come to you as a surprise as we have never
met before, but need not to worry as I am contacting you independently
of my investigation and no one is informed of this communication. I
need your urgent assistance in transferring the sum of $11.3million
immediat
With the introduction of commit 3edfb7bd76bd ("gpiolib: Show correct
direction from the beginning") the gpiolib will attempt to read the
direction of all pins, which triggers a read from protected register
regions.
The pins 0 through 3 and 81 through 84 are protected, so mark these as
reserved.
S
Enable a few core config options to be able to boot SDM845 MTP.
The GCC, PINCTRL and GENI options are required to be able to boot to a
console. Several clocks from GCC are parented by the "bi_tcxo" clock
from the RPMH clock driver, so enable this to save others the time to
debug the missing parent
On Fri, Nov 02, 2018 at 01:40:06PM -0700, Kees Cook wrote:
> On Fri, Nov 2, 2018 at 11:32 AM, Joel Fernandes
> wrote:
> > On Thu, Nov 01, 2018 at 04:51:59PM -0700, Kees Cook wrote:
> >> Since commit 70ad35db3321 ("pstore: Convert console write to use
> >> ->write_buf"), the console writer does no
> -Original Message-
> From: gre...@linuxfoundation.org
> Sent: Thursday, November 1, 2018 11:57 AM
> To: Dexuan Cui
> Cc: Michael Kelley ; KY Srinivasan
> ; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com; Stephen
On 11/2/18, Pierre-Louis Bossart wrote:
>
> On 11/2/18 6:24 AM, Arnd Bergmann wrote:
>> The skylake sound support is written to work both with or without
>> CONFIG_SND_SOC_HDAC_HDA, and uses an #ifdef to decide whether it should
>> link against that. However, this fails with SND_SOC_ALL_CODECS=m o
On 11/2/18, Vasily Khoruzhick wrote:
> On Friday, November 2, 2018 8:33:40 AM PDT Arnd Bergmann wrote:
>> The newly added SND_SUN50I_CODEC_ANALOG driver selects a nonexisting
>> symbol SND_SUNXI_ADDA_PR_REGMAP, which was evidently intended to replace
>> SND_SUN8I_ADDA_PR_REGMAP, but since they are
On Fri, Nov 02, 2018 at 08:02:23PM +0100, Jann Horn wrote:
> On Fri, Nov 2, 2018 at 7:27 PM Sean Christopherson
> wrote:
> > On Fri, Nov 02, 2018 at 10:48:38AM -0700, Andy Lutomirski wrote:
> > > This whole mechanism seems very complicated, and it's not clear
> > > exactly what behavior user code
On 11/2/18, Andy Shevchenko wrote:
> On Fri, Nov 02, 2018 at 12:06:43PM +0100, Arnd Bergmann wrote:
>> We still get a link failure with IOSF_MBI=m when the xpower driver
>> is built-in:
>>
>> drivers/acpi/pmic/intel_pmic_xpower.o: In function
>> `intel_xpower_pmic_update_power':
>> intel_pmic_xpow
On Fri, Nov 2, 2018 at 3:04 PM Arnd Bergmann wrote:
>
> On 11/2/18, Vasily Khoruzhick wrote:
> > On Friday, November 2, 2018 8:33:40 AM PDT Arnd Bergmann wrote:
> >> The newly added SND_SUN50I_CODEC_ANALOG driver selects a nonexisting
> >> symbol SND_SUNXI_ADDA_PR_REGMAP, which was evidently inte
On Thu, Nov 01, 2018 at 10:53:40AM -0700, Andy Lutomirski wrote:
> If a handler is registered, then, if a synchronous exception happens
> (page fault, etc), the kernel would set up an exception frame as usual
> but, rather than checking for signal handlers, it would just call the
> registered handl
On 11/2/18, Arnd Bergmann wrote:
> On 11/2/18, Andy Shevchenko wrote:
>> On Fri, Nov 02, 2018 at 12:06:43PM +0100, Arnd Bergmann wrote:
>>> We still get a link failure with IOSF_MBI=m when the xpower driver
>>> is built-in:
>>>
>>> drivers/acpi/pmic/intel_pmic_xpower.o: In function
>>> `intel_xpo
On 17.09.2018 [13:33:15 +0200], Peter Zijlstra wrote:
> On Fri, Sep 14, 2018 at 06:25:44PM +0200, Jan H. Schönherr wrote:
> > On 09/14/2018 01:12 PM, Peter Zijlstra wrote:
> > > On Fri, Sep 07, 2018 at 11:39:47PM +0200, Jan H. Schönherr wrote:
>
> > >> B) Why would I want this?
> > >
> > >>In
On Fri, Nov 02, 2018 at 01:00:00PM -0700, Paul E. McKenney wrote:
[..]
> > I think it would make sense also to combine it with other memory-ordering
> > topics like the memory model and rseq/cpu-opv things that Mathieu was doing
> > (if it makes sense to combine). But yes, I am definitely interest
On Mon 2018-09-10 13:26:52, Lubomir Rintel wrote:
> Let's defer the FIFO status checking until open().
>
> When we'll get a clk handle, this will allow us to defer clock enablement
> until the device is actually used.
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
--
(english) http
On Wed 2018-10-10 19:22:47, Lubomir Rintel wrote:
> It doesn't make sense to always have this built-in, e.g. on ARM
> multiplatform kernels. A better way to address the problem the original
> commit aimed to solve is to fix Kconfig.
>
> This reverts commit f48d1496b8537d75776478c6942dd87f34d7f270.
On Wed 2018-10-10 19:22:46, Lubomir Rintel wrote:
> According to [1] and [2], the temperature values are in tenths of degree
> Celsius. Exposing the Celsius value makes the battery appear on fire:
>
> $ upower -i /org/freedesktop/UPower/devices/battery_olpc_battery
> ...
> temperature:
On Mon 2018-09-10 14:13:14, Lubomir Rintel wrote:
> The MMP2 platform uses the PJ4 CPU. The cpu_is_mmp2() macro is thus
> actually not useful at all and moreover gives the wrong result on
> MACH_MMP2_DT.
>
> The actual problem I aim to fix is that on a device-tree enabled system,
> the timer ends
On Mon 2018-09-17 13:07:36, Lubomir Rintel wrote:
> There's apparently four of them on a MMP2.
>
> Changes since v1:
> - The controllers seem to be on AXI bus, not APB. Move them.
> - Remove aliases.
>
> Cc: Eric Miao
> Cc: Haojian Zhuang
> Cc: Rob Herring
> Cc: Mark Rutland
> Signed-off-by:
On Mon 2018-09-10 14:04:25, Lubomir Rintel wrote:
> On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71
> and 72 interrupts. Don't reset the "route to SP" bit (4).
>
> I'm just assuming the bit 4 is the "route to SP" bit -- it fixes the
> SP-based keyboard for me and defines
On 11/2/18 11:16 PM, Daniel Mentz wrote:
> On Fri, Nov 2, 2018 at 1:55 PM Alexey Skidanov
> wrote:
>>
>>
>>
>> On 11/2/18 9:17 PM, Daniel Mentz wrote:
>>> On Thu, Nov 1, 2018 at 10:07 AM Alexey Skidanov
>>> wrote:
On 11/1/18 18:48, Stephen Bates wrote:
>>I use gen_pool_first_fit_
Στις 2018-11-02 23:14, Atish Patra έγραψε:
On 11/2/18 11:59 AM, Nick Kossifidis wrote:
Hello All,
Στις 2018-11-02 01:04, Atish Patra έγραψε:
This patch series adds the cpu topology for RISC-V. It contains
both the DT binding and actual source code. It has been tested on
QEMU & Unleashed board.
clps711x_fb_probe() increments refcnt of disp device node by
of_parse_phandle() and leaves it undecremented on both
successful and error paths.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/video/fbdev/clps711x-fb.c | 5 -
1 fil
On Fri, Nov 02, 2018 at 03:14:29PM -0700, Joel Fernandes wrote:
> On Fri, Nov 02, 2018 at 01:00:00PM -0700, Paul E. McKenney wrote:
> [..]
> > > I think it would make sense also to combine it with other memory-ordering
> > > topics like the memory model and rseq/cpu-opv things that Mathieu was
>
On 11/2/18 12:50 PM, Waiman Long wrote:
> On 11/02/2018 03:44 PM, Dave Hansen wrote:
>> On 11/2/18 12:40 PM, Waiman Long wrote:
>>> The 64k+ limit check is kind of arbitrary. So the check is now removed
>>> to just let expand_stack() decide if a segmentation fault should happen.
>> With the 64k che
On Thu, Nov 01, 2018 at 04:22:55PM -0700, Andy Lutomirski wrote:
> On Thu, Nov 1, 2018 at 2:24 PM Linus Torvalds
> wrote:
> >
> > On Thu, Nov 1, 2018 at 12:31 PM Rich Felker wrote:
> > >
> > > See my other emails in this thread. You would register the *address*
> > > (in TLS) of a function pointe
On Fri, Nov 02, 2018 at 09:52:04AM -0700, Sean Christopherson wrote:
> On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
> > On 2018-11-02 09:30, Sean Christopherson wrote:
> > >... The intended convention for EENTER is to have an ENCLU at the AEX
> > >target ...
> > >
> > >... to fu
Hi Masahiro,
> The current SED_CONFIG_EXP could match to comment lines in config
> fragment files, especially when CONFIG_PREFIX_ is empty. For example,
> Buildroot uses empty prefixing; starting symbols with BR2_ is just
> convention.
> Make the sed expression more robust against false positives
Dmitry Vyukov wrote on Fri, Nov 02, 2018:
> >> I guess that's the problem, right? SIGKILL-ed task must not ignore
> >> SIGKILL and hang in infinite loop. This would explain a bunch of hangs
> >> in 9p.
> >
> > Did you check /proc/18253/task/*/stack after manually sending SIGKILL?
>
> Yes:
>
> roo
601 - 700 of 798 matches
Mail list logo
