On 1 November 2018 at 08:44, Nathan Chancellor wrote:
> Clang warns when one enumerated type is implicitly converted to another:
>
> drivers/pinctrl/sprd/pinctrl-sprd.c:845:19: warning: implicit conversion
> from enumeration type 'enum sprd_pinconf_params' to different
> enumeration type 'enum
On 1 November 2018 at 08:44, Nathan Chancellor wrote:
> Clang warns when one enumerated type is implicitly converted to another:
>
> drivers/pinctrl/sprd/pinctrl-sprd.c:845:19: warning: implicit conversion
> from enumeration type 'enum sprd_pinconf_params' to different
> enumeration type 'enum
On 31/10/18 18:58, Daniel Bristot de Oliveira wrote:
> On 10/31/18 5:40 PM, Juri Lelli wrote:
> > On 31/10/18 17:18, Daniel Bristot de Oliveira wrote:
> >> On 10/30/18 12:08 PM, luca abeni wrote:
> >>> Hi Peter,
> >>>
> >>> On Tue, 30 Oct 2018 11:45:54 +0100
> >>> Peter Zijlstra wrote:
> >>>
On 31/10/18 18:58, Daniel Bristot de Oliveira wrote:
> On 10/31/18 5:40 PM, Juri Lelli wrote:
> > On 31/10/18 17:18, Daniel Bristot de Oliveira wrote:
> >> On 10/30/18 12:08 PM, luca abeni wrote:
> >>> Hi Peter,
> >>>
> >>> On Tue, 30 Oct 2018 11:45:54 +0100
> >>> Peter Zijlstra wrote:
> >>>
Hello Greg, Linus,
Greg, I didn't get your feedback on v10 of the i3c patchset [1] where I
was asking if you'd agree to have this framework merged in 4.20 (I know
you were busy with the 4.19 release and after that the Kernel Summit, so
that's not a surprise), so I'm sending this PR. It's really
Hello Greg, Linus,
Greg, I didn't get your feedback on v10 of the i3c patchset [1] where I
was asking if you'd agree to have this framework merged in 4.20 (I know
you were busy with the 4.19 release and after that the Kernel Summit, so
that's not a surprise), so I'm sending this PR. It's really
Please pull this to fixup dtb Kbuild rules for csky subsystem.
The following changes since commit ac435075892e3e651c667b4a9f2267cf3ef1d5a2:
Merge tag 'csky-for-linus-4.20' of https://github.com/c-sky/csky-linux
(2018-10-29 08:25:00 -0700)
are available in the git repository at:
Please pull this to fixup dtb Kbuild rules for csky subsystem.
The following changes since commit ac435075892e3e651c667b4a9f2267cf3ef1d5a2:
Merge tag 'csky-for-linus-4.20' of https://github.com/c-sky/csky-linux
(2018-10-29 08:25:00 -0700)
are available in the git repository at:
The printk timestamps are very useful information to visually see
where kernel is spending time during boot. It also helps us see
the timing of hotplug events at runtime.
This patch enables printk timestamps in RISC-V defconfig so that
we have it enabled by default (similar to other architectures
The printk timestamps are very useful information to visually see
where kernel is spending time during boot. It also helps us see
the timing of hotplug events at runtime.
This patch enables printk timestamps in RISC-V defconfig so that
we have it enabled by default (similar to other architectures
This patch updates defconfig using savedefconfig on Linux-4.19.
Signed-off-by: Anup Patel
---
arch/riscv/configs/defconfig | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
index
This patch updates defconfig using savedefconfig on Linux-4.19.
Signed-off-by: Anup Patel
---
arch/riscv/configs/defconfig | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
index
+ Chandan from Display Port team,
On 10/30/2018 10:03 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-29 23:01:44)
On 10/30/2018 12:13 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-28 03:34:55)
On 2018-10-19 16:04, Taniya Das wrote:
On 10/10/2018 2:04 AM, Stephen Boyd wrote:
+ Chandan from Display Port team,
On 10/30/2018 10:03 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-29 23:01:44)
On 10/30/2018 12:13 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-28 03:34:55)
On 2018-10-19 16:04, Taniya Das wrote:
On 10/10/2018 2:04 AM, Stephen Boyd wrote:
On Wed, Oct 31, 2018 at 11:17:48AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 30, 2018 at 06:11:19PM -0700, Joel Fernandes wrote:
> > Hi Paul,
> >
> > On Tue, Oct 30, 2018 at 04:43:36PM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 30, 2018 at 03:26:49PM -0700, Joel Fernandes wrote:
> > > >
On Wed, Oct 31, 2018 at 11:17:48AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 30, 2018 at 06:11:19PM -0700, Joel Fernandes wrote:
> > Hi Paul,
> >
> > On Tue, Oct 30, 2018 at 04:43:36PM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 30, 2018 at 03:26:49PM -0700, Joel Fernandes wrote:
> > > >
On Wed, Oct 31, 2018 at 9:23 AM Jann Horn wrote:
>
> +linux-api, Andy Lutomirski, Eric Biederman
>
> On Wed, Oct 31, 2018 at 3:12 AM Daniel Colascione wrote:
> > Add a simple proc-based kill interface. To use /proc/pid/kill, just
> > write the signal number in base-10 ASCII to the kill file of
Hi Adrian,
my fix is evidently incomplete - I just crashed elgar trying to remove
the pata_buddha module, sorry. Must've done something silly.
So no, can't post a patch to add module_exit just yet.
Cheers,
Michael
Am 31.10.2018 um 23:06 schrieb John Paul Adrian Glaubitz:
Hi!
On
On Wed, Oct 31, 2018 at 9:23 AM Jann Horn wrote:
>
> +linux-api, Andy Lutomirski, Eric Biederman
>
> On Wed, Oct 31, 2018 at 3:12 AM Daniel Colascione wrote:
> > Add a simple proc-based kill interface. To use /proc/pid/kill, just
> > write the signal number in base-10 ASCII to the kill file of
Hi Adrian,
my fix is evidently incomplete - I just crashed elgar trying to remove
the pata_buddha module, sorry. Must've done something silly.
So no, can't post a patch to add module_exit just yet.
Cheers,
Michael
Am 31.10.2018 um 23:06 schrieb John Paul Adrian Glaubitz:
Hi!
On
On Thu, Nov 1, 2018 at 4:20 AM Olof Johansson wrote:
>
> On Wed, Oct 31, 2018 at 1:42 PM Palmer Dabbelt wrote:
> >
> > On Wed, 31 Oct 2018 12:20:40 PDT (-0700), Olof Johansson wrote:
> > > On Tue, Oct 30, 2018 at 5:37 AM Anup Patel wrote:
> > >>
> > >> The printk timestamps are very useful
On Thu, Nov 1, 2018 at 4:20 AM Olof Johansson wrote:
>
> On Wed, Oct 31, 2018 at 1:42 PM Palmer Dabbelt wrote:
> >
> > On Wed, 31 Oct 2018 12:20:40 PDT (-0700), Olof Johansson wrote:
> > > On Tue, Oct 30, 2018 at 5:37 AM Anup Patel wrote:
> > >>
> > >> The printk timestamps are very useful
Hi all,
On Thu, 1 Nov 2018 09:13:07 +0800 kernel test robot
wrote:
>
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit b179f0826c6a13563c5ce0554c6da6748a1fa699
>
Hi all,
On Thu, 1 Nov 2018 09:13:07 +0800 kernel test robot
wrote:
>
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit b179f0826c6a13563c5ce0554c6da6748a1fa699
>
On Thu, Nov 1, 2018 at 3:59 AM James Bottomley
wrote:
>
> On Tue, 2018-10-16 at 11:52 +0200, Laurent Vivier wrote:
> > Hi,
> >
> > Any comment on this last version?
> >
> > Any chance to be merged?
>
> I've got a use case for this: I went to one of the Graphene talks in
> Edinburgh and it struck
On Thu, Nov 1, 2018 at 3:59 AM James Bottomley
wrote:
>
> On Tue, 2018-10-16 at 11:52 +0200, Laurent Vivier wrote:
> > Hi,
> >
> > Any comment on this last version?
> >
> > Any chance to be merged?
>
> I've got a use case for this: I went to one of the Graphene talks in
> Edinburgh and it struck
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181031:
My fixes tree contains this:
"drivers: net: include linux/ip.h for iphdr"
Non-merge commits (relative to Linus' tree): 790
953 files chan
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181031:
My fixes tree contains this:
"drivers: net: include linux/ip.h for iphdr"
Non-merge commits (relative to Linus' tree): 790
953 files chan
Hi Arnd,
On Thu, Nov 1, 2018 at 6:42 AM Arnd Bergmann wrote:
>
> On 10/31/18, Randy Dunlap wrote:
> > On 10/30/18 8:59 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add any v4.21/v5.1 code to your linux-next included trees
> >> until after the merge window closes.
> >>
> >>
Hi Arnd,
On Thu, Nov 1, 2018 at 6:42 AM Arnd Bergmann wrote:
>
> On 10/31/18, Randy Dunlap wrote:
> > On 10/30/18 8:59 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add any v4.21/v5.1 code to your linux-next included trees
> >> until after the merge window closes.
> >>
> >>
Em qua, 2018-10-31 às 20:24 -0300, Leonardo Bras escreveu:
> Em seg, 2018-10-29 às 01:42 +0900, Masahiro Yamada escreveu:
> > On Wed, Oct 24, 2018 at 1:05 PM Leonardo Bras
> > wrote:
> > > Changes the parameter name to avoid shadowing a variable.
> > >
> > > Signed-off-by: Leonardo Bras
> >
>
Em qua, 2018-10-31 às 20:24 -0300, Leonardo Bras escreveu:
> Em seg, 2018-10-29 às 01:42 +0900, Masahiro Yamada escreveu:
> > On Wed, Oct 24, 2018 at 1:05 PM Leonardo Bras
> > wrote:
> > > Changes the parameter name to avoid shadowing a variable.
> > >
> > > Signed-off-by: Leonardo Bras
> >
>
Refactors the code to accept the modules list as a parameter in
the functions that need it, and moves the variable from the
global scope to the main function scope.
This also fixes the parameter shadowing of add_depends.
Signed-off-by: Leonardo Bras
---
scripts/mod/modpost.c | 39
Refactors the code to accept the modules list as a parameter in
the functions that need it, and moves the variable from the
global scope to the main function scope.
This also fixes the parameter shadowing of add_depends.
Signed-off-by: Leonardo Bras
---
scripts/mod/modpost.c | 39
On Wed, Oct 31, 2018 at 2:10 AM, Peter Zijlstra wrote:
> On Tue, Oct 30, 2018 at 04:28:16PM +, Will Deacon wrote:
>> On Tue, Oct 30, 2018 at 04:58:41PM +0100, Peter Zijlstra wrote:
>> > Like mentioned elsewhere; if you do write_enable() + write_disable()
>> > thingies, it all becomes:
>> >
>>
On Wed, Oct 31, 2018 at 2:10 AM, Peter Zijlstra wrote:
> On Tue, Oct 30, 2018 at 04:28:16PM +, Will Deacon wrote:
>> On Tue, Oct 30, 2018 at 04:58:41PM +0100, Peter Zijlstra wrote:
>> > Like mentioned elsewhere; if you do write_enable() + write_disable()
>> > thingies, it all becomes:
>> >
>>
On 18-10-31 18:15:39, Peter Zijlstra wrote:
> On Wed, Oct 31, 2018 at 11:07:22AM -0400, Waiman Long wrote:
> > On 10/31/2018 10:10 AM, Peter Zijlstra wrote:
> > > On Wed, Oct 31, 2018 at 09:54:17AM +0800, Yi Sun wrote:
> > >> On 18-10-23 17:33:28, Yi Sun wrote:
> > >>> On 18-10-23 10:51:27, Peter
Hi Larry,
I still have a few tiny comments for your patch, please refer to them.
On 2018/11/1 5:28, Andrew Morton wrote:
>
> Folks, could we please review this patch for upstream inclusion?
>
> Thanks.
>
>
> From: Larry Chen
> Subject: ocfs2: fix deadlock caused by ocfs2_defrag_extent
>
>
On 18-10-31 18:15:39, Peter Zijlstra wrote:
> On Wed, Oct 31, 2018 at 11:07:22AM -0400, Waiman Long wrote:
> > On 10/31/2018 10:10 AM, Peter Zijlstra wrote:
> > > On Wed, Oct 31, 2018 at 09:54:17AM +0800, Yi Sun wrote:
> > >> On 18-10-23 17:33:28, Yi Sun wrote:
> > >>> On 18-10-23 10:51:27, Peter
Hi Larry,
I still have a few tiny comments for your patch, please refer to them.
On 2018/11/1 5:28, Andrew Morton wrote:
>
> Folks, could we please review this patch for upstream inclusion?
>
> Thanks.
>
>
> From: Larry Chen
> Subject: ocfs2: fix deadlock caused by ocfs2_defrag_extent
>
>
Refactors the code to accept the modules list as a parameter in
the functions that need it, and moves the variable from the
global scope to the main function scope.
This also fixes the parameter shadowing of add_depends.
Signed-off-by: Leonardo Bras
---
scripts/mod/modpost.c | 39
Refactors the code to accept the modules list as a parameter in
the functions that need it, and moves the variable from the
global scope to the main function scope.
This also fixes the parameter shadowing of add_depends.
Signed-off-by: Leonardo Bras
---
scripts/mod/modpost.c | 39
From: Long Li
On a large system with multiple devices of the same class (e.g. NVMe disks,
using managed IRQs), the kernel tends to concentrate their IRQs on several
CPUs.
The issue is that when NVMe calls irq_matrix_alloc_managed(), the assigned
CPU tends to be the first several CPUs in the
From: Long Li
On a large system with multiple devices of the same class (e.g. NVMe disks,
using managed IRQs), the kernel tends to concentrate their IRQs on several
CPUs.
The issue is that when NVMe calls irq_matrix_alloc_managed(), the assigned
CPU tends to be the first several CPUs in the
Hi Linus,
This tag has a few merge conflicts with some x86/cpu id changes. Stephen
Rothwell's merge in next/master is correct, and I have provided an
example here as well:
git://git.infradead.org/linux-platform-drivers-x86.git pdx86-v4.20-1-merge
Thanks,
Darren Hart
VMware Open Source
Hi Linus,
This tag has a few merge conflicts with some x86/cpu id changes. Stephen
Rothwell's merge in next/master is correct, and I have provided an
example here as well:
git://git.infradead.org/linux-platform-drivers-x86.git pdx86-v4.20-1-merge
Thanks,
Darren Hart
VMware Open Source
On Tue, 2018-10-16 at 11:52 +0200, Laurent Vivier wrote:
> Hi,
>
> Any comment on this last version?
>
> Any chance to be merged?
I've got a use case for this: I went to one of the Graphene talks in
Edinburgh and it struck me that we seem to keep reinventing the type of
sandboxing that
On Tue, 2018-10-16 at 11:52 +0200, Laurent Vivier wrote:
> Hi,
>
> Any comment on this last version?
>
> Any chance to be merged?
I've got a use case for this: I went to one of the Graphene talks in
Edinburgh and it struck me that we seem to keep reinventing the type of
sandboxing that
Starting with GCC 8, a lot of unlikely code was moved out of line to
"cold" subfunctions in .text.unlikely.
For example, the unlikely bits of:
irq_do_set_affinity()
are moved out to the following subfunction:
irq_do_set_affinity.cold.49()
Starting with GCC 9, the numbered suffix has been
Starting with GCC 8, a lot of unlikely code was moved out of line to
"cold" subfunctions in .text.unlikely.
For example, the unlikely bits of:
irq_do_set_affinity()
are moved out to the following subfunction:
irq_do_set_affinity.cold.49()
Starting with GCC 9, the numbered suffix has been
Em Thu, 1 Nov 2018 08:28:20 +1100
Stephen Rothwell escreveu:
> Hi all,
>
> Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type
> without #include
>
> Introduced by commit
>
Em Thu, 1 Nov 2018 08:28:20 +1100
Stephen Rothwell escreveu:
> Hi all,
>
> Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type
> without #include
>
> Introduced by commit
>
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/firewire/net.c:488:9: warning:
variable ‘guid’ set but not used [-Wunused-but-set-variable]
It not used anymore after commit 6752c8db8e0c ("firewire net, ipv4 arp:
Extend hardware address and remove driver-level packet inspection.")
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/firewire/net.c:488:9: warning:
variable ‘guid’ set but not used [-Wunused-but-set-variable]
It not used anymore after commit 6752c8db8e0c ("firewire net, ipv4 arp:
Extend hardware address and remove driver-level packet inspection.")
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/edac/i82975x_edac.c:378:16: warning:
variable ‘dtype’ set but not used [-Wunused-but-set-variable]
It never used since introduction in commit
084a4fccef39 ("edac: move dimm properties to struct dimm_info")
Signed-off-by: YueHaibing
---
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/edac/i82975x_edac.c:378:16: warning:
variable ‘dtype’ set but not used [-Wunused-but-set-variable]
It never used since introduction in commit
084a4fccef39 ("edac: move dimm properties to struct dimm_info")
Signed-off-by: YueHaibing
---
Hi Rob,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 kbuild: consolidate Devicetree
dtb build rules
date: 4 weeks ago
Hi Rob,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 kbuild: consolidate Devicetree
dtb build rules
date: 4 weeks ago
On Wed, Oct 31, 2018 at 07:21:15PM +0100, Thomas Gleixner wrote:
> The SPDX identifier defines the license of the file already. No need for
> the boilerplate.
>
> Signed-off-by: Thomas Gleixner
> Cc: Richard Cochran
> ---
>
> @Richard: This file is (C) OMICRON, but I don't have a contact
>
On Wed, Oct 31, 2018 at 07:21:15PM +0100, Thomas Gleixner wrote:
> The SPDX identifier defines the license of the file already. No need for
> the boilerplate.
>
> Signed-off-by: Thomas Gleixner
> Cc: Richard Cochran
> ---
>
> @Richard: This file is (C) OMICRON, but I don't have a contact
>
On 2018/10/31 22:00, Peter Zijlstra wrote:
On Wed, Oct 31, 2018 at 02:53:20PM +0100, Peter Zijlstra wrote:
On Wed, Oct 31, 2018 at 02:01:20PM +0800, Zhenzhong Duan wrote:
On 2018/10/30 16:36, Peter Zijlstra wrote:
On Mon, Oct 29, 2018 at 11:55:06PM -0700, Zhenzhong Duan wrote:
Since
On 2018/10/31 22:00, Peter Zijlstra wrote:
On Wed, Oct 31, 2018 at 02:53:20PM +0100, Peter Zijlstra wrote:
On Wed, Oct 31, 2018 at 02:01:20PM +0800, Zhenzhong Duan wrote:
On 2018/10/30 16:36, Peter Zijlstra wrote:
On Mon, Oct 29, 2018 at 11:55:06PM -0700, Zhenzhong Duan wrote:
Since
From: Marcel Ziswiler
As UARTB and VFIR share their clock enable bit it is rather unwise for
the kernel to turn off the VFIR one should that be unused (and
potentially vice versa but so far there anyway is no VFIR driver).
Without this patch trying to use UARTB with the regular 8250 driver
will
From: Marcel Ziswiler
Fix a few spelling mistakes I stumbled upon while debugging a customers
UART issues.
Signed-off-by: Marcel Ziswiler
---
drivers/tty/serial/serial-tegra.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/serial-tegra.c
From: Marcel Ziswiler
Get rid of 3 duplicate defines.
Signed-off-by: Marcel Ziswiler
---
drivers/clk/tegra/clk-tegra-periph.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/clk/tegra/clk-tegra-periph.c
b/drivers/clk/tegra/clk-tegra-periph.c
index 38c4eb28c8bf..cc5275ec2c01
From: Marcel Ziswiler
As UARTB and VFIR share their clock enable bit it is rather unwise for
the kernel to turn off the VFIR one should that be unused (and
potentially vice versa but so far there anyway is no VFIR driver).
Without this patch trying to use UARTB with the regular 8250 driver
will
From: Marcel Ziswiler
Fix a few spelling mistakes I stumbled upon while debugging a customers
UART issues.
Signed-off-by: Marcel Ziswiler
---
drivers/tty/serial/serial-tegra.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/serial-tegra.c
From: Marcel Ziswiler
Get rid of 3 duplicate defines.
Signed-off-by: Marcel Ziswiler
---
drivers/clk/tegra/clk-tegra-periph.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/clk/tegra/clk-tegra-periph.c
b/drivers/clk/tegra/clk-tegra-periph.c
index 38c4eb28c8bf..cc5275ec2c01
This series features some UART related clock issue fix and clean-up.
Marcel Ziswiler (3):
clk: tegra: get rid of duplicate defines
clk: tegra: ignore unused vfir clock shared with uartb
serial: tegra: fix some spelling mistakes
drivers/clk/tegra/clk-tegra-periph.c | 5 +
This series features some UART related clock issue fix and clean-up.
Marcel Ziswiler (3):
clk: tegra: get rid of duplicate defines
clk: tegra: ignore unused vfir clock shared with uartb
serial: tegra: fix some spelling mistakes
drivers/clk/tegra/clk-tegra-periph.c | 5 +
On (10/31/18 13:27), Petr Mladek wrote:
> >
> > Signed-off-by: Sergey Senozhatsky
>
> The patch makes sense to me. The locks should stay busted also for
> console_flush_on_panic().
>
> With the added #include :
>
> Reviewed-by: Petr Mladek
Thanks!
Since there are no objections - how shall
On (10/31/18 13:27), Petr Mladek wrote:
> >
> > Signed-off-by: Sergey Senozhatsky
>
> The patch makes sense to me. The locks should stay busted also for
> console_flush_on_panic().
>
> With the added #include :
>
> Reviewed-by: Petr Mladek
Thanks!
Since there are no objections - how shall
Two small fixes, please pull.
Thanks!
The following changes since commit 4b42745211af552f170f38a1b97f4a112b5da6b2:
Merge tag 'armsoc-soc' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2018-10-29 15:37:33
-0700)
are available in the Git repository at:
CC Philip, current kbuild test robot maintainer.
On Wed, Oct 31, 2018 at 12:12:21PM -0600, Logan Gunthorpe wrote:
On 2018-10-31 11:52 a.m., Olof Johansson wrote:
I've migrated machines to a new system and that CI is up and running.
Right now the emails don't go anywhere but me, but let me
Two small fixes, please pull.
Thanks!
The following changes since commit 4b42745211af552f170f38a1b97f4a112b5da6b2:
Merge tag 'armsoc-soc' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2018-10-29 15:37:33
-0700)
are available in the Git repository at:
CC Philip, current kbuild test robot maintainer.
On Wed, Oct 31, 2018 at 12:12:21PM -0600, Logan Gunthorpe wrote:
On 2018-10-31 11:52 a.m., Olof Johansson wrote:
I've migrated machines to a new system and that CI is up and running.
Right now the emails don't go anywhere but me, but let me
made minor cleanup to patch 1 and 2, added Ronnie's reviewed to patch
3, and tentatively merged to cifs-2.6.git for-next
On Wed, Oct 31, 2018 at 5:16 PM Long Li wrote:
>
> From: Long Li
>
> With direct read/write functions implemented, add them to file_operations.
>
> Dircet I/O is used under
made minor cleanup to patch 1 and 2, added Ronnie's reviewed to patch
3, and tentatively merged to cifs-2.6.git for-next
On Wed, Oct 31, 2018 at 5:16 PM Long Li wrote:
>
> From: Long Li
>
> With direct read/write functions implemented, add them to file_operations.
>
> Dircet I/O is used under
On Thu, Nov 01, 2018 at 01:27:08AM +0100, Alexandre Belloni wrote:
Hello,
On 31/10/2018 19:12:06-0400, Sasha Levin wrote:
- m->rtc = rtc_device_register(DRIVER_NAME,
- >client->dev,
- _rtc_ops, THIS_MODULE);
- if (IS_ERR(m->rtc)) {
+
On Thu, Nov 01, 2018 at 01:27:08AM +0100, Alexandre Belloni wrote:
Hello,
On 31/10/2018 19:12:06-0400, Sasha Levin wrote:
- m->rtc = rtc_device_register(DRIVER_NAME,
- >client->dev,
- _rtc_ops, THIS_MODULE);
- if (IS_ERR(m->rtc)) {
+
Randomize address space after each fork
~~
I might be entirely wrong with what I write
and the solution proposed thereafter, yet I
want to raise awareness that with current linux
kernels it is possible to leak (at least) heap
addresses in an attempt to
Randomize address space after each fork
~~
I might be entirely wrong with what I write
and the solution proposed thereafter, yet I
want to raise awareness that with current linux
kernels it is possible to leak (at least) heap
addresses in an attempt to
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 7aa54be2976550f17c11a1c3e3630002dea39303 locking/qspinlock, x86:
Provide liveness guarantee
date: 2 weeks
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 7aa54be2976550f17c11a1c3e3630002dea39303 locking/qspinlock, x86:
Provide liveness guarantee
date: 2 weeks
On 10/31/18 5:48 PM, kbuild test robot wrote:
> Hi Rakesh,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 5b7449810ae6d652629c550d3974c8453836d229
> commit: 6bae5ea9498926440ffc883f3dbceb0adc65e492
On 10/31/18 5:48 PM, kbuild test robot wrote:
> Hi Rakesh,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 5b7449810ae6d652629c550d3974c8453836d229
> commit: 6bae5ea9498926440ffc883f3dbceb0adc65e492
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 21924765862a0871908a35cb0e53e2e1c169b888 SUNRPC: use cmpxchg64() in
gss_seq_send64_fetch_and_inc()
date: 4
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5b7449810ae6d652629c550d3974c8453836d229
commit: 21924765862a0871908a35cb0e53e2e1c169b888 SUNRPC: use cmpxchg64() in
gss_seq_send64_fetch_and_inc()
date: 4
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-zynq.c:985:18: warning: implicit conversion from
enumeration type 'enum zynq_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
{"io-standard",
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-zynq.c:985:18: warning: implicit conversion from
enumeration type 'enum zynq_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
{"io-standard",
On Wed, Oct 31, 2018 at 07:17:45AM -0700, Christoph Hellwig wrote:
> On Wed, Oct 31, 2018 at 04:46:10PM +0530, Anup Patel wrote:
> > I agree that we need a place for vendor-specific ISA extensions and
> > having vendor-specific directories is also good.
>
> The only sensible answer is that we
On Wed, Oct 31, 2018 at 07:17:45AM -0700, Christoph Hellwig wrote:
> On Wed, Oct 31, 2018 at 04:46:10PM +0530, Anup Patel wrote:
> > I agree that we need a place for vendor-specific ISA extensions and
> > having vendor-specific directories is also good.
>
> The only sensible answer is that we
Clang warns when one enumerated type is implicitly converted to another:
drivers/rtc/rtc-omap.c:574:21: warning: implicit conversion from
enumeration type 'enum rtc_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
{"ti,active-high",
Clang warns when one enumerated type is implicitly converted to another:
drivers/rtc/rtc-omap.c:574:21: warning: implicit conversion from
enumeration type 'enum rtc_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
{"ti,active-high",
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-lpc18xx.c:643:29: warning: implicit conversion
from enumeration type 'enum lpc18xx_pin_config_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-lpc18xx.c:643:29: warning: implicit conversion
from enumeration type 'enum lpc18xx_pin_config_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-max77620.c:56:12: warning: implicit conversion
from enumeration type 'enum max77620_pinconf_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
.param =
Clang warns when one enumerated type is implicitly converted to another:
drivers/pinctrl/pinctrl-max77620.c:56:12: warning: implicit conversion
from enumeration type 'enum max77620_pinconf_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
.param =
On 10/31/18 2:02 PM, Fenghua Yu wrote:
> resctrl tests will be implemented. README is added for the tool first.
>
> Signed-off-by: Fenghua Yu
Hi,
> ---
> tools/testing/selftests/resctrl/README | 53
> ++
> 1 file changed, 53 insertions(+)
> create mode 100644
On 10/31/18 2:02 PM, Fenghua Yu wrote:
> resctrl tests will be implemented. README is added for the tool first.
>
> Signed-off-by: Fenghua Yu
Hi,
> ---
> tools/testing/selftests/resctrl/README | 53
> ++
> 1 file changed, 53 insertions(+)
> create mode 100644
1 - 100 of 2040 matches
Mail list logo
