The only reason s390 has ARCH_SELECT_MEMORY_MODEL option in
arch/s390/Kconfig is an ancient compile error with allnoconfig which was
fixed by commit 97195d6b411f ("[S390] fix sparsemem related compile error
with allnoconfig on s390") by adding the ARCH_SELECT_MEMORY_MODEL option.
Since then a lot
The ARCH_SELECT_MEMORY_MODEL option is enabled only for 64-bit. However,
64-bit configuration also enables ARCH_SPARSEMEM_DEFAULT and there is no
ARCH_FLATMEM_ENABLE in arch/sparc/Kconfig.
With such settings, the dependencies in mm/Kconfig are always evaluated to
SPARSEMEM=y for 64-bit and to
Currently, last stage boot loaders such as U-Boot can accept only
uImage which is an unnecessary additional step in automating boot flows.
Add a PE/COFF compliant image header that boot loaders can parse and
directly load kernel flat Image. The existing booting methods will continue
to work as it
Hi,
For several architectures the ARCH_SELECT_MEMORY_MODEL has no real effect
because the dependencies for the memory model are always evaluated to a
single value.
Remove the ARCH_SELECT_MEMORY_MODEL from the Kconfigs for these
architectures.
Mike Rapoport (3):
arm: remove
On Tue, 30 Apr 2019 20:24:33 -0600, Jeffrey Hugo wrote:
> The global clock controller on MSM8998 can consume a number of external
> clocks. Document them.
>
> Signed-off-by: Jeffrey Hugo
> ---
> Documentation/devicetree/bindings/clock/qcom,gcc.txt | 10 ++
> 1 file changed, 10
I2SE has been acquired, so i decided to use my private address now.
Signed-off-by: Stefan Wahren
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2c7d4e1..75a7876 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3068,7 +3068,7 @@
On Sat, Apr 27, 2019 at 2:14 AM wrote:
>
> From: Laurentiu Tudor
>
> Add a couple of new APIs to check the probing status of the required
> cpu bound qman and bman portals:
> 'int bman_portals_probed()' and 'int qman_portals_probed()'.
> They return the following values.
> * 1 if qman/bman
On Sat, Apr 27, 2019 at 11:04:55PM +0100, Dragan Cvetic wrote:
> Add the Soft Decision Forward Error Correction (SDFEC) Engine
> bindings which is available for the Zynq UltraScale+ RFSoC
> FPGA's.
>
> Signed-off-by: Dragan Cvetic
> Signed-off-by: Derek Kiernan
> ---
>
Rob,
On Fri, Apr 26, 2019 at 01:45:59PM -0500, Rob Herring wrote:
> On Mon, Apr 15, 2019 at 05:29:48PM -0400, Gaël PORTAY wrote:
> > diff --git a/include/dt-bindings/power/rk3399-dram.h
> > b/include/dt-bindings/power/rk3399-dram.h
> > new file mode 100644
> > index ..4b3d4a79923b
>
On Wed, May 1, 2019 at 12:17 PM Peter Zijlstra wrote:
>
> Something like so then?
Yes, that looks correct.
We have those X86_EFLAGS_VM tests pretty randomly scattered around,
and I wish there was some cleaner model for this, but I also guess
that there's no point in worrying about the 32-bit
On Tue, 30 Apr 2019 21:37:31 -0700, Bjorn Andersson wrote:
> Add binding for the QMP based side-channel communication mechanism to
> the AOSS, which is used to control resources not exposed through the
> RPMh interface.
>
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v6:
> - Added
On Wed, May 01, 2019 at 09:33:28PM +0200, Jiri Kosina wrote:
> On Wed, 1 May 2019, Steven Rostedt wrote:
>
> > I never tested the 32 bit version of this. And we could just not
> > implement it (I don't think there's live kernel patching for it
> > either).
>
> That's correct, there is no
On Wed, May 1, 2019 at 1:13 PM Nick Desaulniers wrote:
>
> On Tue, Apr 30, 2019 at 9:29 AM Nick Desaulniers
> wrote:
> >
> > On Tue, Apr 30, 2019 at 9:28 AM Nick Desaulniers
> > wrote:
> > > Thanks for the patch.
> > > Reported-by: Nick Desaulniers
> > > Link:
On Wed, 1 May 2019, Steven Rostedt wrote:
> I never tested the 32 bit version of this. And we could just not
> implement it (I don't think there's live kernel patching for it
> either).
That's correct, there is no livepatching on x86_32 (and no plans for
it). CONFIG_LIVEPATCH is not available
>From d228a1a119e33aff91f481fb8ab301a027b5a4ac Mon Sep 17 00:00:00 2001
From: Adam Michaelis
Date: Thu, 25 Apr 2019 15:22:00 -0500
Subject: [PATCH 2/6] dt-bindings: iio: ad7949: Add adi,reference-select
Adding optional parameter to AD7949 to specify the source for the
reference voltage signal.
On Wed, May 01, 2019 at 12:22:34PM -0700, Davidlohr Bueso wrote:
> On Wed, 01 May 2019, Peter Zijlstra wrote:
>
> > Nah, the percpu_rwsem abuse by the freezer is atrocious, we really
> > should not encourage that. Also, it completely wrecks -RT.
> >
> > Hence the proposed patch.
>
> Is this
On Wed, May 01, 2019 at 02:38:51PM -0400, Jerome Glisse wrote:
> Andrew just the patch that would be nice to get in 5.2 so i can fix
> device driver Kconfig before doing the real update to mm HMM Kconfig
>
> On Wed, Apr 17, 2019 at 05:11:41PM -0400, jgli...@redhat.com wrote:
> > From: Jérôme
On Wed, 01 May 2019, Peter Zijlstra wrote:
Nah, the percpu_rwsem abuse by the freezer is atrocious, we really
should not encourage that. Also, it completely wrecks -RT.
Hence the proposed patch.
Is this patch (and removing rcuwait) only intended for rt?
Thanks,
Davidlohr
The oobregion->offset for large page nand parts was wrong, change
fixes this error in calculation.
Fixes: ef5eeea6e911 ("mtd: nand: brcm: switch to mtd_ooblayout_ops")
Signed-off-by: Kamal Dasu
---
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Wed, May 01, 2019 at 11:59:05AM -0700, Linus Torvalds wrote:
> On Wed, May 1, 2019 at 11:52 AM Steven Rostedt wrote:
> >
> > I got Peter's patch working. Here it is. What do you think?
>
> I can tell from just looking at it for five seconds that at least the
> 32-bit case is buggy.
>
> You
On Wed, 1 May 2019 12:12:13 -0700
"Paul E. McKenney" wrote:
> OK, what I did was to apply the patch at the end of this email to -rcu
> branch dev, then run rcutorture as follows:
>
> nohup tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 8 --duration 2
> --configs "TRIVIAL" --bootargs
>
On Wed, May 1, 2019 at 2:35 PM Florian Fainelli wrote:
>
> On 4/26/19 12:22 PM, Kamal Dasu wrote:
> > The oobregion->offset for large page nand parts was wrong, change
> > fixes this error in calculation.
>
> Should this have a Fixes tag so this can be backported to stable trees
> seemingly
On Wed, May 01, 2019 at 12:03:52PM -0700, Linus Torvalds wrote:
> On Wed, May 1, 2019 at 6:11 AM Peter Zijlstra wrote:
> >
> > Here goes, compile tested only...
>
> Ugh, two different threads. This has the same bug (same source) as the
> one Steven posted:
This is what Steve started from; lets
On Wed, 1 May 2019 12:03:52 -0700
Linus Torvalds wrote:
> On Wed, May 1, 2019 at 6:11 AM Peter Zijlstra wrote:
> >
> > Here goes, compile tested only...
>
> Ugh, two different threads. This has the same bug (same source) as the
> one Steven posted:
>
> > --- a/arch/x86/entry/entry_32.S
> >
On Tue, Apr 30, 2019 at 01:55:51PM +0200, Peter Zijlstra wrote:
> On Tue, Apr 30, 2019 at 03:51:30AM -0700, Paul E. McKenney wrote:
> > > Then I'm not entirely sure how we can return 0 and not run on the
> > > expected CPU. If we look at __set_cpus_allowed_ptr(), the only paths out
> > > to 0 are:
Hi -
This patch triggered an oops for me (more below).
On 2/12/19 4:53 AM, Michal Hocko wrote:
[snip]
Fix the issue by reworking how x86 initializes the memory less nodes.
The current implementation is hacked into the workflow and it doesn't
allow any flexibility. There is
On Wed, May 1, 2019 at 6:11 AM Peter Zijlstra wrote:
>
> Here goes, compile tested only...
Ugh, two different threads. This has the same bug (same source) as the
one Steven posted:
> --- a/arch/x86/entry/entry_32.S
> +++ b/arch/x86/entry/entry_32.S
> @@ -1479,6 +1479,13 @@ ENTRY(int3)
>
On Wed, May 1, 2019 at 11:52 AM Steven Rostedt wrote:
>
> I got Peter's patch working. Here it is. What do you think?
I can tell from just looking at it for five seconds that at least the
32-bit case is buggy.
You can't look at CS(%rsp) without first also checking that you're not
coming from
On Wed, May 01, 2019 at 02:58:24PM -0400, Steven Rostedt wrote:
> > + if (ftrace_location(ip)) {
> > + int3_emulate_call(regs, ftrace_update_func_call);
>
> Should be:
>
> int3_emulate_call(regs, (unsigned long)ftrace_regs_caller);
Ah, I lost the plot a little there.
8187] CPU: 0 PID: 1 Comm: swapper Not tainted
5.1.0-rc7-next-20190501-dirty #31
|[1.276234] Hardware name: Generic AM33XX (Flattened Device Tree)
|[1.282510] PC is at sysc_probe+0xb80/0xfc0
|[1.286805] LR is at sysc_probe+0xb40/0xfc0
|[1.291100] pc : []lr : []psr: 6013
|[
On Mon, Mar 11, 2019 at 12:32 PM Roy Pledge wrote:
>
> From: Youri Querry
>
> The timeout for QBMan Management Commands can falsely trigger on a
> busy system. This patch doubles the timeout to avoid the
> false error reports
>
> Signed-off-by: Youri Querry
> Signed-off-by: Roy Pledge
Applied
On Wed, 1 May 2019 20:57:26 +0200
Peter Zijlstra wrote:
> On Wed, May 01, 2019 at 11:01:07AM -0700, Linus Torvalds wrote:
> > This looks sane to me, although I'm surprised that we didn't already
> > have an annotation for the nonstandard stack frame for asm files. That
> > probably would be
On Wed, 1 May 2019 15:11:17 +0200
Peter Zijlstra wrote:
> On Tue, Apr 30, 2019 at 11:33:21AM -0700, Linus Torvalds wrote:
> > Anyway, since Andy really likes the entry code change, can we have
> > that patch in parallel and judge the difference that way? Iirc, that
> > was x86-64 specific too.
On Wed, May 01, 2019 at 11:01:07AM -0700, Linus Torvalds wrote:
> This looks sane to me, although I'm surprised that we didn't already
> have an annotation for the nonstandard stack frame for asm files. That
> probably would be cleaner in a separate commit, but I guess it doesn't
> matter.
>
>
On Wed, May 01, 2019 at 01:26:08PM -0400, Waiman Long wrote:
> On 5/1/19 1:09 PM, Peter Zijlstra wrote:
> > On Tue, Apr 30, 2019 at 03:28:11PM +0200, Peter Zijlstra wrote:
> >
> >> Yeah, but AFAIK fs freezing code has a history of doing exactly that..
> >> This is just the latest incarnation here.
On Wed, 1 May 2019 11:01:07 -0700
Linus Torvalds wrote:
> This looks sane to me, although I'm surprised that we didn't already
> have an annotation for the nonstandard stack frame for asm files. That
> probably would be cleaner in a separate commit, but I guess it doesn't
> matter.
It's still
On 2019-05-01 02:49, Sudeep Holla wrote:
On Tue, Apr 30, 2019 at 05:07:31PM -0700, Sodagudi Prasad wrote:
On 2019-04-30 14:44, Sodagudi Prasad wrote:
+Sudeep
> Hi Mark/Will,
>
> I would like to understand whether ARM linux community have plans to
> support PSCI version 1.1 or not.
> PSCI_1_1
We're trying to use memory.high to limit workloads, but have found that
containment can frequently fail completely and cause OOM situations
outside of the cgroup. This happens especially with swap space -- either
when none is configured, or swap is full. These failures often also
don't have enough
Andrew just the patch that would be nice to get in 5.2 so i can fix
device driver Kconfig before doing the real update to mm HMM Kconfig
On Wed, Apr 17, 2019 at 05:11:41PM -0400, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> This patch just add 2 new Kconfig that are _not use_ by anyone.
Thanks for trying the fix.
So here is my analysis:
Let's start with epoll_pwait:
ep_poll() is what checks for signal_pending() and is responsible for
setting errno to -EINTR when there is a signal.
So if a signal is received after ep_poll(), it is never noticed by the
syscall during execution.
On 4/26/19 12:22 PM, Kamal Dasu wrote:
> The oobregion->offset for large page nand parts was wrong, change
> fixes this error in calculation.
Should this have a Fixes tag so this can be backported to stable trees
seemingly automatically? Thanks!
>
> Signed-off-by: Kamal Dasu
> ---
>
On Wed, May 1, 2019 at 9:07 AM Christoph Hellwig wrote:
>
> Casting mapping->a_ops->readpage to filler_t causes an indirect call
> type mismatch with Control-Flow Integrity checking. This change fixes
> the mismatch in read_cache_page_gfp and read_mapping_page by adding
> using a NULL filler
The DT schema tools are moving from my personal GH repo to the
devicetree.org group on GH. The new location is here:
https://github.com/devicetree-org/dt-schema.git
The old repo will be kept as a mirror.
Signed-off-by: Rob Herring
---
Documentation/devicetree/writing-schema.md | 2 +-
1 file
On Tue, Apr 30, 2019 at 9:29 AM Nick Desaulniers
wrote:
>
> On Tue, Apr 30, 2019 at 9:28 AM Nick Desaulniers
> wrote:
> > Thanks for the patch.
> > Reported-by: Nick Desaulniers
> > Link: https://github.com/ClangBuiltLinux/linux/issues/460
> > Suggested-by: David Laight
>
> sent too soon...
>
This looks sane to me, although I'm surprised that we didn't already
have an annotation for the nonstandard stack frame for asm files. That
probably would be cleaner in a separate commit, but I guess it doesn't
matter.
Anyway, I'm willing to consider the entry code version if it looks a
_lot_
--
Dear Friend.
My name is:Maki Tangza, a banker in one of the banks in my country
Burkina Faso in African.I Hoped that you will not expose or betray
this trust and confident that I am about to repose on you for the
mutual benefit of our both families.I need your urgent assistance in
> On May 1, 2019, at 10:40, Andy Lutomirski wrote:
>
> On Wed, May 1, 2019 at 6:52 AM Bae, Chang Seok
> wrote:
>>
>>
>>> On Apr 5, 2019, at 06:50, Andy Lutomirski wrote:
>>>
>>>
>>>
On Apr 5, 2019, at 2:35 AM, Thomas Gleixner wrote:
> On Mon, 25 Mar 2019, Thomas Gleixner
There is a race condition between resetting the SDHCI controller and
disconnecting the card.
For example:
0) Card is connected and transferring data
1) mmc_sd_reset is called to reset the controller due to a data error
2) sdhci_set_ios calls sdhci_do_reset
3) SOFT_RESET_ALL is toggled which
AMD SDHC 0x7906 requires a hard reset to clear all internal state.
Otherwise it can get into a bad state where the DATA lines are always
read as zeros.
This change requires firmware that can transition the device into
D3Cold for it to work correctly. If the firmware does not support
transitioning
If mtd_oops is in progress switch to polling for nand command completion
interrupts and use PIO mode wihtout DMA so that the mtd_oops buffer can
be completely written in the assinged nand partition. This is needed in
cases where the panic does not happen on cpu0 and there is only one online
CPU
On Tue, Apr 23, 2019 at 6:42 AM Yinbo Zhu wrote:
>
> From: Ashish Kumar
>
> This patch is to add esdhc node and enable SD UHS-I,
> eMMC HS200 for ls1028ardb/ls1028aqds board.
>
> Signed-off-by: Ashish Kumar
> Signed-off-by: Yangbo Lu
> Signed-off-by: Yinbo Zhu
> ---
>
Greeting, Did you received my message? please let me know.Thanks.Mr.Peter Sina.
From: Dalit Ben Zoor
Where there is a spike in the CPU consumption, it may cause
random failures in the C/I since the KMD timeout for CPU
and/or QMAN0 jobs expires and it stops communicating to the simulator.
This commit fixes it by increasing timeout on polling functions
if working with
From: Dalit Ben Zoor
After removing the parsing of the command submission
when doing memset of the device memory, goya_validate_dma_pkt_host
is never called by the kernel, so there is no need to check
context id.
Signed-off-by: Dalit Ben Zoor
Signed-off-by: Oded Gabbay
---
From: Dalit Ben Zoor
use_virt_addr member was used for telling whether to treat the
addresses in the CB as virtual during parsing. We disabled it only
when calling the parser from the driver memset device function,
and since this call had been removed, it should always be enabled.
g+CONFIG_SMP=n" and my earlyprintk vanished.
> So with this added:
> |[0.00] Booting Linux on physical CPU 0x0
> |[0.00] Linux version 5.1.0-rc7-next-20190501 (bigeasy@flow) (gcc
> version 8.3.0 (Debian 8.3.0-7)) #29 Wed May 1 18:55:24 CEST 2019
> |[0.00] CPU: A
On Wed, May 1, 2019 at 6:52 AM Bae, Chang Seok wrote:
>
>
> > On Apr 5, 2019, at 06:50, Andy Lutomirski wrote:
> >
> >
> >
> >> On Apr 5, 2019, at 2:35 AM, Thomas Gleixner wrote:
> >>
> >>> On Mon, 25 Mar 2019, Thomas Gleixner wrote:
> On Fri, 15 Mar 2019, Chang S. Bae wrote:
>
On Wed, May 01, 2019 at 10:41:52PM +0530, Anup Patel wrote:
> On Wed, May 1, 2019 at 10:30 PM Mark Rutland wrote:
> >
> > On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote:
> > > On 4/29/19 4:40 PM, Palmer Dabbelt wrote:
> > > > On Tue, 23 Apr 2019 16:25:06 PDT (-0700),
Fix the callback 9p passes to read_cache_page to actually have the
proper type expected. Casting around function pointers can easily
hide typing bugs, and defeats control flow protection.
Signed-off-by: Christoph Hellwig
---
fs/9p/vfs_addr.c | 6 --
1 file changed, 4 insertions(+), 2
On 5/1/19 10:02 AM, Anup Patel wrote:
On Wed, May 1, 2019 at 10:14 PM Karsten Merker wrote:
On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote:
On 4/29/19 4:40 PM, Palmer Dabbelt wrote:
On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.pa...@wdc.com wrote:
Currently, last stage boot
Dear RT folks!
I'm pleased to announce the v5.0.10-rt7 patch set.
Changes since v5.0.10-rt6:
- Two FPU related patches for x86 which were merged upstream (after
the "x86: load FPU registers on return to userland" series has been
applied).
- Rename rwsem_rt.h -> rwsem-rt.h for
Em Wed, May 01, 2019 at 05:09:59PM +0300, Thomas Backlund escreveu:
>
> Den 01-05-2019 kl. 16:07, skrev Arnaldo Carvalho de Melo:
> > Em Tue, Apr 30, 2019 at 04:31:14PM +0300, Thomas Backlund escreveu:
> > Can you check the output for
> >
On 5/1/19 1:09 PM, Peter Zijlstra wrote:
> On Tue, Apr 30, 2019 at 03:28:11PM +0200, Peter Zijlstra wrote:
>
>> Yeah, but AFAIK fs freezing code has a history of doing exactly that..
>> This is just the latest incarnation here.
>>
>> So the immediate problem here is that the task doing thaw isn't
On Wed, May 01, 2019 at 09:44:52AM -0700, Guenter Roeck wrote:
> On Tue, Apr 30, 2019 at 01:37:51PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.0.11 release.
> > There are 89 patches in this series, all will be posted as a response
> > to this one.
On Wed, 2019-05-01 at 16:25 +0200, Alexandre Belloni wrote:
> On 30/04/2019 22:31:19+, Trent Piepho wrote:
> > On Tue, 2019-04-30 at 22:18 +0200, Alexandre Belloni wrote:
> > > The RTC core already ensures the alarm is set to a time in the future, it
> > > is not necessary to check again in
On Wed, May 1, 2019 at 10:30 PM Mark Rutland wrote:
>
> On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote:
> > On 4/29/19 4:40 PM, Palmer Dabbelt wrote:
> > > On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.pa...@wdc.com wrote:
> > > > Currently, last stage boot loaders such as U-Boot
On Tue, Apr 30, 2019 at 03:28:11PM +0200, Peter Zijlstra wrote:
> Yeah, but AFAIK fs freezing code has a history of doing exactly that..
> This is just the latest incarnation here.
>
> So the immediate problem here is that the task doing thaw isn't the same
> that did freeze, right? The thing
Hi Enric,
Are these two patches an acceptable use of sysfs? There were concerns
earlier about abusing sysfs, but I think that these two uses follow
other sysfs use-cases well.
Thanks,
Nick
Quoting Anson Huang (2019-05-01 02:33:46)
> Hi, Stephen
> I saw Gustavo already sent out a patch to fix these two warnings, so
> I will NOT sent the patch again, thanks.
So I will apply that patch instead? Can you send your reviewed-by tag
then?
On Wed, May 1, 2019 at 10:14 PM Karsten Merker wrote:
>
> On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote:
> > On 4/29/19 4:40 PM, Palmer Dabbelt wrote:
> > > On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.pa...@wdc.com wrote:
> > > > Currently, last stage boot loaders such as U-Boot
he console remains dark.
>
> OK. Can you please email me your .config and the kernel cmdline you're
> using? I'll try to reproduce that one here.
This is "multi_v7_defconfig+CONFIG_SMP=n" and my earlyprintk vanished.
So with this added:
|[0.00] Booting Linux on phy
On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote:
> On 4/29/19 4:40 PM, Palmer Dabbelt wrote:
> > On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.pa...@wdc.com wrote:
> > > Currently, last stage boot loaders such as U-Boot can accept only
> > > uImage which is an unnecessary additional
Commit 0e7df22401a3 ("PCI: Add sysfs sriov_drivers_autoprobe to control
VF driver binding") allows the user to specify that drivers for VFs of
a PF should not be probed, but it actually causes pci_device_probe() to
return success back to the driver core in this case. Therefore by all
sysfs
On Wed, May 1, 2019 at 9:07 AM Christoph Hellwig wrote:
>
> Casting mapping->a_ops->readpage to filler_t causes an indirect call
> type mismatch with Control-Flow Integrity checking. This change fixes
> the mismatch in read_cache_page_gfp and read_mapping_page by adding
> using a NULL filler
On Wed 01 May 07:25 PDT 2019, Jeffrey Hugo wrote:
> On 4/30/2019 9:43 PM, Bjorn Andersson wrote:
> > On Tue 30 Apr 19:27 PDT 2019, Jeffrey Hugo wrote:
> > > +static const struct of_device_id mmcc_msm8998_match_table[] = {
> > > + { .compatible = "qcom,mmcc-msm8998" },
> > > + { }
> > > +};
> > >
w.
> >
> > Adding Kevin to Cc, he just confirmed on #armlinux irc that he is able to
> > reproduce this with CONFIG_SMP=n and root=/dev/ram0. I could not reproduce
> > this issue so far on omap3 with NFSroot at least.
>
> So that problem remains even that the job for toda
don't understand why this pops up now.
>
> Adding Kevin to Cc, he just confirmed on #armlinux irc that he is able to
> reproduce this with CONFIG_SMP=n and root=/dev/ram0. I could not reproduce
> this issue so far on omap3 with NFSroot at least.
So that problem remains even that the job fo
On Tue, Apr 30, 2019 at 01:37:29PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.38 release.
> There are 100 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
On Tue, Apr 30, 2019 at 01:37:51PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.0.11 release.
> There are 89 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
On Mon, Apr 29, 2019 at 10:42:40PM -0700, Atish Patra wrote:
> On 4/29/19 4:40 PM, Palmer Dabbelt wrote:
> > On Tue, 23 Apr 2019 16:25:06 PDT (-0700), atish.pa...@wdc.com wrote:
> > > Currently, last stage boot loaders such as U-Boot can accept only
> > > uImage which is an unnecessary additional
On 5/1/19 4:02 AM, Robin Murphy wrote:
> On 01/05/2019 11:47, Mark Rutland wrote:
>> On Tue, Apr 30, 2019 at 03:38:31PM -0700, Florian Fainelli wrote:
>>> Similar to commits c68b0274fb3cf ("ARM: reduce "Booted secondary
>>> processor" message to debug level") and 035e787543de7 ("ARM: 8644/1:
>>>
On Tue, Apr 30, 2019 at 01:38:07PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.115 release.
> There are 53 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
On Tue, Apr 30, 2019 at 01:38:11PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.172 release.
> There are 41 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
On Mon, Apr 29, 2019 at 7:52 AM Jan Glauber wrote:
>
> It turned out the issue we have on ThunderX2 is the file open-close sequence
> with small read sizes. If the used files are opened read-only the
> lockref code (enabled by ARCH_USE_CMPXCHG_LOCKREF) is used.
>
> The lockref CMPXCHG_LOOP uses
Hi Enric and Sebastian,
I sent out a v8 to address Enric's nits:
https://lore.kernel.org/patchwork/patch/1065815/
Thanks,
Nick
On 01 May 2019 10:04, Logesh Kolandavel wrote:
> From: Logesh
>
> If the da7213 codec is configured as Master with the DAPM power down
> delay time set, 'snd_soc_component_write' function overwrites the
> DAI_CLK_EN bit of DAI_CLK_MODE register which leads to audio play
> only once until it
since a week or two so I don't understand why this pops up now.
Adding Kevin to Cc, he just confirmed on #armlinux irc that he is able to
reproduce this with CONFIG_SMP=n and root=/dev/ram0. I could not reproduce
this issue so far on omap3 with NFSroot at least.
> I just revived my BBB and I can boot t
On Wed, May 01, 2019 at 06:13:30PM +0200, Oleg Nesterov wrote:
> On 04/30, Sudeep Holla wrote:
> >
> > While the TIF_SYSCALL_EMU is set in ptrace_resume independent of any
> > architecture, currently only powerpc and x86 unset the TIF_SYSCALL_EMU
> > flag in ptrace_disable which gets called from
On Wed, Apr 24, 2019 at 09:23:43PM +0200, Eugeniu Rosca wrote:
> From: Suresh Udipi
>
> It looks like v4.18-rc1 commit [0] which upstreams mld-1.8.0
> commit [1] missed to fix the memory leak in mod_exit function.
>
> Do it now.
>
> [0] aba258b7310167 ("staging: most: cdev: fix chrdev_region
On 04/30, Sudeep Holla wrote:
>
> While the TIF_SYSCALL_EMU is set in ptrace_resume independent of any
> architecture, currently only powerpc and x86 unset the TIF_SYSCALL_EMU
> flag in ptrace_disable which gets called from ptrace_detach.
>
> Let's move the clearing of TIF_SYSCALL_EMU flag to
On 04/30, Sudeep Holla wrote:
>
> The usage of emulated/_TIF_SYSCALL_EMU flags in syscall_trace_enter
> seems to be bit overcomplicated than required. Let's simplify it.
>
> Cc: Andy Lutomirski
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: Borislav Petkov
> Signed-off-by: Sudeep Holla
On Wed, May 01, 2019 at 10:57:23AM -0500, Pierre-Louis Bossart wrote:
> SoundWire support will be provided in Linux with the Sound Open
> Firmware (SOF) on Intel platforms. Before we start adding the missing
> pieces, there are a number of warnings and style issues reported by
> checkpatch,
Casting mapping->a_ops->readpage to filler_t causes an indirect call
type mismatch with Control-Flow Integrity checking. This change fixes
the mismatch in read_cache_page_gfp and read_mapping_page by adding
using a NULL filler argument as an indication to call ->readpage
directly, and by passing
On 5/1/19 3:47 AM, Mark Rutland wrote:
> On Tue, Apr 30, 2019 at 03:38:31PM -0700, Florian Fainelli wrote:
>> Similar to commits c68b0274fb3cf ("ARM: reduce "Booted secondary
>> processor" message to debug level") and 035e787543de7 ("ARM: 8644/1: Reduce
>> "CPU:
>> shutdown" message to debug
Fix the callback jffs2 passes to read_cache_page to actually have the
proper type expected. Casting around function pointers can easily
hide typing bugs, and defeats control flow protection.
Signed-off-by: Christoph Hellwig
---
fs/jffs2/file.c | 4 ++--
fs/jffs2/fs.c | 2 +-
We can just pass a NULL filler and do the right thing inside of
do_read_cache_page based on the NULL parameter.
Signed-off-by: Christoph Hellwig
---
include/linux/pagemap.h | 3 +--
mm/filemap.c| 10 ++
2 files changed, 7 insertions(+), 6 deletions(-)
diff --git
Fix the callbacks NFS passes to read_cache_page to actually have the
proper type expected. Casting around function pointers can easily
hide typing bugs, and defeats control flow protection.
Signed-off-by: Christoph Hellwig
---
fs/nfs/dir.c | 7 ---
fs/nfs/symlink.c | 7 ---
2 files
Signed-off-by: Christoph Hellwig
---
mm/filemap.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index d78f577baef2..a2fc59f56f50 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -2956,7 +2956,8 @@ struct page *read_cache_page(struct
On Wed, May 01, 2019 at 10:57:25AM -0500, Pierre-Louis Bossart wrote:
> No C++ comments in .h files
That's not really the issue here.
>
> Reviewed-by: Takashi Iwai
> Signed-off-by: Pierre-Louis Bossart
> ---
> drivers/soundwire/bus.h| 4 ++--
> drivers/soundwire/cadence_master.h
Hi Jan,
[+Peter and Linus, since they enjoy this stuff]
On Mon, Apr 29, 2019 at 02:52:11PM +, Jan Glauber wrote:
> I've been looking into performance issues that were reported for several
> test-cases, for instance an nginx benchmark.
Could you share enough specifics here so that we can
201 - 300 of 465 matches
Mail list logo
