On Fri, 10 May 2019 14:56:29 +0200,
Pierre-Louis Bossart wrote:
>
> On 5/10/19 2:12 AM, Takashi Iwai wrote:
> > On Fri, 10 May 2019 04:36:57 +0200,
> > YueHaibing wrote:
> >>
> >> Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
> >>
> >> sound/soc/sof/core.o: In function `snd_sof_device_pro
On 2019/5/10 15:12, Takashi Iwai wrote:
> On Fri, 10 May 2019 04:36:57 +0200,
> YueHaibing wrote:
>>
>> Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
>>
>> sound/soc/sof/core.o: In function `snd_sof_device_probe':
>> core.c:(.text+0x4af): undefined reference to `sof_nocodec_setup'
>>
>> Ch
From: Colin Ian King
Don't populate the array template on the stack but instead make it
static. Makes the object code smaller by 10 bytes. Also reformat
the declaration.
Before:
textdata bss dec hex filename
293769360 128 3886497d0 drivers/hid/hid-logitech-dj.
Hi Rob,
On 5/8/19 10:35 PM, Rob Herring wrote:
> On Wed, May 8, 2019 at 4:45 AM Lukasz Luba wrote:
>>
>>
>> On 5/8/19 9:19 AM, Krzysztof Kozlowski wrote:
>>> On Tue, 7 May 2019 at 19:04, Rob Herring wrote:
> +- devfreq-events : phandles of the PPMU events used by the controller.
> +- sam
On Mon, Apr 29, 2019 at 11:36:22AM +0800, Aaron Lu wrote:
> On Tue, Apr 23, 2019 at 04:18:16PM +, Vineeth Remanan Pillai wrote:
> > +/*
> > + * l(a,b)
> > + * le(a,b) := !l(b,a)
> > + * g(a,b) := l(b,a)
> > + * ge(a,b) := !l(a,b)
> > + */
> > +
> > +/* real prio, less is less */
> > +static in
This reverts commit c17e9377aa81664d94b4f2102559fcf2a01ec8e7.
The lpc32xx clock driver is not able to actually change the PLL rate as
this would require reparenting ARM_CLK, DDRAM_CLK, PERIPH_CLK to SYSCLK,
then stop the PLL, update the register, restart the PLL and wait for the
PLL to lock and fi
On 5/10/19 12:18 AM, YueHaibing wrote:
Fix gcc build error while CONFIG_REGULATOR is not set
drivers/power/supply/ucs1002_power.o: In function `ucs1002_probe':
drivers/power/supply/ucs1002_power.c:593: undefined reference to
`devm_regulator_register'
drivers/power/supply/ucs1002_power.o:(.rodat
On 10/05/2019 13:29, Amit Kucheria wrote:
> Add device bindings for cpuidle states for cpu devices.
>
> Cc: Marc Gonzalez
> Signed-off-by: Amit Kucheria
> ---
> arch/arm64/boot/dts/qcom/msm8998.dtsi | 32 +++
> 1 file changed, 32 insertions(+)
>
> diff --git a/arch/arm
Hi Alexandre,
> This reverts commit c17e9377aa81664d94b4f2102559fcf2a01ec8e7.
>
> The lpc32xx clock driver is not able to actually change the PLL rate as
> this would require reparenting ARM_CLK, DDRAM_CLK, PERIPH_CLK to SYSCLK,
> then stop the PLL, update the register, restart the PLL and wait fo
Michael Kelley writes:
> From: Vitaly Kuznetsov Sent: Wednesday, May 8, 2019
> 7:55 AM
>> >>
>> >> Sorry, my bad: I meant to say "not cache-like" (these allocations are
>> >> not 'cache') but the typo made it completely incomprehensible.
>> >
>> > No worries! Thank you for sharing your thought
From: Colin Ian King
Don't populate the array consumer_rdesc_start on the stack but instead
make it static. Makes the object code smaller by 88 bytes.
Before:
textdata bss dec hex filename
591559840 448 69443 10f43 drivers/hid/hid-logitech-hidpp.o
After:
text
Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
sound/soc/sof/core.o: In function `snd_sof_device_probe':
core.c:(.text+0x4af): undefined reference to `sof_nocodec_setup'
Change IS_ENABLED to IS_REACHABLE to fix this.
Reported-by: Hulk Robot
Suggested-by: Takashi Iwai
Fixes: c16211d6226
On 2019-05-07 01:39, Dan Williams wrote:
Towards enabling memory hotplug to track partial population of a
section, introduce 'struct mem_section_usage'.
A pointer to a 'struct mem_section_usage' instance replaces the
existing
pointer to a 'pageblock_flags' bitmap. Effectively it adds one more
On 5/10/19 8:04 AM, Takashi Iwai wrote:
On Fri, 10 May 2019 14:56:29 +0200,
Pierre-Louis Bossart wrote:
On 5/10/19 2:12 AM, Takashi Iwai wrote:
On Fri, 10 May 2019 04:36:57 +0200,
YueHaibing wrote:
Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
sound/soc/sof/core.o: In function `snd
On 5/9/19 11:41 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.118 release.
There are 42 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
On 5/9/19 11:41 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.175 release.
There are 28 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
On 5/9/19 11:41 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.42 release.
There are 66 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
On 5/10/19 8:29 AM, YueHaibing wrote:
Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
sound/soc/sof/core.o: In function `snd_sof_device_probe':
core.c:(.text+0x4af): undefined reference to `sof_nocodec_setup'
Change IS_ENABLED to IS_REACHABLE to fix this.
this just hides the issue inst
On 5/9/19 11:41 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.15 release.
There are 95 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 b
Hello,
Some purely cosmetic suggestions below.
On Fri, 10 May 2019 15:41:02 +0800
Mason Yang wrote:
> + if (ret)
> + pr_err("set feature failed to read retry moded:%d\n", mode);
I don't know what is the policy in the MTD/NAND subsystem, but
shouldn't you be using dev_err() in
On Fri, 10 May 2019 15:34:03 +0200,
Pierre-Louis Bossart wrote:
>
> On 5/10/19 8:04 AM, Takashi Iwai wrote:
> > On Fri, 10 May 2019 14:56:29 +0200,
> > Pierre-Louis Bossart wrote:
> >>
> >> On 5/10/19 2:12 AM, Takashi Iwai wrote:
> >>> On Fri, 10 May 2019 04:36:57 +0200,
> >>> YueHaibing wrote:
>
On 10/05/19 7:06 PM, Guenter Roeck wrote:
> On 5/9/19 11:41 AM, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 5.0.15 release.
>> There are 95 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being app
Fix gcc build error while CONFIG_UIO is not set
ERROR: "uio_unregister_device" [drivers/staging/kpc2000/kpc2000/kpc2000.ko]
undefined!
ERROR: "__uio_register_device" [drivers/staging/kpc2000/kpc2000/kpc2000.ko]
undefined!
Add UIO Kconfig dependency to fix this.
Reported-by: Hulk Robot
Fixes:
Hi Mason,
Thomas Petazzoni wrote on Fri, 10 May
2019 15:37:04 +0200:
> Hello,
>
> Some purely cosmetic suggestions below.
>
> On Fri, 10 May 2019 15:41:02 +0800
> Mason Yang wrote:
>
> > + if (ret)
> > + pr_err("set feature failed to read retry moded:%d\n", mode);
>
> I don'
On Thu, May 9, 2019 at 4:06 PM Sedat Dilek wrote:
>
> On Thu, May 9, 2019 at 8:45 AM Masahiro Yamada
> wrote:
> >
> > We do not support old Clang versions. Upgrade your clang version
> > if any of these flags is unsupported.
> >
> > Let's add flags within ifdef CONFIG_CC_IS_CLANG unconditionally,
On Fri, 10 May 2019 15:41:10 +0200,
Takashi Iwai wrote:
>
> On Fri, 10 May 2019 15:34:03 +0200,
> Pierre-Louis Bossart wrote:
> >
> > On 5/10/19 8:04 AM, Takashi Iwai wrote:
> > > On Fri, 10 May 2019 14:56:29 +0200,
> > > Pierre-Louis Bossart wrote:
> > >>
> > >> On 5/10/19 2:12 AM, Takashi Iwai
On Thu, May 09, 2019 at 10:30:52PM -0700, Christoph Hellwig wrote:
> Also I don't see any reason why we'd need to do the freeze game on
> resume.
Right, definitely no reason for resume.
> Even on suspend it looks a little odd to me, as in theory
> the PM core should have already put the system
On Fri, May 10, 2019 at 01:23:11AM -0700, Rafael J. Wysocki wrote:
> On Fri, May 10, 2019 at 8:08 AM Kai-Heng Feng
> > I tested the patch from Keith and it has two issues just as simply skipping
> > nvme_dev_disable():
> > 1) It consumes more power in S2I
> > 2) System freeze after resume
>
> Well
On Thu, May 09, 2019 at 11:05:42PM -0700, Kai-Heng Feng wrote:
> Yes, that’ what I was told by the NVMe vendor, so all I know is to impose a
> memory barrier.
> If mb() shouldn’t be used here, what’s the correct variant to use in this
> context?
I'm afraid the requirement is still not clear to
We do not support old Clang versions. Upgrade your clang version
if any of these flags is unsupported.
Let's add all flags within ifdef CONFIG_CC_IS_CLANG unconditionally.
Signed-off-by: Masahiro Yamada
Reviewed-by: Sedat Dilek
Reviewed-by: Nathan Chancellor
Tested-by: Nick Desaulniers
---
C
On Wed 2019-05-08 19:31:06, Tetsuo Handa wrote:
> Hello.
>
> We are again getting corrupted reports where message from WARN() is missing.
> For example, https://syzkaller.appspot.com/text?tag=CrashLog&x=1720cac8a0
> was
> titled as "WARNING in cgroup_exit" because the
> "WARNING: CPU: 0 PID:
On Fri, May 10, 2019 at 6:45 PM Marc Gonzalez wrote:
>
> On 10/05/2019 13:29, Amit Kucheria wrote:
>
> > Add device bindings for cpuidle states for cpu devices.
> >
> > Cc: Marc Gonzalez
> > Signed-off-by: Amit Kucheria
> > ---
> > arch/arm64/boot/dts/qcom/msm8998.dtsi | 32
On Fri, May 10, 2019 at 08:50:52PM +1000, Michael Ellerman wrote:
> Yeah that looks better to me. I didn't think about the case where EDAC
> core is modular.
>
> Do you want me to send a new patch?
Nah, I'll fix it up.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid to
On Thu, 9 May 2019 23:54:46 +
Paul Burton wrote:
> Hi Thomas,
>
> On Wed, May 08, 2019 at 09:52:39AM +0200, Thomas Bogendoerfer wrote:
> > On Tue, 7 May 2019 23:18:15 -0700
> > Christoph Hellwig wrote:
> >
> > > On Tue, May 07, 2019 at 11:09:13PM +0200, Thomas Bogendoerfer wrote:
> > > > C
Hello,
Thomas Petazzoni wrote on Fri, 10 May
2019 15:37:04 +0200:
> Hello,
>
> Some purely cosmetic suggestions below.
>
> On Fri, 10 May 2019 15:41:02 +0800
> Mason Yang wrote:
>
> > + if (ret)
> > + pr_err("set feature failed to read retry moded:%d\n", mode);
>
> I don't k
On Tue, Apr 23, 2019 at 09:36:33AM -0500, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> This patch series adds EDAC support for the Stratix10 OCRAM
> and SDMMC peripherals.
>
> Thor Thayer (4):
> EDAC, altera: Add Stratix10 OCRAM ECC support
> arm64: dts: stratix10: Add OCRAM ED
Fix gcc build warning:
drivers/clocksource/timer-ixp4xx.c:78:20:
warning: 'ixp4xx_read_sched_clock' defined but not used [-Wunused-function]
Reported-by: Hulk Robot
Signed-off-by: YueHaibing
---
drivers/clocksource/timer-ixp4xx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/c
On 09/05/2019 23:03:40+0200, Alexandre Belloni wrote:
> Hello Linus,
>
> A huge series from me this cycle. I went through many drivers to set the
> date and time range supported by the RTC which helps solving HW
> limitation when the time comes (as early as next year for some). This
> time, I focu
Linus,
please pull one vsprintf fix from
git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk
tags/printk-for-5.2-fixes
=
- Replace the problematic probe_kernel_read() with original simple
pointer checks in vsprintf().
--
On 2019/05/10 23:12, Petr Mladek wrote:
> On Wed 2019-05-08 19:31:06, Tetsuo Handa wrote:
>> Hello.
>>
>> We are again getting corrupted reports where message from WARN() is missing.
>> For example,
>> https://syzkaller.appspot.com/text?tag=CrashLog&x=1720cac8a0 was
>> titled as "WARNING in cg
On Fri, 10 May 2019 14:17:20 +0200
Peter Zijlstra wrote:
> But both ftrace and retprobes are at C function call boundaries.
> Preserving flags doesn't make sense.
I agree, but I did it just because of my OCD and being complete in
"emulating an int3" for ftrace_regs_caller ;-)
Yeah, we can remov
This driver exposes a standard tty interface on top of the rpmsg
framework through the "rpmsg-tty-channel" rpmsg service.
This driver supports multi-instances, offering a /dev/ttyRPMSGx entry
per rpmsg endpoint.
Signed-off-by: Arnaud Pouliquen
Signed-off-by: Fabien Dessenne
---
Documentation/s
Return the rpmsg buffer payload size for sending message, so rpmsg users
can split a long message in several sub rpmsg buffers.
Signed-off-by: Arnaud Pouliquen
Signed-off-by: Fabien Dessenne
---
drivers/rpmsg/rpmsg_core.c | 20
drivers/rpmsg/rpmsg_internal.h | 2 ++
This patch set introduces a TTY console on top of the RPMsg framework which
enables the following use cases:
- Provide a console to communicate easily with the remote processor
application.
- Provide an interface to get the remote processor log traces without
ring buffer limitation.
- Ease the
On 10/05/2019 16:12, Amit Kucheria wrote:
On Fri, May 10, 2019 at 6:45 PM Marc Gonzalez wrote:
On 10/05/2019 13:29, Amit Kucheria wrote:
Add device bindings for cpuidle states for cpu devices.
Cc: Marc Gonzalez
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 32
** Contains fix for i386 build breakage **
Enjoy!
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
tags/ib-mfd-pinctrl-v5.2-1
On Fri, May 10, 2019 at 10:24:50PM +0800, Gen Zhang wrote:
> On Fri, May 10, 2019 at 13:14:02PM +0800, Greg KH <
> gre...@linuxfoundation.org> wrote:
> >Note, your email client ate all of the tabs and made the patch
> >impossible to apply, so please fix this up before you resend it.
> >
> >thanks,
On 05/09, Sultan Alsawaf wrote:
>
> On Thu, May 09, 2019 at 05:56:46PM +0200, Oleg Nesterov wrote:
> > Impossible ;) I bet lockdep should report the deadlock as soon as
> > find_victims()
> > calls find_lock_task_mm() when you already have a locked victim.
>
> I hope you're not a betting man ;)
I
On 23-Apr-2019 04:18:17 PM, Vineeth Remanan Pillai wrote:
> From: Peter Zijlstra (Intel)
>
> Marks all tasks in a cgroup as matching for core-scheduling.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> kernel/sched/core.c | 62
> kernel/sched/sch
Hi Robin,
> -Original Message-
> From: Robin Murphy
> Sent: Friday, May 10, 2019 6:04 PM
>
> Hi Laurentiu,
>
> On 10/05/2019 15:56, wrote:
> > From: Laurentiu Tudor
> >
> > For HCs that have local memory, replace the current DMA API usage
> > with a genalloc generic allocator to manag
> On May 10, 2019, at 4:23 PM, Rafael J. Wysocki wrote:
>
> On Fri, May 10, 2019 at 8:08 AM Kai-Heng Feng
> wrote:
>>
>> at 06:19, wrote:
>>
-Original Message-
From: Keith Busch
Sent: Thursday, May 9, 2019 4:54 PM
To: Limonciello, Mario
Cc: kai.heng.f...@
> On May 10, 2019, at 10:02 PM, Keith Busch wrote:
>
> On Thu, May 09, 2019 at 11:05:42PM -0700, Kai-Heng Feng wrote:
>> Yes, that’ what I was told by the NVMe vendor, so all I know is to impose a
>> memory barrier.
>> If mb() shouldn’t be used here, what’s the correct variant to use in this
Change of subject line to v2:
** Contains fix for i386 build breakage **
Enjoy!
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.
We are seeing syzbot reports [1] where printk() messages prior to panic()
are missing for unknown reason. To test whether it is due to some testcase
changing console loglevel, let's panic() as soon as console loglevel has
changed. This patch is intended for testing on linux-next.git only, and
will
All syscall_get_*() and syscall_set_*() functions must be defined
as static inline as on all other architectures, otherwise asm/syscall.h
cannot be included in more than one compilation unit.
This bug has to be fixed in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Check whether PTRACE_GET_SYSCALL_INFO semantics implemented in the kernel
matches userspace expectations.
Acked-by: Shuah Khan
Cc: Oleg Nesterov
Cc: Andy Lutomirski
Cc: Elvira Khabirova
Cc: Eugene Syromyatnikov
Cc: linux-kselft...@vger.kernel.org
Signed-off-by: Dmitry V. Levin
---
Notes:
From: Elvira Khabirova
PTRACE_GET_SYSCALL_INFO is a generic ptrace API that lets ptracer obtain
details of the syscall the tracee is blocked in.
There are two reasons for a special syscall-related ptrace request.
Firstly, with the current ptrace API there are cases when ptracer cannot
retrieve
The following changes since commit
d9defe448f4c7b88ca2ae636a321ef8970fa718d:
docs/livepatch: Unify style of livepatch documentation in the ReST format
(2019-05-07 16:06:28 -0600)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.2a
for you to fetch changes up
syscall_get_error() is required to be implemented on this
architecture in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Acked-by
On 5/10/19 8:56 AM, Takashi Iwai wrote:
On Fri, 10 May 2019 15:41:10 +0200,
Takashi Iwai wrote:
On Fri, 10 May 2019 15:34:03 +0200,
Pierre-Louis Bossart wrote:
On 5/10/19 8:04 AM, Takashi Iwai wrote:
On Fri, 10 May 2019 14:56:29 +0200,
Pierre-Louis Bossart wrote:
On 5/10/19 2:12 AM, Tak
syscall_get_error() is required to be implemented on all
architectures in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Acked-by
syscall_get_* functions are required to be implemented on all
architectures in order to extend the generic ptrace API with
PTRACE_GET_SYSCALL_INFO request.
This adds remaining 2 syscall_get_* functions as documented in
asm-generic/syscall.h: syscall_get_error and syscall_get_return_value.
Cc: Ric
syscall_get_error() is required to be implemented on all
architectures in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Acked-by
On 05/10, Christian Brauner wrote:
>
> @@ -2102,7 +2102,7 @@ static __latent_entropy struct task_struct
> *copy_process(
>*/
> retval = cgroup_can_fork(p);
> if (retval)
> - goto bad_fork_put_pidfd;
> + goto bad_fork_cgroup_threadgroup_change_end;
>
>
On 5/9/19 8:03 PM, Huang, Ying wrote:
Yang Shi writes:
On 5/9/19 7:12 PM, Huang, Ying wrote:
Yang Shi writes:
Since commit bd4c82c22c36 ("mm, THP, swap: delay splitting THP after
swapped out"), THP can be swapped out in a whole. But, nr_reclaimed
still gets inc'ed by one even though a
Hi Adam,
>>> This moves all remaining users of the legacy TI_ST driver to hcill
>>> (patches
>>> 1-3). Then patches 4-7 convert wl128x-radio driver to a standard
>>> platform
>>> device driver with support for multiple instances. Patch 7 will result
>>> in
>>> (userl
Hi Linus,
Gathered pile of patches for Platform Drivers x86. No surprises and no merge
conflicts. Business as usual.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are availabl
On Fri, May 10, 2019 at 11:15:05PM +0800, Kai Heng Feng wrote:
> Sorry, I should mention that I use a slightly modified
> drivers/nvme/host/pci.c:
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 3e4fb891a95a..ece428ce6876 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/d
On Fri, May 10, 2019 at 12:06:07PM +0530, Naresh Kamboju wrote:
> On Fri, 10 May 2019 at 00:21, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.0.15 release.
> > There are 95 patches in this series, all will be posted as a response
> > to this one. If an
Like order boards, order nodes by address then node names then aliases.
Signed-off-by: Jerome Brunet
---
.../boot/dts/amlogic/meson-g12a-sei510.dts| 92 +--
1 file changed, 46 insertions(+), 46 deletions(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a-sei510.dts
b/ar
Like order boards, order nodes by address then node names then aliases.
Signed-off-by: Jerome Brunet
---
.../boot/dts/amlogic/meson-g12a-u200.dts | 50 ++-
1 file changed, 26 insertions(+), 24 deletions(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a-u200.dts
b/arch
On Fri, May 10, 2019 at 11:18:52PM +0800, Kai Heng Feng wrote:
> > I'm afraid the requirement is still not clear to me. AFAIK, all our
> > barriers routines ensure data is visible either between CPUs, or between
> > CPU and devices. The CPU never accesses HMB memory, so there must be some
> > other
The order of the nodes in the u200 and sei510 is bit fancy.
Order nodes by address, then node name, then aliases.
This makes rebasing is little less painful
Jerome Brunet (2):
arm64: dts: meson: sei510: consistently order nodes
arm64: dts: meson: u200: consistently order nodes
.../boot/dts/
This patch adds 'DAXDEV_SYNC' flag which is set
for nd_region doing synchronous flush. This later
is used to disable MAP_SYNC functionality for
ext4 & xfs filesystem for devices don't support
synchronous flush.
Signed-off-by: Pankaj Gupta
---
drivers/dax/bus.c| 2 +-
drivers/dax/sup
This patch introduces 'daxdev_mapping_supported' helper
which checks if 'MAP_SYNC' is supported with filesystem
mapping. It also checks if corresponding dax_device is
synchronous. Virtio pmem device is asynchronous and
does not not support VM_SYNC.
Suggested-by: Jan Kara
Signed-off-by: Pankaj Gu
This patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information from
Qemu over VIRTIO and registers it on nvdimm_bus. It also
creates a nd_region object with the persistent memory
range information so that existing 'nvdimm/pmem' driver
can reserve this into sy
On Fri, May 10, 2019 at 07:13:43PM +0530, Vandana BN wrote:
>
> On 10/05/19 7:06 PM, Guenter Roeck wrote:
> > On 5/9/19 11:41 AM, Greg Kroah-Hartman wrote:
> >> This is the start of the stable review cycle for the 5.0.15 release.
> >> There are 95 patches in this series, all will be posted as a re
On 5/9/19 9:33 PM, William Kucharski wrote:
On May 9, 2019, at 9:03 PM, Huang, Ying wrote:
Yang Shi writes:
On 5/9/19 7:12 PM, Huang, Ying wrote:
How about to change this to
nr_reclaimed += hpage_nr_pages(page);
Either is fine to me. Is this faster than "1 << compound_order
Hi Niklas,
On Fri, May 10, 2019 at 01:36:08PM +0200, Niklas Söderlund wrote:
> Hi Eugeniu,
>
> On 2019-05-10 12:42:31 +0200, Eugeniu Rosca wrote:
> > Hi Niklas,
> >
> > On Wed, May 08, 2019 at 01:54:03AM +0200, Niklas Söderlund wrote:
> > > Hi Jiada,
> > [..]
> > > I really like this series, nic
On Thu, May 9, 2019 at 11:27 PM Hsin-Yi Wang wrote:
>
> On Wed, May 8, 2019 at 3:47 AM Rob Herring wrote:
>
> > > Documentation/devicetree/bindings/chosen.txt | 14 +
> >
> > Actually, this file has been converted to json-schema and lives
> > here[1]. I need to remove this one (or leave i
Hi,
On Thu, 2019-05-09 at 11:39 -0700, Eric Anholt wrote:
> Paul Kocialkowski writes:
>
> > The binner BO is not required until the V3D is in use, so avoid
> > allocating it at probe and do it on the first non-dumb BO allocation.
> >
> > Keep track of which clients are using the V3D and liberat
Convert the STM32 pinctrl binding to DT schema format using json-schema.
Signed-off-by: Alexandre Torgue
---
Hi,
First pacth to convert DT bindings file (here pinctrl STM32) to json-schema
in order to take advantage of devicetree validation tool for STM32.
Changes since v1:
- Fix errors repor
This patch adds functionality to perform flush from guest
to host over VIRTIO. We are registering a callback based
on 'nd_region' type. virtio_pmem driver requires this special
flush function. For rest of the region types we are registering
existing flush function. Report error returned by host fsy
On Fri, May 10, 2019 at 11:18:07AM +0100, Jon Hunter wrote:
>
> On 09/05/2019 19:42, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.1.1 release.
> > There are 30 patches in this series, all will be posted as a response
> > to this one. If anyone has any issue
Dont support 'MAP_SYNC' with non-DAX files and DAX files
with asynchronous dax_device. Virtio pmem provides
asynchronous host page cache flush mechanism. We don't
support 'MAP_SYNC' with virtio pmem and ext4.
Signed-off-by: Pankaj Gupta
Reviewed-by: Jan Kara
---
fs/ext4/file.c | 10 ++
Thanks for the review Enric!
I can resend the patch with the fixes, or if you think the fixes are
simple enough, you could tweak them as you apply them. Let
me know if you want me to resend a clean version.
> > +
> > +static DEVICE_ATTR_WO(boot_on_ac);
>
> Is not possible to read the flag? From t
On Thu, 14 Mar 2019, Paul Burton wrote:
> > @@ -66,7 +65,7 @@ need_resched:
> > andit0, 1
> > beqzt0, restore_all
> > jal preempt_schedule_irq
> > - b need_resched
> > + j restore_all
>
> One nit - why change from branch to jump? It's not a big deal, but I'
pt., 10 maj 2019 o 11:16 Bartosz Golaszewski napisał(a):
>
> śr., 8 maj 2019 o 09:13 Richard Weinberger napisał(a):
> >
> > - Ursprüngliche Mail -
> > >> Can you please check?
> > >> This patch is already queued in -next. So we need to decide whether to
> > >> revert or fix it now.
> > >>
On 08/05/2019 22:17, Tony Krowiak wrote:
On 5/2/19 1:34 PM, Pierre Morel wrote:
We register a AP PQAP instruction hook during the open
of the mediated device. And unregister it on release.
During the probe of the AP device, we allocate a vfio_ap_queue
structure to keep track of the information
On 10/05/2019 17:20, Bartosz Golaszewski wrote:
pt., 10 maj 2019 o 11:16 Bartosz Golaszewski napisał(a):
śr., 8 maj 2019 o 09:13 Richard Weinberger napisał(a):
- Ursprüngliche Mail -
Can you please check?
This patch is already queued in -next. So we need to decide whether to
revert
Hi,
On Fri, May 10, 2019 at 06:05:06AM -0700, Guenter Roeck wrote:
> On 5/10/19 12:18 AM, YueHaibing wrote:
> > Fix gcc build error while CONFIG_REGULATOR is not set
> >
> > drivers/power/supply/ucs1002_power.o: In function `ucs1002_probe':
> > drivers/power/supply/ucs1002_power.c:593: undefined
When a process signals the audit daemon (shutdown, rotate, resume,
reconfig) but syscall auditing is not enabled, we still want to know the
identity of the process sending the signal to the audit daemon.
Move audit_signal_info() out of syscall auditing to general auditing but
create a new function
On 5/10/19 8:50 AM, YueHaibing wrote:
On 2019/5/10 21:36, Pierre-Louis Bossart wrote:
On 5/10/19 8:29 AM, YueHaibing wrote:
Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
sound/soc/sof/core.o: In function `snd_sof_device_probe':
core.c:(.text+0x4af): undefined reference to `sof_noco
Since commit bd4c82c22c36 ("mm, THP, swap: delay splitting THP after
swapped out"), THP can be swapped out in a whole. But, nr_reclaimed
still gets inc'ed by one even though a whole THP (512 pages) gets
swapped out.
This doesn't make too much sense to memory reclaim. For example, direct
reclaim
On Fri, May 10, 2019 at 05:50:51PM +0200, Greg Kroah-Hartman wrote:
> On Fri, May 10, 2019 at 12:06:07PM +0530, Naresh Kamboju wrote:
> > On Fri, 10 May 2019 at 00:21, Greg Kroah-Hartman
> > wrote:
> > >
> > > This is the start of the stable review cycle for the 5.0.15 release.
> > > There are 95
On Fri, May 10, 2019 at 10:12:40AM +0800, Huang, Ying wrote:
> > + nr_reclaimed += (1 << compound_order(page));
>
> How about to change this to
>
>
> nr_reclaimed += hpage_nr_pages(page);
Please don't. That embeds the knowledge that we can only swap out either
normal pages o
On Thu, May 09, 2019 at 08:42:32PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.1 release.
> There are 30 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.
There's no need to support either DYNAMIC_FTRACE=n or mcount (non fentry)
in x86_32. As the static tracing (DYNAMIC_FTRACE=n) does not support
fentry, we can just remove it, as the static tracing is only around to
test the static tracing in generic code as other architectures have it
but not DYNAMI
From: "Steven Rostedt (VMware)"
There's two methods of enabling function tracing in Linux on x86. One is
with just "gcc -pg" and the other is "gcc -pg -mfentry". The former will use
calls to a special function "mcount" after the frame is set up in all C
functions. The latter will add calls to a s
From: "Steven Rostedt (VMware)"
When DYNAMIC_FTRACE is enabled in the kernel, all the functions that can be
traced by the function tracer have a "nop" placeholder at the start of the
function. When function tracing is enabled, the nop is converted into a call
to the tracing infrastructure where t
201 - 300 of 568 matches
Mail list logo
