[PATCH] sched/deadline: make function ‘grub_reclaim’ static

Since function ‘grub_reclaim’ can be made static, make it so. Silence the following gcc warning (W=1): kernel/sched/deadline.c:1120:5: warning: no previous prototype for ‘grub_reclaim’ [-Wmissing-prototypes] Signed-off-by: Mathieu Malaterre --- kernel/sched/deadline.c | 2

[PATCH] sched/deadline: make function ‘grub_reclaim’ static

Since function ‘grub_reclaim’ can be made static, make it so. Silence the following gcc warning (W=1): kernel/sched/deadline.c:1120:5: warning: no previous prototype for ‘grub_reclaim’ [-Wmissing-prototypes] Signed-off-by: Mathieu Malaterre --- kernel/sched/deadline.c | 2 +- 1 file

Re: [PATCH v4 0/8] Introduce the for_each_set_clump macro

On Wed, May 16, 2018 at 5:03 PM, Linus Walleij wrote: > On Tue, May 15, 2018 at 6:22 PM, William Breathitt Gray > wrote: > >> For example, suppose you would like to iterate over a 16-bit integer 4 >> bits at a time, skipping over 4-bit groups

Re: [PATCH v4 0/8] Introduce the for_each_set_clump macro

On Wed, May 16, 2018 at 5:03 PM, Linus Walleij wrote: > On Tue, May 15, 2018 at 6:22 PM, William Breathitt Gray > wrote: > >> For example, suppose you would like to iterate over a 16-bit integer 4 >> bits at a time, skipping over 4-bit groups with no set bit, where >> represents the current

Re: [PATCH -mm] mm, hugetlb: Pass fault address to no page handler

On 05/16/2018 02:12 AM, Michal Hocko wrote: > On Tue 15-05-18 08:57:56, Huang, Ying wrote: >> From: Huang Ying >> >> This is to take better advantage of huge page clearing >> optimization (c79b57e462b5d, "mm: hugetlb: clear target sub-page last >> when clearing huge page").

Re: [PATCH -mm] mm, hugetlb: Pass fault address to no page handler

On 05/16/2018 02:12 AM, Michal Hocko wrote: > On Tue 15-05-18 08:57:56, Huang, Ying wrote: >> From: Huang Ying >> >> This is to take better advantage of huge page clearing >> optimization (c79b57e462b5d, "mm: hugetlb: clear target sub-page last >> when clearing huge page"). Which will clear to

Re: [PATCH v16 8/9] PCI/DPC: Unify and plumb error handling into DPC

On Wed, May 16, 2018 at 08:28:39PM +0530, p...@codeaurora.org wrote: > On 2018-05-16 18:34, Bjorn Helgaas wrote: > > On Wed, May 16, 2018 at 05:45:58PM +0530, p...@codeaurora.org wrote: > > > On 2018-05-16 16:22, Bjorn Helgaas wrote: > > > > On Wed, May 16, 2018 at 01:46:25PM +0530,

Re: [PATCH v16 8/9] PCI/DPC: Unify and plumb error handling into DPC

On Wed, May 16, 2018 at 08:28:39PM +0530, p...@codeaurora.org wrote: > On 2018-05-16 18:34, Bjorn Helgaas wrote: > > On Wed, May 16, 2018 at 05:45:58PM +0530, p...@codeaurora.org wrote: > > > On 2018-05-16 16:22, Bjorn Helgaas wrote: > > > > On Wed, May 16, 2018 at 01:46:25PM +0530,

Sometimes unusable i2c-hid devices in 4.17-rcX

Hi All, I've been running 4.16-rc7 on an XPS 9365 for some time and recently moved up to 4.17-rc5. Immediately I noticed that i2c-hid devices (both touchscreen and touchpad) were not working. Also when shutting the system down or rebooting it would just hang. (magic sysrq still worked). I

Sometimes unusable i2c-hid devices in 4.17-rcX

Hi All, I've been running 4.16-rc7 on an XPS 9365 for some time and recently moved up to 4.17-rc5. Immediately I noticed that i2c-hid devices (both touchscreen and touchpad) were not working. Also when shutting the system down or rebooting it would just hang. (magic sysrq still worked). I

[PATCH] clocksource: Move the inline keyword at the beginning of function declarations

The inline keyword was not at the beginning of the function declarations. Fix the following warnings triggered when using W=1: kernel/time/clocksource.c:456:1: warning: ‘inline’ is not at beginning of declaration [-Wold-style-declaration] kernel/time/clocksource.c:457:1: warning: ‘inline’ is

