Re: [PATCH v9 04/11] arm64: kexec_file: allocate memory walking through memblock list

James, On Tue, May 01, 2018 at 06:46:09PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > We need to prevent firmware-reserved memory regions, particularly EFI > > memory map as well as ACPI tables, from being corrupted by loading > > kernel/initrd (or

Re: [PATCH v9 04/11] arm64: kexec_file: allocate memory walking through memblock list

James, On Tue, May 01, 2018 at 06:46:09PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > We need to prevent firmware-reserved memory regions, particularly EFI > > memory map as well as ACPI tables, from being corrupted by loading > > kernel/initrd (or

Re: [PATCH V2 1/5] backlight: qcom-wled: Rename pm8941-wled.c to qcom-wled.c

Hi Jingoo Han, Thanks for the response. Thanks, Kiran On 2018-05-04 21:25, Jingoo Han wrote: On Thursday, May 3, 2018 6:12 AM, Kiran Gunda wrote: If you really want someone to review your patch, please add more detailed explanations. 1. Please add 0th patch. I have already added the 0th

Re: [PATCH V2 1/5] backlight: qcom-wled: Rename pm8941-wled.c to qcom-wled.c

Hi Jingoo Han, Thanks for the response. Thanks, Kiran On 2018-05-04 21:25, Jingoo Han wrote: On Thursday, May 3, 2018 6:12 AM, Kiran Gunda wrote: If you really want someone to review your patch, please add more detailed explanations. 1. Please add 0th patch. I have already added the 0th

Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge

On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote: > > diff --git a/block/bfq-mq-iosched.c b/block/bfq-mq-iosched.c > index 118f319af7c0..6662efe29b69 100644 > --- a/block/bfq-mq-iosched.c > +++ b/block/bfq-mq-iosched.c > @@ -525,8 +525,13 @@ static void bfq_limit_depth(unsigned int op,

Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge

On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote: > > diff --git a/block/bfq-mq-iosched.c b/block/bfq-mq-iosched.c > index 118f319af7c0..6662efe29b69 100644 > --- a/block/bfq-mq-iosched.c > +++ b/block/bfq-mq-iosched.c > @@ -525,8 +525,13 @@ static void bfq_limit_depth(unsigned int op,

Re: [PATCH 3/3] staging: wilc1000: Remove unnecessary array index check

On Sun, 6 May 2018 00:33:33 -0700 Nathan Chancellor wrote: > This statment triggers GCC's -Wtype-limit since key_index is an > unsigned integer so it cannot be less than zero. > > Signed-off-by: Nathan Chancellor Reviewed-by: Ajay Singh

Re: [PATCH 3/3] staging: wilc1000: Remove unnecessary array index check

On Sun, 6 May 2018 00:33:33 -0700 Nathan Chancellor wrote: > This statment triggers GCC's -Wtype-limit since key_index is an > unsigned integer so it cannot be less than zero. > > Signed-off-by: Nathan Chancellor Reviewed-by: Ajay Singh > --- >

Re: [PATCH 2/3] staging: wilc1000: Remove useless function

On Sun, 6 May 2018 00:33:32 -0700 Nathan Chancellor wrote: > GCC warns that 'wid' is unused in wilc_remove_key and it's correct; > the variable is only local. Get rid of the function (since it just > returns zero) and shuffle the remaining code into one if statement. >

Re: [PATCH 2/3] staging: wilc1000: Remove useless function

On Sun, 6 May 2018 00:33:32 -0700 Nathan Chancellor wrote: > GCC warns that 'wid' is unused in wilc_remove_key and it's correct; > the variable is only local. Get rid of the function (since it just > returns zero) and shuffle the remaining code into one if statement. > > Signed-off-by: Nathan

Re: [PATCH 1/3] staging: wilc1000: Remove unused variables

Thank you for the patch series. On Sun, 6 May 2018 00:33:31 -0700 Nathan Chancellor wrote: > GCC warns these variables are all set but never used so remove them. > > Signed-off-by: Nathan Chancellor Reviewed-by: Ajay Singh

Re: [PATCH 1/3] staging: wilc1000: Remove unused variables

Thank you for the patch series. On Sun, 6 May 2018 00:33:31 -0700 Nathan Chancellor wrote: > GCC warns these variables are all set but never used so remove them. > > Signed-off-by: Nathan Chancellor Reviewed-by: Ajay Singh > --- > drivers/staging/wilc1000/host_interface.c | 12

Re: [PATCH] clocksource/drivers/sprd: Fix Kconfig dependency

On Thu, May 03, 2018 at 08:27:32PM +0800, Chunyan Zhang wrote: > SPRD arch doesn't select SPRD_TIMER, so this config would not > appear even if ARCH_SPRD is set and COMPILE_TEST is not. > > Fix the Kconfig selection rule by letting the SPRD arch to select. Instead of changing this Kconfig,

Re: [PATCH] clocksource/drivers/sprd: Fix Kconfig dependency

On Thu, May 03, 2018 at 08:27:32PM +0800, Chunyan Zhang wrote: > SPRD arch doesn't select SPRD_TIMER, so this config would not > appear even if ARCH_SPRD is set and COMPILE_TEST is not. > > Fix the Kconfig selection rule by letting the SPRD arch to select. Instead of changing this Kconfig,

linux-next: Tree for May 7

Hi all, Changes since 20180504: The net-next tree gained a conflict against the net tree. The tip tree gained conflicts against the bpf-next tree. Non-merge commits (relative to Linus' tree): 4139 3963 files changed, 164135 insertions(+), 75455 deletions(-)

linux-next: Tree for May 7

Hi all, Changes since 20180504: The net-next tree gained a conflict against the net tree. The tip tree gained conflicts against the bpf-next tree. Non-merge commits (relative to Linus' tree): 4139 3963 files changed, 164135 insertions(+), 75455 deletions(-)

Re: [PATCH v9 03/11] arm64: kexec_file: invoke the kernel without purgatory

On Tue, May 01, 2018 at 06:46:06PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > On arm64, purugatory would do almosty nothing. So just invoke secondary > > kernel directy by jumping into its entry code. > > (Nits: purgatory, almost, directly) Oops, I

Re: [PATCH v9 03/11] arm64: kexec_file: invoke the kernel without purgatory

On Tue, May 01, 2018 at 06:46:06PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > On arm64, purugatory would do almosty nothing. So just invoke secondary > > kernel directy by jumping into its entry code. > > (Nits: purgatory, almost, directly) Oops, I

Re: [PATCH] scsi: sg: fix a missing-check bug

On 2018-05-05 11:21 PM, Wenwen Wang wrote: In sg_write(), the opcode of the command is firstly copied from the userspace pointer 'buf' and saved to the kernel variable 'opcode', using the __get_user() function. The size of the command, i.e., 'cmd_size' is then calculated based on the 'opcode'.

Re: [PATCH] scsi: sg: fix a missing-check bug

On 2018-05-05 11:21 PM, Wenwen Wang wrote: In sg_write(), the opcode of the command is firstly copied from the userspace pointer 'buf' and saved to the kernel variable 'opcode', using the __get_user() function. The size of the command, i.e., 'cmd_size' is then calculated based on the 'opcode'.

Re: [greybus-dev] [PATCH] staging: greybus: Remove unused local variable

On 05-05-18, 23:50, Nathan Chancellor wrote: > Fixes the following W=1 warning: variable ‘intf_id’ set but > not used [-Wunused-but-set-variable] > > Signed-off-by: Nathan Chancellor > --- > drivers/staging/greybus/svc.c | 3 --- > 1 file changed, 3 deletions(-) > >

Re: [greybus-dev] [PATCH] staging: greybus: Remove unused local variable

On 05-05-18, 23:50, Nathan Chancellor wrote: > Fixes the following W=1 warning: variable ‘intf_id’ set but > not used [-Wunused-but-set-variable] > > Signed-off-by: Nathan Chancellor > --- > drivers/staging/greybus/svc.c | 3 --- > 1 file changed, 3 deletions(-) > > diff --git

Re: [PATCH 04/24] selftests: cpufreq: return Kselftest Skip code for skipped tests

On 04-05-18, 19:13, Shuah Khan (Samsung OSG) wrote: > When cpufreq test is skipped because of unmet dependencies and/or > unsupported configuration, it exits with error which is treated as > a fail by the Kselftest framework. This leads to false negative > result even when the test could not be

Re: [PATCH 04/24] selftests: cpufreq: return Kselftest Skip code for skipped tests

On 04-05-18, 19:13, Shuah Khan (Samsung OSG) wrote: > When cpufreq test is skipped because of unmet dependencies and/or > unsupported configuration, it exits with error which is treated as > a fail by the Kselftest framework. This leads to false negative > result even when the test could not be

Re: Kernel build with gcc 8 a lot of warnings

On Sat, May 05, 2018 at 09:21:12PM +0200, damian wrote: > Helllo together, > > Hello everybody, > > is something special to note when kernel build with gcc 8? I receive various > warnings from the objtool: > With GCC 7 works all fine. > > kernel/cgroup/cgroup.o: warning: objtool:

Re: Kernel build with gcc 8 a lot of warnings

On Sat, May 05, 2018 at 09:21:12PM +0200, damian wrote: > Helllo together, > > Hello everybody, > > is something special to note when kernel build with gcc 8? I receive various > warnings from the objtool: > With GCC 7 works all fine. > > kernel/cgroup/cgroup.o: warning: objtool:

Re: moving affs + RDB partition support to staging?

On 20180506 01:52, John Paul Adrian Glaubitz wrote: On 04/27/2018 03:26 AM, jdow wrote: And before I forget there are two features of the RDBs that I heartily recommend never implementing on Linux. They were good ideas at the time; but, times changed. The RDBs are capable of storing

Re: moving affs + RDB partition support to staging?

On 20180506 01:52, John Paul Adrian Glaubitz wrote: On 04/27/2018 03:26 AM, jdow wrote: And before I forget there are two features of the RDBs that I heartily recommend never implementing on Linux. They were good ideas at the time; but, times changed. The RDBs are capable of storing

[PATCH v2 7/7] platform/x86: mlx-platform: Add mlxreg-io platform driver activation

Add mlxreg-io platform driver activation. Access driver uses the same regmap infrastructure as others Mellanox platform drivers. Specific registers description for default platform data configuration are added to mlx-platform. There are the registers for resets control, reset causes monitoring,

[PATCH v2 7/7] platform/x86: mlx-platform: Add mlxreg-io platform driver activation

Add mlxreg-io platform driver activation. Access driver uses the same regmap infrastructure as others Mellanox platform drivers. Specific registers description for default platform data configuration are added to mlx-platform. There are the registers for resets control, reset causes monitoring,

[PATCH v2 4/7] platform: mellanox: add new ODM system types to mlx-platform

Add new ODM system types, matched according to DMI_BOARD_NAME. The supported ODM Ids are: VMOD0001, VMOD0002, VMOD0003, VMOD0004, VMOD0005. Patch does not introduce new systems, but allows to ODM companies to set DMI_BOARD_VENDOR and DMI_PRODUCT_NAME on their own. It assumes that ODM company can't

[PATCH v2 5/7] platform/x86: mlx-platform: Add LED platform driver activation

Add LED platform driver activation from mlx-platform. This LED driver uses the same regmap infrastructure as others Mellanox platform drivers, so LED specific registers description is added. System LED configuration depends on system type. To support all the relevant types per system type LED

[PATCH v2 4/7] platform: mellanox: add new ODM system types to mlx-platform

Add new ODM system types, matched according to DMI_BOARD_NAME. The supported ODM Ids are: VMOD0001, VMOD0002, VMOD0003, VMOD0004, VMOD0005. Patch does not introduce new systems, but allows to ODM companies to set DMI_BOARD_VENDOR and DMI_PRODUCT_NAME on their own. It assumes that ODM company can't

[PATCH v2 5/7] platform/x86: mlx-platform: Add LED platform driver activation

Add LED platform driver activation from mlx-platform. This LED driver uses the same regmap infrastructure as others Mellanox platform drivers, so LED specific registers description is added. System LED configuration depends on system type. To support all the relevant types per system type LED

[PATCH v2 6/7] platform/mellanox: Introduce support for Mellanox register access driver

Introduce new Mellanox platform driver to allow access to Mellanox programmable device register space trough sysfs interface. The driver purpose is to provide sysfs interface for user space for the registers essential for system control and monitoring. The sets of registers for sysfs access are

[PATCH v2 3/7] platform/mellanox: mlxreg-hotplug: add extra cycle for hotplug work queue

Add extra cycle for hotplug work queue to handle the case when a signal is It adds missed logic for signal acknowledge, by adding an extra run for received, but no specific signal assertion is detected. Such case theoretically can happen for example in case several units are removed or inserted at

[PATCH v2 6/7] platform/mellanox: Introduce support for Mellanox register access driver

Introduce new Mellanox platform driver to allow access to Mellanox programmable device register space trough sysfs interface. The driver purpose is to provide sysfs interface for user space for the registers essential for system control and monitoring. The sets of registers for sysfs access are

[PATCH v2 3/7] platform/mellanox: mlxreg-hotplug: add extra cycle for hotplug work queue

Add extra cycle for hotplug work queue to handle the case when a signal is It adds missed logic for signal acknowledge, by adding an extra run for received, but no specific signal assertion is detected. Such case theoretically can happen for example in case several units are removed or inserted at

Re: Proof-of-concept: better(?) page-table manipulation API

On Tue, Apr 24, 2018 at 8:44 AM Kirill A. Shutemov < kirill.shute...@linux.intel.com> wrote: > Hi everybody, > I've proposed to talk about page able manipulation API on the LSF/MM'2018, > so I need something material to talk about. I gave it a quick read. I like the concept a lot, and I have

Re: Proof-of-concept: better(?) page-table manipulation API

On Tue, Apr 24, 2018 at 8:44 AM Kirill A. Shutemov < kirill.shute...@linux.intel.com> wrote: > Hi everybody, > I've proposed to talk about page able manipulation API on the LSF/MM'2018, > so I need something material to talk about. I gave it a quick read. I like the concept a lot, and I have

Re: [PATCH v3] ASoC: da7219: read fmw property to get mclk for non-dts systems

On 5/4/2018 2:45 PM, Adam Thomson wrote: > On 03 May 2018 08:59, Akshu Agrawal wrote: > >> Non-dts based systems can use ACPI DSDT to pass on the mclk >> to da7219. >> This enables da7219 mclk to be linked to system clock. >> Enable/Disable of the mclk is already handled in the codec so >>

Re: [PATCH v3] ASoC: da7219: read fmw property to get mclk for non-dts systems

On 5/4/2018 2:45 PM, Adam Thomson wrote: > On 03 May 2018 08:59, Akshu Agrawal wrote: > >> Non-dts based systems can use ACPI DSDT to pass on the mclk >> to da7219. >> This enables da7219 mclk to be linked to system clock. >> Enable/Disable of the mclk is already handled in the codec so >>

Re: [PATCH v9 02/11] kexec_file: make kexec_image_post_load_cleanup_default() global

On Tue, May 01, 2018 at 06:46:04PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > Change this function from static to global so that arm64 can implement > > its own arch_kimage_file_post_load_cleanup() later using > >

Re: [PATCH v9 02/11] kexec_file: make kexec_image_post_load_cleanup_default() global

On Tue, May 01, 2018 at 06:46:04PM +0100, James Morse wrote: > Hi Akashi, > > On 25/04/18 07:26, AKASHI Takahiro wrote: > > Change this function from static to global so that arm64 can implement > > its own arch_kimage_file_post_load_cleanup() later using > >

Re: linux-next: manual merge of the tip tree with the bpf-next tree

Hi all, On Mon, 7 May 2018 12:09:09 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > arch/x86/net/bpf_jit_comp.c > > between commit: > > e782bdcf58c5 ("bpf, x64: remove ld_abs/ld_ind") > > from the bpf-next tree and

Re: linux-next: manual merge of the tip tree with the bpf-next tree

Hi all, On Mon, 7 May 2018 12:09:09 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > arch/x86/net/bpf_jit_comp.c > > between commit: > > e782bdcf58c5 ("bpf, x64: remove ld_abs/ld_ind") > > from the bpf-next tree and commit: > >

Re: [PATCH] x86/vdso: remove unused file

On Fri, May 4, 2018 at 10:59 AM Jann Horn wrote: > commit da861e18eccc ("x86, vdso: Get rid of the fake section mechanism") > left this file behind; nothing is using it anymore. Acked-by: Andy Lutomirski

Re: [PATCH] x86/vdso: remove unused file

On Fri, May 4, 2018 at 10:59 AM Jann Horn wrote: > commit da861e18eccc ("x86, vdso: Get rid of the fake section mechanism") > left this file behind; nothing is using it anymore. Acked-by: Andy Lutomirski

Re: [PATCH v2 01/14] mtd: rawnand: helper function for setting up ECC parameters

2018-05-03 21:20 GMT+09:00 Abhishek Sahu : > commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check, > match, maximize ECC settings") provides generic helpers which > drivers can use for setting up ECC parameters. > > Since same board can have different ECC strength

Re: [PATCH v2 01/14] mtd: rawnand: helper function for setting up ECC parameters

2018-05-03 21:20 GMT+09:00 Abhishek Sahu : > commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check, > match, maximize ECC settings") provides generic helpers which > drivers can use for setting up ECC parameters. > > Since same board can have different ECC strength nand chips so >

[PATCH v2 03/13] drm/kms/mode/exynos-dsi: using helper func drm_display_mode_to_videomode for calculating timing parameters

To avoid duplicate logic for the same Signed-off-by: Satendra Singh Thakur Acked-by: Madhur Verma Cc: Hemanshu Srivastava --- v2: Removed Mr Robin from reviewed-by field drivers/gpu/drm/exynos/exynos_drm_dsi.c |

[PATCH v2 03/13] drm/kms/mode/exynos-dsi: using helper func drm_display_mode_to_videomode for calculating timing parameters

To avoid duplicate logic for the same Signed-off-by: Satendra Singh Thakur Acked-by: Madhur Verma Cc: Hemanshu Srivastava --- v2: Removed Mr Robin from reviewed-by field drivers/gpu/drm/exynos/exynos_drm_dsi.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff

[PATCH v2] drm/kms/mode: added a new helper for calculating videomode from crtc's display mode

1. -Added a new helper drm_display_mode_crtc_to_videomode -This helper calculates mode parameters like --horizontal front_porch, back_porch, sync length --vertical front_porch, back_porch, sync length -using crtc fields of struct drm_display_mode -It uses following fields of crtc mode --horizontal

[PATCH v2] drm/kms/mode: added a new helper for calculating videomode from crtc's display mode

1. -Added a new helper drm_display_mode_crtc_to_videomode -This helper calculates mode parameters like --horizontal front_porch, back_porch, sync length --vertical front_porch, back_porch, sync length -using crtc fields of struct drm_display_mode -It uses following fields of crtc mode --horizontal

Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge

On Mon, 2018-05-07 at 04:43 +0200, Mike Galbraith wrote: > On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote: > > > > I've attached a compressed patch (to avoid possible corruption from my > > mailer). I'm little confident, but no pain, no gain, right? > > > > If possible, apply this patch

Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge

On Mon, 2018-05-07 at 04:43 +0200, Mike Galbraith wrote: > On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote: > > > > I've attached a compressed patch (to avoid possible corruption from my > > mailer). I'm little confident, but no pain, no gain, right? > > > > If possible, apply this patch

Re: [PATCH] VFIO: Fix Documentation

Hi, Alex. On 2018/5/1 2:38, Alex Williamson wrote: > On Fri, 20 Apr 2018 18:07:27 +0800 > "dongbo (E)" wrote: > >> From: Dong Bo >> >> Signed-off-by: Dong Bo >> --- > > Hi Dong Bo, > > The patch is corrupted, please resend and also

Re: [PATCH] VFIO: Fix Documentation

Hi, Alex. On 2018/5/1 2:38, Alex Williamson wrote: > On Fri, 20 Apr 2018 18:07:27 +0800 > "dongbo (E)" wrote: > >> From: Dong Bo >> >> Signed-off-by: Dong Bo >> --- > > Hi Dong Bo, > > The patch is corrupted, please resend and also include a commit log, > something as simple as "Update

Re: [RFC PATCH 3/3] arcnet: com20020: Add ethtool support

On Sat, May 05, 2018 at 11:35:29PM +0200, Andrea Greco wrote: > From: Andrea Greco > > Setup ethtols for export com20020 diag register > > Signed-off-by: Andrea Greco > --- > drivers/net/arcnet/com20020-isa.c| 1 + >

Re: [RFC PATCH 3/3] arcnet: com20020: Add ethtool support

On Sat, May 05, 2018 at 11:35:29PM +0200, Andrea Greco wrote: > From: Andrea Greco > > Setup ethtols for export com20020 diag register > > Signed-off-by: Andrea Greco > --- > drivers/net/arcnet/com20020-isa.c| 1 + > drivers/net/arcnet/com20020-membus.c | 1 + >

Linux 4.17-rc4

Hmm. Things look fairly normal. Two thirds of the 4.17-rc4 patch is drivers, which sounds about right. Media, networking, rdma, input, nvme, usb. A little bit of everything, in other words. There's the usual architecture suspects, and some othe rcore updates too (mainly networking, but some

Linux 4.17-rc4

Hmm. Things look fairly normal. Two thirds of the 4.17-rc4 patch is drivers, which sounds about right. Media, networking, rdma, input, nvme, usb. A little bit of everything, in other words. There's the usual architecture suspects, and some othe rcore updates too (mainly networking, but some

[PATCH] vfio: fix documentation

From: Dong Bo Update vfio_add_group_dev description to match the current API. Signed-off-by: Dong Bo --- Documentation/vfio.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt

[PATCH] vfio: fix documentation

From: Dong Bo Update vfio_add_group_dev description to match the current API. Signed-off-by: Dong Bo --- Documentation/vfio.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt index ef6a511..f1a4d3c 100644 ---

Re: [PATCH v3 6/9] ALSA: hda/ca0132: add alt_select_in/out for R3Di + SBZ

Hi, On May 6 2018 04:03, Connor McAdams wrote: Add functions ca0132_alt_select_out and ca0132_alt_select_in for switching outputs and inputs for r3di and sbz. Also, add enumerated controls for selecting output and input source. Signed-off-by: Connor McAdams ---

Re: [PATCH v3 6/9] ALSA: hda/ca0132: add alt_select_in/out for R3Di + SBZ

Hi, On May 6 2018 04:03, Connor McAdams wrote: Add functions ca0132_alt_select_out and ca0132_alt_select_in for switching outputs and inputs for r3di and sbz. Also, add enumerated controls for selecting output and input source. Signed-off-by: Connor McAdams --- sound/pci/hda/patch_ca0132.c

Re: [RFC PATCH 2/3] arcnet: com20020: Fixup missing SLOWARB bit

On Sat, May 05, 2018 at 11:37:54PM +0200, Andrea Greco wrote: > From: Andrea Greco > > If com20020 clock is major of 40Mhz SLOWARB bit is requested. > > Signed-off-by: Andrea Greco > --- > drivers/net/arcnet/com20020.c | 4 > 1 file changed, 4

Re: [RFC PATCH 2/3] arcnet: com20020: Fixup missing SLOWARB bit

On Sat, May 05, 2018 at 11:37:54PM +0200, Andrea Greco wrote: > From: Andrea Greco > > If com20020 clock is major of 40Mhz SLOWARB bit is requested. > > Signed-off-by: Andrea Greco > --- > drivers/net/arcnet/com20020.c | 4 > 1 file changed, 4 insertions(+) > > diff --git

Re: [RFC PATCH 1/3] arcnet: com20020: Add memory map of com20020

On Sat, May 05, 2018 at 11:34:45PM +0200, Andrea Greco wrote: > From: Andrea Greco Hi Andrea, Here are some (mostly stylistic) suggestions to help you get your driver merged. > Add support for com20022I/com20020, memory mapped chip version. > Support bus: Intel 80xx and

Re: [RFC PATCH 1/3] arcnet: com20020: Add memory map of com20020

On Sat, May 05, 2018 at 11:34:45PM +0200, Andrea Greco wrote: > From: Andrea Greco Hi Andrea, Here are some (mostly stylistic) suggestions to help you get your driver merged. > Add support for com20022I/com20020, memory mapped chip version. > Support bus: Intel 80xx and Motorola 68xx. > Bus

Re: [PATCH 1/2] kdump/x86: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

On 04/27/18 at 05:14pm, Dave Young wrote: > Hi, > > This is a resend of below patches: > http://lists.infradead.org/pipermail/kexec/2017-October/019569.html > > I dropped the original patch 1 since Baoquan is not happy with it. > For patch 2 (the 1st patch in this series), there is some

Re: [PATCH 1/2] kdump/x86: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

On 04/27/18 at 05:14pm, Dave Young wrote: > Hi, > > This is a resend of below patches: > http://lists.infradead.org/pipermail/kexec/2017-October/019569.html > > I dropped the original patch 1 since Baoquan is not happy with it. > For patch 2 (the 1st patch in this series), there is some

RE: [PATCH] Documentation: block: cmdline-partition.txt fixes and additions

> -Original Message- > From: Randy Dunlap [mailto:rdun...@infradead.org] > Sent: Monday, May 07, 2018 2:50 AM > To: linux-bl...@vger.kernel.org; axboe > Cc: LKML ; Caizhiyong > ; Andrew Morton

RE: [PATCH] Documentation: block: cmdline-partition.txt fixes and additions

> -Original Message- > From: Randy Dunlap [mailto:rdun...@infradead.org] > Sent: Monday, May 07, 2018 2:50 AM > To: linux-bl...@vger.kernel.org; axboe > Cc: LKML ; Caizhiyong > ; Andrew Morton ; > linux-...@vger.kernel.org; Jonathan Corbet > Subject: [PATCH] Documentation: block:

Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge

On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote: > > I've attached a compressed patch (to avoid possible corruption from my > mailer). I'm little confident, but no pain, no gain, right? > > If possible, apply this patch on top of the fix I proposed in this > thread, just to eliminate

Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge

On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote: > > I've attached a compressed patch (to avoid possible corruption from my > mailer). I'm little confident, but no pain, no gain, right? > > If possible, apply this patch on top of the fix I proposed in this > thread, just to eliminate

Re: [PATCH 1/6] powerpc/syscalls: Switch trivial cases to SYSCALL_DEFINE

"Naveen N. Rao" writes: > Michael Ellerman wrote: >> From: Al Viro >> >> Signed-off-by: Al Viro >> --- >> arch/powerpc/kernel/pci_32.c | 6 +++--- >> arch/powerpc/kernel/pci_64.c |

Re: [PATCH 1/6] powerpc/syscalls: Switch trivial cases to SYSCALL_DEFINE

"Naveen N. Rao" writes: > Michael Ellerman wrote: >> From: Al Viro >> >> Signed-off-by: Al Viro >> --- >> arch/powerpc/kernel/pci_32.c | 6 +++--- >> arch/powerpc/kernel/pci_64.c | 4 ++-- >> arch/powerpc/mm/subpage-prot.c | 4 +++- >>

Re: moving affs + RDB partition support to staging?

Al, I don't think there is USB sticks with affs on them as yet. There isn't even USB host controller support for Amiga hardware (yet). Last I tried USB on m68k (Atari, 060 accelerator) the desktop experience was such that I'd rather not repeat that in a hurry (and that was a simple FAT USB

Re: moving affs + RDB partition support to staging?

Al, I don't think there is USB sticks with affs on them as yet. There isn't even USB host controller support for Amiga hardware (yet). Last I tried USB on m68k (Atari, 060 accelerator) the desktop experience was such that I'd rather not repeat that in a hurry (and that was a simple FAT USB

RE: [PATCH v3] block: add verifier for cmdline partition

> /* > * Purpose: allocate cmdline partitions. > * Returns: > @@ -93,6 +158,7 @@ int cmdline_partition(struct parsed_partitions *state) > disk_size = get_capacity(state->bdev->bd_disk) << 9; > > cmdline_parts_set(parts, disk_size, 1, add_part, (void *)state); > +

RE: [PATCH v3] block: add verifier for cmdline partition

> /* > * Purpose: allocate cmdline partitions. > * Returns: > @@ -93,6 +158,7 @@ int cmdline_partition(struct parsed_partitions *state) > disk_size = get_capacity(state->bdev->bd_disk) << 9; > > cmdline_parts_set(parts, disk_size, 1, add_part, (void *)state); > +

Re: [PATCH v3 5/9] ALSA: hda/ca0132: add/change helper functions for R3Di and SBZ

Hi, On May 6 2018 04:03, Connor McAdams wrote: Edit core functions to support the Sound Blaster Z and Recon3Di for startup and loading of the DSP, as well as setting effects. Signed-off-by: Connor McAdams --- sound/pci/hda/patch_ca0132.c | 1064

Re: [PATCH v3 5/9] ALSA: hda/ca0132: add/change helper functions for R3Di and SBZ

Hi, On May 6 2018 04:03, Connor McAdams wrote: Edit core functions to support the Sound Blaster Z and Recon3Di for startup and loading of the DSP, as well as setting effects. Signed-off-by: Connor McAdams --- sound/pci/hda/patch_ca0132.c | 1064 -- 1

[PATCH] pinctrl: mvebu: use correct MPP sel value for dev pins

The "dev" function is selected with the value 0x4 not 0x01. Fixes: commit d7ae8f8dee7f ("pinctrl: mvebu: pinctrl driver for 98DX3236 SoC") Signed-off-by: Chris Packham --- drivers/pinctrl/mvebu/pinctrl-armada-xp.c | 20 ++-- 1 file changed, 10

[PATCH] pinctrl: mvebu: use correct MPP sel value for dev pins

The "dev" function is selected with the value 0x4 not 0x01. Fixes: commit d7ae8f8dee7f ("pinctrl: mvebu: pinctrl driver for 98DX3236 SoC") Signed-off-by: Chris Packham --- drivers/pinctrl/mvebu/pinctrl-armada-xp.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-)

Re: [PATCH] iio: humidity: hts221: Fix sensor reads after resume

On Sun, 2018-05-06 at 17:19 +0100, Jonathan Cameron wrote: > On Mon, 30 Apr 2018 12:25:46 +0800 > Shrirang Bagul wrote: > > > CTRL1 register (ODR & BDU settings) gets reset after system comes back > > from suspend, causing subsequent reads from the sensor to fail. >

Re: [PATCH] iio: humidity: hts221: Fix sensor reads after resume

On Sun, 2018-05-06 at 17:19 +0100, Jonathan Cameron wrote: > On Mon, 30 Apr 2018 12:25:46 +0800 > Shrirang Bagul wrote: > > > CTRL1 register (ODR & BDU settings) gets reset after system comes back > > from suspend, causing subsequent reads from the sensor to fail. > > > > This patch restores

[PATCH v2] f2fs-tools: fix to match with the start_sector

f2fs-tools uses ioctl BLKSSZGET to get sector_size, however, this ioctl will return a value which may be larger than 512 (according to the value of q->limits.logical_block_size), then this will be inconsistent with the start_sector, since start_sector is got from ioctl HDIO_GETGEO and is always in

[PATCH v2] f2fs-tools: fix to match with the start_sector

f2fs-tools uses ioctl BLKSSZGET to get sector_size, however, this ioctl will return a value which may be larger than 512 (according to the value of q->limits.logical_block_size), then this will be inconsistent with the start_sector, since start_sector is got from ioctl HDIO_GETGEO and is always in

Re: moving affs + RDB partition support to staging?

On Sun, May 06, 2018 at 10:32:47PM +0100, Al Viro wrote: > On Sun, May 06, 2018 at 09:46:23PM +0100, Al Viro wrote: > > > I'm fixing that pile of crap (along with the NFS exports > > one and, hopefully, rename mess as well). HOWEVER, I am not going > > to take over the damn thing - David has

Re: moving affs + RDB partition support to staging?

On Sun, May 06, 2018 at 10:32:47PM +0100, Al Viro wrote: > On Sun, May 06, 2018 at 09:46:23PM +0100, Al Viro wrote: > > > I'm fixing that pile of crap (along with the NFS exports > > one and, hopefully, rename mess as well). HOWEVER, I am not going > > to take over the damn thing - David has

linux-next: manual merge of the tip tree with the bpf-next tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/x86/net/bpf_jit_comp.c between commit: e782bdcf58c5 ("bpf, x64: remove ld_abs/ld_ind") from the bpf-next tree and commit: 5f26c50143f5 ("x86/bpf: Clean up non-standard comments, to make the code more readable")

linux-next: manual merge of the tip tree with the bpf-next tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/x86/net/bpf_jit_comp.c between commit: e782bdcf58c5 ("bpf, x64: remove ld_abs/ld_ind") from the bpf-next tree and commit: 5f26c50143f5 ("x86/bpf: Clean up non-standard comments, to make the code more readable")

[PATCH-next] scsi: libsas: dynamically allocate and free ata host

Now the ata host for libsas is embedded in domain_device, and the ->kref member is not initialized. Afer we add ata transport class, ata_host_get() will be called when adding transport ATA port and a warning will be triggered as below: refcount_t: increment on 0; use-after-free. WARNING: CPU: 2

[PATCH-next] scsi: libsas: dynamically allocate and free ata host

Now the ata host for libsas is embedded in domain_device, and the ->kref member is not initialized. Afer we add ata transport class, ata_host_get() will be called when adding transport ATA port and a warning will be triggered as below: refcount_t: increment on 0; use-after-free. WARNING: CPU: 2

Re: [PATCH] isdn: eicon: fix a missing-check bug

Hello, I am just notice your subject line.There are missing something i think On Sat, May 05, 2018 at 02:32:46PM -0500, Wenwen Wang wrote: In divasmain.c, the function divas_write() firstly invokes the function diva_xdi_open_adapter() to open the adapter that matches with the adapter number

Re: [PATCH] isdn: eicon: fix a missing-check bug

Hello, I am just notice your subject line.There are missing something i think On Sat, May 05, 2018 at 02:32:46PM -0500, Wenwen Wang wrote: In divasmain.c, the function divas_write() firstly invokes the function diva_xdi_open_adapter() to open the adapter that matches with the adapter number

Re: [J-core] [PATCH v5 00/22] sh: LANDISK and R2Dplus convert to device tree

On Thu, 03 May 2018 19:07:38 +0900, John Paul Adrian Glaubitz wrote: > > [1 ] > Hi Rich! > > On 05/03/2018 04:33 AM, Rich Felker wrote: > > I found the U-Boot stuff here: > > > > https://ja.osdn.net/users/ysato/pf/uboot/wiki/FrontPage > > > > but I'm not sure how to install it yet. Will try

Re: [J-core] [PATCH v5 00/22] sh: LANDISK and R2Dplus convert to device tree

On Thu, 03 May 2018 19:07:38 +0900, John Paul Adrian Glaubitz wrote: > > [1 ] > Hi Rich! > > On 05/03/2018 04:33 AM, Rich Felker wrote: > > I found the U-Boot stuff here: > > > > https://ja.osdn.net/users/ysato/pf/uboot/wiki/FrontPage > > > > but I'm not sure how to install it yet. Will try

  1   2   3   4   5   6   >