[PATCH] clocksource: Move the inline keyword at the beginning of function declarations

The inline keyword was not at the beginning of the function declarations. Fix the following warnings triggered when using W=1: kernel/time/clocksource.c:456:1: warning: ‘inline’ is not at beginning of declaration [-Wold-style-declaration] kernel/time/clocksource.c:457:1: warning: ‘inline’ is

Re: [PATCH v6 2/3] gpio: pca953x: define masks for addressing common and extended registers

> Am 16.05.2018 um 21:50 schrieb Andy Shevchenko : > > On Wed, May 16, 2018 at 8:01 PM, H. Nikolaus Schaller > wrote: >> These mask bits are to be used to map the extended register >> addreseses (which are defined for an unsupported 8-bit pcal

Re: [PATCH v6 2/3] gpio: pca953x: define masks for addressing common and extended registers

> Am 16.05.2018 um 21:50 schrieb Andy Shevchenko : > > On Wed, May 16, 2018 at 8:01 PM, H. Nikolaus Schaller > wrote: >> These mask bits are to be used to map the extended register >> addreseses (which are defined for an unsupported 8-bit pcal chip) >> to 16 and 24 bit chips (pcal6524). >> >>

[PATCH] sched/debug: Move print_rt_rq and print_dl_rq declarations to kernel/sched/sched.h

In commit 6b55c9654fcc ("sched/debug: Move print_cfs_rq() declaration to kernel/sched/sched.h"), ‘print_cfs_rq’ prototype was added to right next to prototypes for ‘print_cfs_stats’, ‘print_rt_stats’ and ‘print_dl_stats’. Update this previous commit and also move related prototypes: ‘print_rt_rq’

[PATCH] sched/debug: Move print_rt_rq and print_dl_rq declarations to kernel/sched/sched.h

In commit 6b55c9654fcc ("sched/debug: Move print_cfs_rq() declaration to kernel/sched/sched.h"), ‘print_cfs_rq’ prototype was added to right next to prototypes for ‘print_cfs_stats’, ‘print_rt_stats’ and ‘print_dl_stats’. Update this previous commit and also move related prototypes: ‘print_rt_rq’

Re: [PATCH 4.4 014/190] lockd: fix lockd shutdown race

On Tue, May 15, 2018 at 07:44:24PM +0100, Ben Hutchings wrote: > On Wed, 2018-04-11 at 20:34 +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: "J. Bruce Fields" > > > >

Re: [PATCH v6 0/3] pcal6524 extensions and fixes for pca953x driver

On Wed, May 16, 2018 at 8:01 PM, H. Nikolaus Schaller wrote: > V6: > * added proper attribution to the formula used for fixing the > pcal6524 register address (changes commit message only) > * add back missing first patch from V2 that defines the > PCA_LATCH_INT constant

Re: [PATCH 4.4 014/190] lockd: fix lockd shutdown race

On Tue, May 15, 2018 at 07:44:24PM +0100, Ben Hutchings wrote: > On Wed, 2018-04-11 at 20:34 +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: "J. Bruce Fields" > > > > > > [ Upstream

Re: [PATCH v6 0/3] pcal6524 extensions and fixes for pca953x driver

On Wed, May 16, 2018 at 8:01 PM, H. Nikolaus Schaller wrote: > V6: > * added proper attribution to the formula used for fixing the > pcal6524 register address (changes commit message only) > * add back missing first patch from V2 that defines the > PCA_LATCH_INT constant > * removed patches

Re: [PATCH v6 2/3] gpio: pca953x: define masks for addressing common and extended registers

On Wed, May 16, 2018 at 8:01 PM, H. Nikolaus Schaller wrote: > These mask bits are to be used to map the extended register > addreseses (which are defined for an unsupported 8-bit pcal chip) > to 16 and 24 bit chips (pcal6524). > > Reviewed-by: Andy Shevchenko

Re: [PATCH v6 2/3] gpio: pca953x: define masks for addressing common and extended registers

On Wed, May 16, 2018 at 8:01 PM, H. Nikolaus Schaller wrote: > These mask bits are to be used to map the extended register > addreseses (which are defined for an unsupported 8-bit pcal chip) > to 16 and 24 bit chips (pcal6524). > > Reviewed-by: Andy Shevchenko > Signed-off-by: H. Nikolaus

[PATCH] MAINTAINERS: update sound/soc/intel maintainers

The information for Intel SoC drivers was not updated for several years. Add myself, Liam and Keyon (Jie) as maintainers to get notified of contributions and bug reports. As discussed with Mark and Takashi, I'll also monitor alsa-devel and ack Intel patches as necessary. Signed-off-by:

[PATCH] MAINTAINERS: update sound/soc/intel maintainers

The information for Intel SoC drivers was not updated for several years. Add myself, Liam and Keyon (Jie) as maintainers to get notified of contributions and bug reports. As discussed with Mark and Takashi, I'll also monitor alsa-devel and ack Intel patches as necessary. Signed-off-by:

Re: [PATCH net-next 09/10] net: hns3: Add support of .sriov_configure in HNS3 driver

Hi Peng, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Salil-Mehta/Misc-Bug-Fixes-and-clean-ups-for-HNS3-Driver/20180516-211239 reproduce: # apt-get install sparse make ARCH

Re: [PATCH net-next 09/10] net: hns3: Add support of .sriov_configure in HNS3 driver

Hi Peng, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Salil-Mehta/Misc-Bug-Fixes-and-clean-ups-for-HNS3-Driver/20180516-211239 reproduce: # apt-get install sparse make ARCH

[RFC PATCH] net: hns3: hns3_pci_sriov_configure() can be static

Fixes: fdb793670a00 ("net: hns3: Add support of .sriov_configure in HNS3 driver") Signed-off-by: Fengguang Wu --- hns3_enet.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c

[RFC PATCH] net: hns3: hns3_pci_sriov_configure() can be static

Fixes: fdb793670a00 ("net: hns3: Add support of .sriov_configure in HNS3 driver") Signed-off-by: Fengguang Wu --- hns3_enet.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c

[PATCH v2 3/4] coresight: allow to build as modules

Allow to build coresight as modules. This greatly enhances developer efficiency by allowing the development to take place exclusively on the target, and without needing to reboot in between changes. - Kconfig bools become tristates, to allow =m - MODULE_* macros added: Please correct me if I'm

[PATCH v2 3/4] coresight: allow to build as modules

Allow to build coresight as modules. This greatly enhances developer efficiency by allowing the development to take place exclusively on the target, and without needing to reboot in between changes. - Kconfig bools become tristates, to allow =m - MODULE_* macros added: Please correct me if I'm

Re: [PATCH v2] vfio/mdev: Check globally for duplicate devices

On 5/16/2018 8:53 PM, Alex Williamson wrote: > When we create an mdev device, we check for duplicates against the > parent device and return -EEXIST if found, but the mdev device > namespace is global since we'll link all devices from the bus. We do > catch this later in

Re: [PATCH v2] vfio/mdev: Check globally for duplicate devices

On 5/16/2018 8:53 PM, Alex Williamson wrote: > When we create an mdev device, we check for duplicates against the > parent device and return -EEXIST if found, but the mdev device > namespace is global since we'll link all devices from the bus. We do > catch this later in

Re: [PATCH IB/core 2/2] IB/cm: Send authentic pkey in REQ msg and check eligibility of the pkeys

On 5/16/2018 3:22 PM, Håkon Bugge wrote: > But, do we need an update to IBTA (that the BTH.PKey shall be that of the > VM's Port)? Nothing in spec mentions shared (port) virtualization so that is an exercise completely left to the reader... Annex A19 is silent on this specific point but the

Re: [PATCH IB/core 2/2] IB/cm: Send authentic pkey in REQ msg and check eligibility of the pkeys

On 5/16/2018 3:22 PM, Håkon Bugge wrote: > But, do we need an update to IBTA (that the BTH.PKey shall be that of the > VM's Port)? Nothing in spec mentions shared (port) virtualization so that is an exercise completely left to the reader... Annex A19 is silent on this specific point but the

[PATCH] tracing: make function ‘ftrace_exports’ static

In commit 478409dd683d ("tracing: Add hook to function tracing for other subsystems to use"), a new function ‘ftrace_exports’ was added. Since this function can be made static, make it so. Silence the following warning triggered using W=1: kernel/trace/trace.c:2451:6: warning: no previous

[PATCH] tracing: make function ‘ftrace_exports’ static

In commit 478409dd683d ("tracing: Add hook to function tracing for other subsystems to use"), a new function ‘ftrace_exports’ was added. Since this function can be made static, make it so. Silence the following warning triggered using W=1: kernel/trace/trace.c:2451:6: warning: no previous

Re: [RFC/RFT] [PATCH 05/10] cpufreq: intel_pstate: HWP boost performance on IO Wake

On Wed, 2018-05-16 at 11:45 +0200, Rafael J. Wysocki wrote: [...] > > > + if (time_before64(time, cpu->last_io_update + 2 * > > TICK_NSEC) && > > + intel_pstate_check_boost_threhold(cpu)) > > + cpu->iowait_boost = true; > > + > > +

Re: [RFC/RFT] [PATCH 05/10] cpufreq: intel_pstate: HWP boost performance on IO Wake

On Wed, 2018-05-16 at 11:45 +0200, Rafael J. Wysocki wrote: [...] > > > + if (time_before64(time, cpu->last_io_update + 2 * > > TICK_NSEC) && > > + intel_pstate_check_boost_threhold(cpu)) > > + cpu->iowait_boost = true; > > + > > +

Re: [PATCH] cpufreq: brcmstb-avs-cpufreq: sort frequencies in ascending order

On 05/15/2018 09:32 PM, Viresh Kumar wrote: > On 15-05-18, 20:49, Markus Mayer wrote: >> From: Markus Mayer >> >> Most CPUfreq drivers (at least on ARM) seem to be sorting the available >> frequencies from lowest to highest. To match this behaviour, we reverse >> the sorting

Re: [PATCH] cpufreq: brcmstb-avs-cpufreq: sort frequencies in ascending order

On 05/15/2018 09:32 PM, Viresh Kumar wrote: > On 15-05-18, 20:49, Markus Mayer wrote: >> From: Markus Mayer >> >> Most CPUfreq drivers (at least on ARM) seem to be sorting the available >> frequencies from lowest to highest. To match this behaviour, we reverse >> the sorting order in

[PATCH] mmc: block: propagate correct returned value in mmc_rpmb_ioctl

In commit 97548575bef3 ("mmc: block: Convert RPMB to a character device") a new function `mmc_rpmb_ioctl` was added. The final return is simply returning a value of `0` instead of propagating the correct return code. Discovered during a compilation with W=1, silence the following gcc warning

[PATCH] mmc: block: propagate correct returned value in mmc_rpmb_ioctl

In commit 97548575bef3 ("mmc: block: Convert RPMB to a character device") a new function `mmc_rpmb_ioctl` was added. The final return is simply returning a value of `0` instead of propagating the correct return code. Discovered during a compilation with W=1, silence the following gcc warning

RE: [PATCH 1/2] ACPICA: Introduce acpi_dispatch_gpe()

I'm not sure why this is necessary, please explain. Is the implication here that some driver is going to poll on acpi_dispatch_gpe? Bob > -Original Message- > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Sent: Wednesday, May 16, 2018 5:12 AM > To: Linux ACPI

RE: [PATCH 1/2] ACPICA: Introduce acpi_dispatch_gpe()

I'm not sure why this is necessary, please explain. Is the implication here that some driver is going to poll on acpi_dispatch_gpe? Bob > -Original Message- > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Sent: Wednesday, May 16, 2018 5:12 AM > To: Linux ACPI > Cc: Zhang, Rui

Re: [PATCH v2] coresight: documentation: update sysfs section

On Mon, 14 May 2018 12:19:59 -0500 Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed

Re: [PATCH v2] coresight: documentation: update sysfs section

On Mon, 14 May 2018 12:19:59 -0500 Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed

Re: [PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

On 05/16/2018 12:07 PM, David Miller wrote: > From: David Miller > Date: Wed, 16 May 2018 15:06:59 -0400 (EDT) > >> So applied, thanks. > > Nevermind, eventually got a build failure: > > ERROR: "knav_queue_open" [drivers/net/ethernet/ti/keystone_netcp.ko] > undefined! >

Re: [PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

On 05/16/2018 12:07 PM, David Miller wrote: > From: David Miller > Date: Wed, 16 May 2018 15:06:59 -0400 (EDT) > >> So applied, thanks. > > Nevermind, eventually got a build failure: > > ERROR: "knav_queue_open" [drivers/net/ethernet/ti/keystone_netcp.ko] > undefined! > make[1]: ***

Re: [PATCH] Documentation: arm: clean up Marvell Berlin family info

On Mon, 14 May 2018 17:55:10 -0400 Thomas Hebb wrote: > Remove dead links, make spacing consistent, and note that the family was > acquired by Synaptics in 2017. > > Signed-off-by: Thomas Hebb Applied to the docs tree, thanks. jon

Re: [PATCH] Documentation: arm: clean up Marvell Berlin family info

On Mon, 14 May 2018 17:55:10 -0400 Thomas Hebb wrote: > Remove dead links, make spacing consistent, and note that the family was > acquired by Synaptics in 2017. > > Signed-off-by: Thomas Hebb Applied to the docs tree, thanks. jon

[PATCH] rtc: nvmem: don't return an error when not enabled

Avoid reporting an error when RTC_NVMEM is not selected. Reported-by: kernel test robot Signed-off-by: Alexandre Belloni --- include/linux/rtc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/rtc.h

[PATCH] rtc: nvmem: don't return an error when not enabled

Avoid reporting an error when RTC_NVMEM is not selected. Reported-by: kernel test robot Signed-off-by: Alexandre Belloni --- include/linux/rtc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/rtc.h b/include/linux/rtc.h index 4c007f69082f..6268208760e9 100644

Re: [PATCH] Documentation: gpio: driver: Fix a typo and some odd grammar

On Wed, 16 May 2018 14:08:00 +0200 Jonathan Neuschäfer wrote: > Signed-off-by: Jonathan Neuschäfer Applied, thanks. jon

Re: [PATCH] Documentation: gpio: driver: Fix a typo and some odd grammar

On Wed, 16 May 2018 14:08:00 +0200 Jonathan Neuschäfer wrote: > Signed-off-by: Jonathan Neuschäfer Applied, thanks. jon

Re: [PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

From: David Miller Date: Wed, 16 May 2018 15:06:59 -0400 (EDT) > So applied, thanks. Nevermind, eventually got a build failure: ERROR: "knav_queue_open" [drivers/net/ethernet/ti/keystone_netcp.ko] undefined! make[1]: *** [scripts/Makefile.modpost:92: __modpost] Error 1

[PATCH v3] {net, IB}/mlx5: Use 'kvfree()' for memory allocated by 'kvzalloc()'

When 'kvzalloc()' is used to allocate memory, 'kvfree()' must be used to free it. Fixes: 1cbe6fc86ccfe ("IB/mlx5: Add support for CQE compressing") Fixes: fed9ce22bf8ae ("net/mlx5: E-Switch, Add API to create vport rx rules") Fixes: 9efa75254593d ("net/mlx5_core: Introduce access functions to

Re: [PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

From: David Miller Date: Wed, 16 May 2018 15:06:59 -0400 (EDT) > So applied, thanks. Nevermind, eventually got a build failure: ERROR: "knav_queue_open" [drivers/net/ethernet/ti/keystone_netcp.ko] undefined! make[1]: *** [scripts/Makefile.modpost:92: __modpost] Error 1 make: ***

[PATCH v3] {net, IB}/mlx5: Use 'kvfree()' for memory allocated by 'kvzalloc()'

When 'kvzalloc()' is used to allocate memory, 'kvfree()' must be used to free it. Fixes: 1cbe6fc86ccfe ("IB/mlx5: Add support for CQE compressing") Fixes: fed9ce22bf8ae ("net/mlx5: E-Switch, Add API to create vport rx rules") Fixes: 9efa75254593d ("net/mlx5_core: Introduce access functions to

Re: [PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

From: Florian Fainelli Date: Wed, 16 May 2018 11:52:55 -0700 > This patch series includes more drivers to be build tested with COMPILE_TEST > enabled. This helps cover some of the issues I just ran into with missing > a driver *sigh*. > > Changes in v2: > > - allow FEC to

Re: [PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

From: Florian Fainelli Date: Wed, 16 May 2018 11:52:55 -0700 > This patch series includes more drivers to be build tested with COMPILE_TEST > enabled. This helps cover some of the issues I just ran into with missing > a driver *sigh*. > > Changes in v2: > > - allow FEC to build outside of

[PATCH net-next v2 1/3] net: ethernet: ti: Allow most drivers with COMPILE_TEST

Most of the TI drivers build just fine with COMPILE_TEST, cpmac (AR7) is the exception because it uses a header file from arch/mips/include/asm/mach-ar7/ar7.h. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/ti/Kconfig | 14 +++--- 1 file changed, 7

[PATCH net-next v2 1/3] net: ethernet: ti: Allow most drivers with COMPILE_TEST

Most of the TI drivers build just fine with COMPILE_TEST, cpmac (AR7) is the exception because it uses a header file from arch/mips/include/asm/mach-ar7/ar7.h. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/ti/Kconfig | 14 +++--- 1 file changed, 7 insertions(+), 7

[PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

Hi David, This patch series includes more drivers to be build tested with COMPILE_TEST enabled. This helps cover some of the issues I just ran into with missing a driver *sigh*. Changes in v2: - allow FEC to build outside of CONFIG_ARM/ARM64 by defining a layout of registers, this is not

[PATCH net-next v2 0/3] net: Allow more drivers with COMPILE_TEST

Hi David, This patch series includes more drivers to be build tested with COMPILE_TEST enabled. This helps cover some of the issues I just ran into with missing a driver *sigh*. Changes in v2: - allow FEC to build outside of CONFIG_ARM/ARM64 by defining a layout of registers, this is not

[PATCH net-next v2 3/3] net: phy: Allow MDIO_MOXART and MDIO_SUN4I with COMPILE_TEST

Those drivers build just fine with COMPILE_TEST, so make that possible. Signed-off-by: Florian Fainelli --- drivers/net/phy/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig index

[PATCH net-next v2 3/3] net: phy: Allow MDIO_MOXART and MDIO_SUN4I with COMPILE_TEST

Those drivers build just fine with COMPILE_TEST, so make that possible. Signed-off-by: Florian Fainelli --- drivers/net/phy/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig index 0e2305ccc91f..343989f9f9d9 100644

Re: [Intel-gfx] [PATCH v2 2/5] drm/i915: hdmi: add CEC notifier to intel_hdmi

Hi Ville, On 16/05/2018 16:07, Ville Syrjälä wrote: > On Wed, May 16, 2018 at 09:40:17AM +0200, Neil Armstrong wrote: >> On 16/05/2018 09:31, Neil Armstrong wrote: >>> Hi Ville, >>> >>> On 15/05/2018 17:35, Ville Syrjälä wrote: On Tue, May 15, 2018 at 04:42:19PM +0200, Neil Armstrong wrote:

[PATCH net-next v2 2/3] net: ethernet: freescale: Allow FEC with COMPILE_TEST

The Freescale FEC driver builds fine with COMPILE_TEST, so make that possible. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/freescale/Kconfig| 2 +- drivers/net/ethernet/freescale/fec.h | 2 +- drivers/net/ethernet/freescale/fec_main.c | 2 +- 3 files

Re: [PATCH net] tuntap: fix use after free during release

From: Jason Wang Date: Wed, 16 May 2018 20:39:33 +0800 > After commit b196d88aba8a ("tun: fix use after free for ptr_ring") we > need clean up tx ring during release(). But unfortunately, it tries to > do the cleanup blindly after socket were destroyed which will lead >

Re: [PATCH net] tuntap: fix use after free during release

From: Jason Wang Date: Wed, 16 May 2018 20:39:33 +0800 > After commit b196d88aba8a ("tun: fix use after free for ptr_ring") we > need clean up tx ring during release(). But unfortunately, it tries to > do the cleanup blindly after socket were destroyed which will lead > another use-after-free.

Re: [Intel-gfx] [PATCH v2 2/5] drm/i915: hdmi: add CEC notifier to intel_hdmi

Hi Ville, On 16/05/2018 16:07, Ville Syrjälä wrote: > On Wed, May 16, 2018 at 09:40:17AM +0200, Neil Armstrong wrote: >> On 16/05/2018 09:31, Neil Armstrong wrote: >>> Hi Ville, >>> >>> On 15/05/2018 17:35, Ville Syrjälä wrote: On Tue, May 15, 2018 at 04:42:19PM +0200, Neil Armstrong wrote:

[PATCH net-next v2 2/3] net: ethernet: freescale: Allow FEC with COMPILE_TEST

The Freescale FEC driver builds fine with COMPILE_TEST, so make that possible. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/freescale/Kconfig| 2 +- drivers/net/ethernet/freescale/fec.h | 2 +- drivers/net/ethernet/freescale/fec_main.c | 2 +- 3 files changed, 3

Re: [PATCH net-next] net: ethoc: Remove useless test before clk_disable_unprepare

From: YueHaibing Date: Wed, 16 May 2018 19:18:22 +0800 > clk_disable_unprepare() already checks that the clock pointer is valid. > No need to test it before calling it. > > Signed-off-by: YueHaibing Applied.

Re: [PATCH net-next] net: ethoc: Remove useless test before clk_disable_unprepare

From: YueHaibing Date: Wed, 16 May 2018 19:18:22 +0800 > clk_disable_unprepare() already checks that the clock pointer is valid. > No need to test it before calling it. > > Signed-off-by: YueHaibing Applied.

Re: [PATCH net-next] net: stmmac: Remove useless test before clk_disable_unprepare

From: YueHaibing Date: Wed, 16 May 2018 18:59:19 +0800 > clk_disable_unprepare() already checks that the clock pointer is valid. > No need to test it before calling it. > > Signed-off-by: YueHaibing Applied.

Re: [PATCH net-next] net: stmmac: Remove useless test before clk_disable_unprepare

From: YueHaibing Date: Wed, 16 May 2018 18:59:19 +0800 > clk_disable_unprepare() already checks that the clock pointer is valid. > No need to test it before calling it. > > Signed-off-by: YueHaibing Applied.

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 5/16/2018 2:31 PM, Timur Tabi wrote: > On 05/16/2018 01:23 PM, Sinan Kaya wrote: >> +    win_start = window->res->start - window->offset; > > Can you guarantee that window->res->start is always >= window->offset? > Resource offset is generally 0 when not translating or a positive number

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 5/16/2018 2:31 PM, Timur Tabi wrote: > On 05/16/2018 01:23 PM, Sinan Kaya wrote: >> +    win_start = window->res->start - window->offset; > > Can you guarantee that window->res->start is always >= window->offset? > Resource offset is generally 0 when not translating or a positive number

Re: [PATCH] net: 8390: ne: Fix accidentally removed RBTX4927 support

From: Geert Uytterhoeven Date: Wed, 16 May 2018 11:18:01 +0200 > The configuration settings for RBTX4927 were accidentally removed, > leading to a silently broken network interface. > > Re-add the missing settings to fix this. > > Fixes: 8eb97ff5a4ec941d ("net: 8390:

Re: [PATCH] net: 8390: ne: Fix accidentally removed RBTX4927 support

From: Geert Uytterhoeven Date: Wed, 16 May 2018 11:18:01 +0200 > The configuration settings for RBTX4927 were accidentally removed, > leading to a silently broken network interface. > > Re-add the missing settings to fix this. > > Fixes: 8eb97ff5a4ec941d ("net: 8390: remove m32r specific

Re: [PATCH V1 06/19] perf tools: Fix kernel_start for PTI on x86

Em Wed, May 16, 2018 at 09:16:57PM +0300, Adrian Hunter escreveu: > On 05/16/2018 04:55 PM, Arnaldo Carvalho de Melo wrote: > > Em Wed, May 16, 2018 at 04:45:41PM +0300, Adrian Hunter escreveu: > >> On 16/05/18 16:00, Arnaldo Carvalho de Melo wrote: > >>> 2303 bool machine__is(struct machine

Re: [PATCH V1 06/19] perf tools: Fix kernel_start for PTI on x86

Em Wed, May 16, 2018 at 09:16:57PM +0300, Adrian Hunter escreveu: > On 05/16/2018 04:55 PM, Arnaldo Carvalho de Melo wrote: > > Em Wed, May 16, 2018 at 04:45:41PM +0300, Adrian Hunter escreveu: > >> On 16/05/18 16:00, Arnaldo Carvalho de Melo wrote: > >>> 2303 bool machine__is(struct machine

Re: [PATCH] net: qcom/emac: Encapsulate sgmii ops under one structure

From: Hemanth Puranik Date: Wed, 16 May 2018 06:40:53 +0530 > This patch introduces ops structure for sgmii, This by ensures that > we do not need dummy functions in case of emulation platforms. > > Signed-off-by: Hemanth Puranik Applied to

Re: [PATCH] net: qcom/emac: Encapsulate sgmii ops under one structure

From: Hemanth Puranik Date: Wed, 16 May 2018 06:40:53 +0530 > This patch introduces ops structure for sgmii, This by ensures that > we do not need dummy functions in case of emulation platforms. > > Signed-off-by: Hemanth Puranik Applied to net-next.

Re: [PATCH net-next v2 0/2] of: mdio: Fall back to mdiobus_register() with NULL device_node

Hi David, On Wed, May 16, 2018 at 8:21 PM, David Miller wrote: > From: Florian Fainelli > Date: Tue, 15 May 2018 16:56:17 -0700 > >> This patch series updates of_mdiobus_register() such that when the >> device_node >> argument is NULL, it calls

Re: [PATCH net-next v2 0/2] of: mdio: Fall back to mdiobus_register() with NULL device_node

Hi David, On Wed, May 16, 2018 at 8:21 PM, David Miller wrote: > From: Florian Fainelli > Date: Tue, 15 May 2018 16:56:17 -0700 > >> This patch series updates of_mdiobus_register() such that when the >> device_node >> argument is NULL, it calls mdiobus_register() directly. This is consistent

[BUG] net: stmmac: dwmac-sun8i broken in linux-next

Hello The dwmac-sun8i driver is broken in next-20180515, symptom are no RX and TX errors as shown by ifconfig: eth0: flags=4163 mtu 1500 inet 192.168.1.204 netmask 255.255.255.0 broadcast 192.168.1.255 ether 96:75:ff:0d:f6:d8 txqueuelen 1000

[BUG] net: stmmac: dwmac-sun8i broken in linux-next

Hello The dwmac-sun8i driver is broken in next-20180515, symptom are no RX and TX errors as shown by ifconfig: eth0: flags=4163 mtu 1500 inet 192.168.1.204 netmask 255.255.255.0 broadcast 192.168.1.255 ether 96:75:ff:0d:f6:d8 txqueuelen 1000 (Ethernet) RX packets 0

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 05/16/2018 01:23 PM, Sinan Kaya wrote: + win_start = window->res->start - window->offset; Can you guarantee that window->res->start is always >= window->offset? + win_size = window->res->end - window->res->start + 1; Use resource_size() instead. -- Qualcomm

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 05/16/2018 01:23 PM, Sinan Kaya wrote: + win_start = window->res->start - window->offset; Can you guarantee that window->res->start is always >= window->offset? + win_size = window->res->end - window->res->start + 1; Use resource_size() instead. -- Qualcomm

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 5/16/2018 2:23 PM, Sinan Kaya wrote: > + if (win_start <= base && win_end >= base + win_size - 1) { > + base += window->offset; > + break; > + } I should probably add window->offset!=0 to the if statement in order not to break

Re: [RFC PATCH] efi/fb: Convert PCI bus address to resource if translated by the bridge

On 5/16/2018 2:23 PM, Sinan Kaya wrote: > + if (win_start <= base && win_end >= base + win_size - 1) { > + base += window->offset; > + break; > + } I should probably add window->offset!=0 to the if statement in order not to break

[PATCH 5/5] staging: lustre: Fix "from from"->"from"

Trivial fix to spelling mistake in README.txt Signed-off-by: Sabin Mihai Rapan --- drivers/staging/lustre/README.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/lustre/README.txt b/drivers/staging/lustre/README.txt index

[PATCH 5/5] staging: lustre: Fix "from from"->"from"

Trivial fix to spelling mistake in README.txt Signed-off-by: Sabin Mihai Rapan --- drivers/staging/lustre/README.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/lustre/README.txt b/drivers/staging/lustre/README.txt index 0676243eea9e..783959240490 100644

[PATCH 4/5] staging: lustre: Fix "Possible intergrate"->"Possibly integrate"

Trivial fix to spelling mistake in TODO file. Signed-off-by: Sabin Mihai Rapan --- drivers/staging/lustre/TODO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/lustre/TODO b/drivers/staging/lustre/TODO index 94446487748a..5332cdb19bfa

[PATCH 4/5] staging: lustre: Fix "Possible intergrate"->"Possibly integrate"

Trivial fix to spelling mistake in TODO file. Signed-off-by: Sabin Mihai Rapan --- drivers/staging/lustre/TODO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/lustre/TODO b/drivers/staging/lustre/TODO index 94446487748a..5332cdb19bfa 100644 ---

[PATCH 3/5] staging: lustre: Fix "unsigned"->"unsigned int"

This patch fixes the checkpatch.pl warning: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' Signed-off-by: Sabin Mihai Rapan --- .../staging/lustre/include/uapi/linux/lustre/lustre_fiemap.h| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 3/5] staging: lustre: Fix "unsigned"->"unsigned int"

This patch fixes the checkpatch.pl warning: WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned' Signed-off-by: Sabin Mihai Rapan --- .../staging/lustre/include/uapi/linux/lustre/lustre_fiemap.h| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/5] staging: lustre: Fix inclusion of local headers

This patch fixes the checkpatch.pl error: ERROR:UAPI_INCLUDE: No #include in ...include/uapi/... should use a uapi/ path prefix Signed-off-by: Sabin Mihai Rapan --- drivers/staging/lustre/include/uapi/linux/lnet/lnet-dlc.h | 4 ++--

[PATCH 1/5] staging: lustre: Fix inclusion of local headers

This patch fixes the checkpatch.pl error: ERROR:UAPI_INCLUDE: No #include in ...include/uapi/... should use a uapi/ path prefix Signed-off-by: Sabin Mihai Rapan --- drivers/staging/lustre/include/uapi/linux/lnet/lnet-dlc.h | 4 ++-- drivers/staging/lustre/include/uapi/linux/lnet/lnetctl.h

<    1   2   3   4   5   6   7   8   9   10   >