Re: Problem with setxattr on sockfs with Smack after 971df15bd54ad46e907046ff33750a137b2f0096

On 10/31/2016 2:55 PM, Casey Schaufler wrote: > Smack has always used extended attributes to identify > the security information used to make access control > decisions on packet delivery. The two attributes > security.SMACK64_IPIN and security.SMACK64_IPOUT > contain the label used for inbound

Re: Problem with setxattr on sockfs with Smack after 971df15bd54ad46e907046ff33750a137b2f0096

On 10/31/2016 2:55 PM, Casey Schaufler wrote: > Smack has always used extended attributes to identify > the security information used to make access control > decisions on packet delivery. The two attributes > security.SMACK64_IPIN and security.SMACK64_IPOUT > contain the label used for inbound

[PATCH 08/14] pinctrl-sx150x: Replace sx150x_*_cfg by means of regmap API

The difference between 8 and 16 pin GPIO expanders can be accomodated by the means of regmap API without resorting to usaing driver-specific read/write accessors. This change, IMHO, brings the following benefits: - Replaces driver's idiosyncratic way of dealing with

[PATCH 02/14] pinctrl-sx150x: Add SX1503 specific data

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 24 1 file changed, 24 insertions(+) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index 41b9e6a..e0f52e4 100644 ---

[PATCH 08/14] pinctrl-sx150x: Replace sx150x_*_cfg by means of regmap API

The difference between 8 and 16 pin GPIO expanders can be accomodated by the means of regmap API without resorting to usaing driver-specific read/write accessors. This change, IMHO, brings the following benefits: - Replaces driver's idiosyncratic way of dealing with

[PATCH 02/14] pinctrl-sx150x: Add SX1503 specific data

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 24 1 file changed, 24 insertions(+) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index 41b9e6a..e0f52e4 100644 --- a/drivers/pinctrl/pinctrl-sx150x.c +++

[PATCH 01/14] pinctrl-sx150x: Rely on of_modalias_node for OF matching

None of the OF match table entries contain any compatiblity strings that could not be matched against using i2c_device_id table above and of_modalias_node. Besides that entries in OF match table do not cary proper device variant information which is need by the drive. Those two facts combined,

[PATCH 07/14] pinctrl-sx150x: Convert driver to use regmap API

To allow for future code simplification Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 102 +-- 1 file changed, 56 insertions(+), 46 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c

[PATCH 01/14] pinctrl-sx150x: Rely on of_modalias_node for OF matching

None of the OF match table entries contain any compatiblity strings that could not be matched against using i2c_device_id table above and of_modalias_node. Besides that entries in OF match table do not cary proper device variant information which is need by the drive. Those two facts combined,

[PATCH 07/14] pinctrl-sx150x: Convert driver to use regmap API

To allow for future code simplification Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 102 +-- 1 file changed, 56 insertions(+), 46 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index

[PATCH 04/14] pinctrl-sx150x: Fix incorrect constant in sx150x_init_hw

According to the datasheet for SX1504/5/6, RegAdvanced's "Autoclear NINT" bit that turns the feature when set and disables it when cleared, so writing 0x04 to the register will have the opposite from desirable effect. Signed-off-by: Andrey Smirnov ---

[PATCH 06/14] pinctrl-sx150x: Improve sx150x_init_misc for SX1504/5/6

For Sx1504/5/6 only SX1506 has RegAdvanced, so put some code in place to account for that. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/pinctrl/pinctrl-sx150x.c

[PATCH 04/14] pinctrl-sx150x: Fix incorrect constant in sx150x_init_hw

According to the datasheet for SX1504/5/6, RegAdvanced's "Autoclear NINT" bit that turns the feature when set and disables it when cleared, so writing 0x04 to the register will have the opposite from desirable effect. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 2 +- 1

[PATCH 06/14] pinctrl-sx150x: Improve sx150x_init_misc for SX1504/5/6

For Sx1504/5/6 only SX1506 has RegAdvanced, so put some code in place to account for that. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index

[PATCH 11/14] pinctrl-sx150x: Simplify interrupt handler

Make use of for_each_set_bit macro and reduce boilerplate code. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 18 ++ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c

[PATCH 10/14] pinctrl-sx150x: Improve oscio GPIO functions

Move actual code that configures oscio pin into a separate function and use it instead of calling sx150x_gpio_set to avoid calling sx150x_pin_is_oscio twice and correctly propagte error code in sx150x_gpio_direction_output. Signed-off-by: Andrey Smirnov ---

[PATCH 03/14] pinctrl-sx150x: Replace magic number in sx150x_init_hw

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index e0f52e4..f4481fb 100644 ---

[PATCH 11/14] pinctrl-sx150x: Simplify interrupt handler

Make use of for_each_set_bit macro and reduce boilerplate code. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 18 ++ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index

[PATCH 10/14] pinctrl-sx150x: Improve oscio GPIO functions

Move actual code that configures oscio pin into a separate function and use it instead of calling sx150x_gpio_set to avoid calling sx150x_pin_is_oscio twice and correctly propagte error code in sx150x_gpio_direction_output. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 18

[PATCH 03/14] pinctrl-sx150x: Replace magic number in sx150x_init_hw

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index e0f52e4..f4481fb 100644 --- a/drivers/pinctrl/pinctrl-sx150x.c +++

[PATCH 12/14] pinctrl-sx150x: Use handle_bad_irq instead of handle_edge_irq

Althought the function passed as a "handler" during GPIO chip instantiation is not going to ever be called, specifying handle_edge_irq there makes for a rather confusing read, both because no "ack" callback in specified for irqchip and because there's no acking action is necessary. Specify

[PATCH 12/14] pinctrl-sx150x: Use handle_bad_irq instead of handle_edge_irq

Althought the function passed as a "handler" during GPIO chip instantiation is not going to ever be called, specifying handle_edge_irq there makes for a rather confusing read, both because no "ack" callback in specified for irqchip and because there's no acking action is necessary. Specify

[PATCH 13/14] pinctrl-sx150x: Remove magic numbers from sx150x_irq_set_type

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 24 1 file changed, 20 insertions(+), 4 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index 31ed7e3..13afcb9 100644 ---

Re: [char-misc:char-misc-testing] warning

Hi Tobias, On Tue, 1 Nov 2016 16:33:03 +0100 Tobias Jakobi wrote: > Hello Robin, > > I'm afraid I can't help you with that. The series was done as a request > by Daniel Vetter, see here for reference: > http://www.spinics.net/lists/dri-devel/msg113011.html So.. I

[PATCH 05/14] pinctrl-sx150x: Move some code out of sx150x_init_hw

Move the code configuring explicit IRQ acking into a standalone function to declutter sx150x_init_hw a bit and make that code somewhat less repetitious. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 38 ++ 1

[PATCH 13/14] pinctrl-sx150x: Remove magic numbers from sx150x_irq_set_type

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 24 1 file changed, 20 insertions(+), 4 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index 31ed7e3..13afcb9 100644 ---

Re: [char-misc:char-misc-testing] warning

Hi Tobias, On Tue, 1 Nov 2016 16:33:03 +0100 Tobias Jakobi wrote: > Hello Robin, > > I'm afraid I can't help you with that. The series was done as a request > by Daniel Vetter, see here for reference: > http://www.spinics.net/lists/dri-devel/msg113011.html So.. I should contact Daniel Vetter

[PATCH 05/14] pinctrl-sx150x: Move some code out of sx150x_init_hw

Move the code configuring explicit IRQ acking into a standalone function to declutter sx150x_init_hw a bit and make that code somewhat less repetitious. Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 38 ++ 1 file changed, 26

Re: [PATCH v2 2/6] net: phy: broadcom: Add BCM54810 PHY entry

On Sat, Oct 29, 2016 at 10:18:39AM +0200, Andrew Lunn wrote: > On Fri, Oct 28, 2016 at 04:56:55PM -0400, Jon Mason wrote: > > The BCM54810 PHY requires some semi-unique configuration, which results > > in some additional configuration in addition to the standard config. > > Also, some users of the

Re: [PATCH v2 2/6] net: phy: broadcom: Add BCM54810 PHY entry

On Sat, Oct 29, 2016 at 10:18:39AM +0200, Andrew Lunn wrote: > On Fri, Oct 28, 2016 at 04:56:55PM -0400, Jon Mason wrote: > > The BCM54810 PHY requires some semi-unique configuration, which results > > in some additional configuration in addition to the standard config. > > Also, some users of the

[PATCH -next] mfd: intel_soc_pmic_bxtwc: Fix a typo in MODULE_DEVICE_TABLE()

From: Wei Yongjun Fix a typo in MODULE_DEVICE_TABLE(). 'pmic_acpi_ids' should be 'bxtwc_acpi_ids'. Signed-off-by: Wei Yongjun --- drivers/mfd/intel_soc_pmic_bxtwc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH -next] mfd: intel_soc_pmic_bxtwc: Fix a typo in MODULE_DEVICE_TABLE()

From: Wei Yongjun Fix a typo in MODULE_DEVICE_TABLE(). 'pmic_acpi_ids' should be 'bxtwc_acpi_ids'. Signed-off-by: Wei Yongjun --- drivers/mfd/intel_soc_pmic_bxtwc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mfd/intel_soc_pmic_bxtwc.c

[PATCH] sdhci-esdhc-imx: fix bus-width for 1-bit operation.

From: Leonardo Graboski Veiga The 1-bit operation mode, enabled by seeting the 'bus-width' property of the device tree 'esdhc' node to <1>, not work while using SD card. The behavior is only noticed when only the data pin 0 is connected to the hardware. A series of

[PATCH] sdhci-esdhc-imx: fix bus-width for 1-bit operation.

From: Leonardo Graboski Veiga The 1-bit operation mode, enabled by seeting the 'bus-width' property of the device tree 'esdhc' node to <1>, not work while using SD card. The behavior is only noticed when only the data pin 0 is connected to the hardware. A series of kernel errors are printed to

[PATCH 09/14] pinctrl-sx150x: Remove excessive locking

Gpiochip and irqchip aspects of this driver do not access any shared registers on the chip itself and atomicity of various regmap operations is ensured by that API's implementation, so there doesn't seem to be a reason to hold the lock in as many places as it is held now. Signed-off-by: Andrey

[PATCH 09/14] pinctrl-sx150x: Remove excessive locking

Gpiochip and irqchip aspects of this driver do not access any shared registers on the chip itself and atomicity of various regmap operations is ensured by that API's implementation, so there doesn't seem to be a reason to hold the lock in as many places as it is held now. Signed-off-by: Andrey

[PATCH 00/14] pinctrl-sx150x: Various bug-fixes and code simplifications

Linus, Neil: I've had some help and got my hardware setup modified to enable IRQ functionality testing, so ended up looking at the code of SX150x more resulting in some code improvements (hopefully) and bugfixes. There are many small changes each of which is probably better described by

[PATCH 00/14] pinctrl-sx150x: Various bug-fixes and code simplifications

Linus, Neil: I've had some help and got my hardware setup modified to enable IRQ functionality testing, so ended up looking at the code of SX150x more resulting in some code improvements (hopefully) and bugfixes. There are many small changes each of which is probably better described by

[PATCH 14/14] pinctrl-sx150x: Remove magic numbers from sx150x_reset

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index 13afcb9..580a6de 100644 ---

[PATCH 14/14] pinctrl-sx150x: Remove magic numbers from sx150x_reset

Signed-off-by: Andrey Smirnov --- drivers/pinctrl/pinctrl-sx150x.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c index 13afcb9..580a6de 100644 --- a/drivers/pinctrl/pinctrl-sx150x.c +++

Re: [PATCH] kbuild: add %/built-in.o target in top Makefile

Hi, hope someone like this :-) On Mon, Oct 24, 2016 at 12:45:11PM +, Wei Yang wrote: >Current kbuild just supports building built-in.o in second directory level >individually. There is no rule to build those built-in.o targets below >third directory level. > >Even current kbuild system could

Re: [PATCH] kbuild: add %/built-in.o target in top Makefile

Hi, hope someone like this :-) On Mon, Oct 24, 2016 at 12:45:11PM +, Wei Yang wrote: >Current kbuild just supports building built-in.o in second directory level >individually. There is no rule to build those built-in.o targets below >third directory level. > >Even current kbuild system could

Re: please, where has xconfig KConf option documentation gone with linux 4.8's Qt5 / Qt4 xconfig ?

On 11/01/16 05:17, Boris Barbulovski wrote: > hi Randy, > > Frankly I don't have answer to your questions, but I did reproduced > the issues you described. > > And found that: > > * `Show Debug Info` menu item was(created, but) not added to the menu. > * if the `showDebug` setting was set to

Re: please, where has xconfig KConf option documentation gone with linux 4.8's Qt5 / Qt4 xconfig ?

On 11/01/16 05:17, Boris Barbulovski wrote: > hi Randy, > > Frankly I don't have answer to your questions, but I did reproduced > the issues you described. > > And found that: > > * `Show Debug Info` menu item was(created, but) not added to the menu. > * if the `showDebug` setting was set to

[PATCH] x86/boot: reduce one instruction by adding delta to gdtr's base address

%ebp contains the address where it is loaded and gdtr's base address is already set to "gdt" in compilation. It is fine to get the correct base address by adding the delta to gdtr's base address. This patch fixes the gdtr's base address by adding delta to it and saves one instruction.

[PATCH] x86/boot: reduce one instruction by adding delta to gdtr's base address

%ebp contains the address where it is loaded and gdtr's base address is already set to "gdt" in compilation. It is fine to get the correct base address by adding the delta to gdtr's base address. This patch fixes the gdtr's base address by adding delta to it and saves one instruction.

Re: [GIT PULL] kbuild changes for v4.9-rc1

On 2016-10-18 03:34, Nicholas Piggin wrote: > Hi Adam, > > Thanks, this is looking good. powerpc will be able to use the generic > header. > > On Tue, 18 Oct 2016 02:16:26 +0200 > Adam Borowski wrote: > >> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:

Re: [GIT PULL] kbuild changes for v4.9-rc1

On 2016-10-18 03:34, Nicholas Piggin wrote: > Hi Adam, > > Thanks, this is looking good. powerpc will be able to use the generic > header. > > On Tue, 18 Oct 2016 02:16:26 +0200 > Adam Borowski wrote: > >> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote: +#include

Re: [PATCH net-next 5/5] ipv6: Compute multipath hash for forwarded ICMP errors from offending packet

On Mon, Oct 31, 2016 at 07:25 PM GMT, Tom Herbert wrote: > On Sun, Oct 30, 2016 at 6:03 AM, Jakub Sitnicki wrote: >> On Fri, Oct 28, 2016 at 02:25 PM GMT, Tom Herbert wrote: >>> >>> If this patch is being done to be compatible with IPv4 I guess that's >>> okay, but it would be

Re: [PATCH net-next 5/5] ipv6: Compute multipath hash for forwarded ICMP errors from offending packet

On Mon, Oct 31, 2016 at 07:25 PM GMT, Tom Herbert wrote: > On Sun, Oct 30, 2016 at 6:03 AM, Jakub Sitnicki wrote: >> On Fri, Oct 28, 2016 at 02:25 PM GMT, Tom Herbert wrote: >>> >>> If this patch is being done to be compatible with IPv4 I guess that's >>> okay, but it would be false advertisement

Re: [RFC 1/3] regulator: core: Add over current changed event

Hi Mark, On Mon, Oct 31, 2016 at 5:22 PM, Mark Brown wrote: > On Sun, Oct 30, 2016 at 01:02:21PM +0100, Axel Haslam wrote: > >> The event REGULATOR_EVENT_OVER_CURRENT allready exists. >> what is missing and what i would need form the usb driver, is a way for >> the consumer

Re: [RFC 1/3] regulator: core: Add over current changed event

Hi Mark, On Mon, Oct 31, 2016 at 5:22 PM, Mark Brown wrote: > On Sun, Oct 30, 2016 at 01:02:21PM +0100, Axel Haslam wrote: > >> The event REGULATOR_EVENT_OVER_CURRENT allready exists. >> what is missing and what i would need form the usb driver, is a way for >> the consumer to know that the

Re: [PATCH] PCI: create revision file in sysfs

On Tue, Nov 1, 2016 at 11:42 AM, Emil Velikov wrote: > From: Emil Velikov > > Currently the revision isn't available via sysfs/libudev thus if one > wants to know the value they need to read through the config file. > > This in itself

Re: [PATCH] PCI: create revision file in sysfs

On Tue, Nov 1, 2016 at 11:42 AM, Emil Velikov wrote: > From: Emil Velikov > > Currently the revision isn't available via sysfs/libudev thus if one > wants to know the value they need to read through the config file. > > This in itself wakes/powers up the device, causing unwanted delay > since it

[PATCH] perf/x86: Fix overlap counter scheduling bug

My fuzzer testing hits following warning in the counter scheduling code: WARNING: CPU: 0 PID: 0 at arch/x86/events/core.c:718 perf_assign_events+0x2ae/0x2c0 Call Trace: dump_stack+0x68/0x93 __warn+0xcb/0xf0 warn_slowpath_null+0x1d/0x20 perf_assign_events+0x2ae/0x2c0

[PATCH] perf/x86: Fix overlap counter scheduling bug

My fuzzer testing hits following warning in the counter scheduling code: WARNING: CPU: 0 PID: 0 at arch/x86/events/core.c:718 perf_assign_events+0x2ae/0x2c0 Call Trace: dump_stack+0x68/0x93 __warn+0xcb/0xf0 warn_slowpath_null+0x1d/0x20 perf_assign_events+0x2ae/0x2c0

[PATCH] PCI: create revision file in sysfs

From: Emil Velikov Currently the revision isn't available via sysfs/libudev thus if one wants to know the value they need to read through the config file. This in itself wakes/powers up the device, causing unwanted delay since it can be quite costly. Expose the

[PATCH] PCI: create revision file in sysfs

From: Emil Velikov Currently the revision isn't available via sysfs/libudev thus if one wants to know the value they need to read through the config file. This in itself wakes/powers up the device, causing unwanted delay since it can be quite costly. Expose the revision as a separate file,

Re: [PATCH/RESEND V4 2/3] ARM64 LPC: Add missing range exception for special ISA

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/zhichang-yuan/ARM64-LPC-legacy-ISA-I-O-support/20161101-211425 base: https://git.kernel.org/

Re: [PATCH/RESEND V4 2/3] ARM64 LPC: Add missing range exception for special ISA

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/zhichang-yuan/ARM64-LPC-legacy-ISA-I-O-support/20161101-211425 base: https://git.kernel.org/

Re: [PATCH v4] media: Driver for Toshiba et8ek8 5MP sensor

Hi! > > I'll have to go through the patches, et8ek8 driver is probably not > > enough to get useful video. platform/video-bus-switch.c is needed for > > camera switching, then some omap3isp patches to bind flash and > > autofocus into the subdevice. > > > > Then, device tree support on n900 can

Re: [PATCH v4] media: Driver for Toshiba et8ek8 5MP sensor

Hi! > > I'll have to go through the patches, et8ek8 driver is probably not > > enough to get useful video. platform/video-bus-switch.c is needed for > > camera switching, then some omap3isp patches to bind flash and > > autofocus into the subdevice. > > > > Then, device tree support on n900 can

Re: [PATCH net-next 5/5] ipv6: Compute multipath hash for forwarded ICMP errors from offending packet

From: Jakub Sitnicki Date: Tue, 01 Nov 2016 16:13:51 +0100 > On Mon, Oct 31, 2016 at 07:15 PM GMT, David Miller wrote: >> From: Jakub Sitnicki >> Date: Sun, 30 Oct 2016 14:03:11 +0100 >> >>> 2) ensure the flow labels used in both directions are the same (either

Re: [PATCH net-next 5/5] ipv6: Compute multipath hash for forwarded ICMP errors from offending packet

From: Jakub Sitnicki Date: Tue, 01 Nov 2016 16:13:51 +0100 > On Mon, Oct 31, 2016 at 07:15 PM GMT, David Miller wrote: >> From: Jakub Sitnicki >> Date: Sun, 30 Oct 2016 14:03:11 +0100 >> >>> 2) ensure the flow labels used in both directions are the same (either >>>reflected by one side, or

[PATCH 3/3] net: 3c509: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/3com/3c509.c | 55 +++- 1 files changed, 29 insertions(+), 26 deletions(-)

[PATCH 3/3] net: 3c509: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/3com/3c509.c | 55 +++- 1 files changed, 29 insertions(+), 26 deletions(-) diff --git

[PATCH 1/3] net: mii: add generic function to support ksetting support

The old ethtool api (get_setting and set_setting) has generic mii functions mii_ethtool_sset and mii_ethtool_gset. To support the new ethtool api ({get|set}_link_ksettings), we add two generics mii function mii_ethtool_{get|set}_link_ksettings_get. Signed-off-by: Philippe Reynes

[PATCH 1/3] net: mii: add generic function to support ksetting support

The old ethtool api (get_setting and set_setting) has generic mii functions mii_ethtool_sset and mii_ethtool_gset. To support the new ethtool api ({get|set}_link_ksettings), we add two generics mii function mii_ethtool_{get|set}_link_ksettings_get. Signed-off-by: Philippe Reynes ---

Re: [char-misc:char-misc-testing] warning

Hello Robin, I'm afraid I can't help you with that. The series was done as a request by Daniel Vetter, see here for reference: http://www.spinics.net/lists/dri-devel/msg113011.html I don't have any nouveau platform here. With best wishes, Tobias Robin van der Gracht wrote: > Hi Tobias, > >

Re: [char-misc:char-misc-testing] warning

Hello Robin, I'm afraid I can't help you with that. The series was done as a request by Daniel Vetter, see here for reference: http://www.spinics.net/lists/dri-devel/msg113011.html I don't have any nouveau platform here. With best wishes, Tobias Robin van der Gracht wrote: > Hi Tobias, > >

[PATCH 2/3] net: 3c59x: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/3com/3c59x.c | 14 -- 1 files changed, 8 insertions(+), 6 deletions(-) diff --git

[PATCH 2/3] net: 3c59x: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/3com/3c59x.c | 14 -- 1 files changed, 8 insertions(+), 6 deletions(-) diff --git a/drivers/net/ethernet/3com/3c59x.c

Re: [PATCH v10 00/19] Add Mediated device support

Hi, > I rebased KVMGT upon v10, with 2 minor changes: > > 1, get_user_pages_remote has only 7 args Appears to be a 4.9 merge window change. v10 as-is applies and builds fine against 4.8, after rebasing to 4.9-rc3 it stops building due to this. Can you share the patch? > 2, vfio

Re: [PATCH v10 00/19] Add Mediated device support

Hi, > I rebased KVMGT upon v10, with 2 minor changes: > > 1, get_user_pages_remote has only 7 args Appears to be a 4.9 merge window change. v10 as-is applies and builds fine against 4.8, after rebasing to 4.9-rc3 it stops building due to this. Can you share the patch? > 2, vfio

[PATCH] NVMe: Call nvme_pci_disable on error path of nvme_probe_work

Commit d5537e988eec ("NVMe: Don't unmap controller registers on reset"), introduced a regression in which it did not replace nvme_dev_unmap() with nvme_pci_disable() in the error path of nvme_probe_work(). This led to the following NVMe driver crash on systems where the devices did not initialise

[PATCH] NVMe: Call nvme_pci_disable on error path of nvme_probe_work

Commit d5537e988eec ("NVMe: Don't unmap controller registers on reset"), introduced a regression in which it did not replace nvme_dev_unmap() with nvme_pci_disable() in the error path of nvme_probe_work(). This led to the following NVMe driver crash on systems where the devices did not initialise

[PATCH] USB: fix typo in documentation

A typo sneaked in the latest change on the USB documentation. Fixing it and also a trailing whitespace since it is also in the "USB Host-Side API Model" chapter. Signed-off-by: Luis de Bethencourt --- Documentation/DocBook/usb.tmpl | 4 ++-- 1 file changed, 2

[PATCH] USB: fix typo in documentation

A typo sneaked in the latest change on the USB documentation. Fixing it and also a trailing whitespace since it is also in the "USB Host-Side API Model" chapter. Signed-off-by: Luis de Bethencourt --- Documentation/DocBook/usb.tmpl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH] staging: vc04_services: parse_rx_slots() - Fix compiler warning

vc04_services contains a debug logging mechanism. The log is maintained in a shared memory area between the kernel and the firmware. Changing the sizes of the data in this area would require a firmware change which is distributed independently from the kernel binary. One of the items logged is

[PATCH] staging: vc04_services: parse_rx_slots() - Fix compiler warning

vc04_services contains a debug logging mechanism. The log is maintained in a shared memory area between the kernel and the firmware. Changing the sizes of the data in this area would require a firmware change which is distributed independently from the kernel binary. One of the items logged is

Re: [PATCH net-next 5/5] ipv6: Compute multipath hash for forwarded ICMP errors from offending packet

On Mon, Oct 31, 2016 at 07:15 PM GMT, David Miller wrote: > From: Jakub Sitnicki > Date: Sun, 30 Oct 2016 14:03:11 +0100 > >> 2) ensure the flow labels used in both directions are the same (either >>reflected by one side, or fixed, e.g. not used and set to 0), so that >>

RE: [PATCH v2] Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Tuesday, November 1, 2016 9:34 AM > To: de...@linuxdriverproject.org > Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; > Haiyang Zhang ; Van De Ven, Arjan >

Re: [PATCH net-next 5/5] ipv6: Compute multipath hash for forwarded ICMP errors from offending packet

On Mon, Oct 31, 2016 at 07:15 PM GMT, David Miller wrote: > From: Jakub Sitnicki > Date: Sun, 30 Oct 2016 14:03:11 +0100 > >> 2) ensure the flow labels used in both directions are the same (either >>reflected by one side, or fixed, e.g. not used and set to 0), so that >>the 4-tuple we

RE: [PATCH v2] Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Tuesday, November 1, 2016 9:34 AM > To: de...@linuxdriverproject.org > Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; > Haiyang Zhang ; Van De Ven, Arjan > > Subject: [PATCH v2] Drivers: hv: vmbus:

Re: [RFC 1/2] mmc: sdhci: dt: Add device tree properties sdhci-caps and sdhci-caps-mask

On Tue, Nov 01, 2016 at 07:13:29AM +0900, Jaehoon Chung wrote: > On 10/31/2016 09:34 PM, Adrian Hunter wrote: > > On 31/10/16 13:59, Jaehoon Chung wrote: > >> On 10/28/2016 05:12 PM, Ulf Hansson wrote: > >>> On 25 October 2016 at 21:58, Zach Brown wrote: > On some systems

Re: [RFC 1/2] mmc: sdhci: dt: Add device tree properties sdhci-caps and sdhci-caps-mask

On Tue, Nov 01, 2016 at 07:13:29AM +0900, Jaehoon Chung wrote: > On 10/31/2016 09:34 PM, Adrian Hunter wrote: > > On 31/10/16 13:59, Jaehoon Chung wrote: > >> On 10/28/2016 05:12 PM, Ulf Hansson wrote: > >>> On 25 October 2016 at 21:58, Zach Brown wrote: > On some systems the sdhci capabilty

Re: [PATCH 2/4] fs: remove the never implemented aio_fsync file operation

On Tue, Nov 1, 2016 at 7:30 AM, Christoph Hellwig wrote: > > sync_file_range is entirely different from fsync - Absolutely. And I think it's a shame. Particularly the fact that we don't have any way to actually tie into the filesystem, and we just work on the page cache level,

Re: [PATCH 2/4] fs: remove the never implemented aio_fsync file operation

On Tue, Nov 1, 2016 at 7:30 AM, Christoph Hellwig wrote: > > sync_file_range is entirely different from fsync - Absolutely. And I think it's a shame. Particularly the fact that we don't have any way to actually tie into the filesystem, and we just work on the page cache level, which "mostly

Re: [PATCH/RESEND V4 2/3] ARM64 LPC: Add missing range exception for special ISA

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/zhichang-yuan/ARM64-LPC-legacy-ISA-I-O-support/20161101-211425 base: https://git.kernel.org/

Re: [PATCH/RESEND V4 2/3] ARM64 LPC: Add missing range exception for special ISA

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/zhichang-yuan/ARM64-LPC-legacy-ISA-I-O-support/20161101-211425 base: https://git.kernel.org/

Re: [RFC PATCH 0/4] Clean up watchdog handlers

On 11/1/2016 8:20 AM, Don Zickus wrote: On Mon, Oct 31, 2016 at 04:30:59PM -0500, Babu Moger wrote: On 10/31/2016 4:00 PM, Don Zickus wrote: On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote: This is an attempt to cleanup watchdog handlers. Right now, kernel/watchdog.c implements

Re: [RFC PATCH 0/4] Clean up watchdog handlers

On 11/1/2016 8:20 AM, Don Zickus wrote: On Mon, Oct 31, 2016 at 04:30:59PM -0500, Babu Moger wrote: On 10/31/2016 4:00 PM, Don Zickus wrote: On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote: This is an attempt to cleanup watchdog handlers. Right now, kernel/watchdog.c implements

Re: [PATCH] kobject: set state_initialized to 0 in kobject_cleanup

On Tue, Nov 01, 2016 at 06:41:44PM +0800, Songjun Wu wrote: > If state_initialized is not set to 0 when a kobject is > released, a device is registered, unregistered, and > registered again, the error below will occur. > > kobject (dec04bb0): tried to init an initialized object, > something is

Re: [PATCH] kobject: set state_initialized to 0 in kobject_cleanup

On Tue, Nov 01, 2016 at 06:41:44PM +0800, Songjun Wu wrote: > If state_initialized is not set to 0 when a kobject is > released, a device is registered, unregistered, and > registered again, the error below will occur. > > kobject (dec04bb0): tried to init an initialized object, > something is

Re: [PATCH 01/14] dma: sun6i-dma: Add burst case of 4

On Tue, Nov 1, 2016 at 9:46 PM, Koul, Vinod wrote: > On Sun, 2016-10-30 at 10:06 +0800, Chen-Yu Tsai wrote: >> Looking at the dmaengine API, I believe we got it wrong. >> >> max_burst in dma_slave_config denotes the largest amount of data >> a single transfer should be, as

Re: [PATCH 01/14] dma: sun6i-dma: Add burst case of 4

On Tue, Nov 1, 2016 at 9:46 PM, Koul, Vinod wrote: > On Sun, 2016-10-30 at 10:06 +0800, Chen-Yu Tsai wrote: >> Looking at the dmaengine API, I believe we got it wrong. >> >> max_burst in dma_slave_config denotes the largest amount of data >> a single transfer should be, as described in

Re: [PATCH 1/1] xen-netfront: do not cast grant table reference to signed short

From: Dongli Zhang Date: Mon, 31 Oct 2016 21:46:09 -0700 (PDT) > David, I am very sorry for this error and I will be careful the next time. > Would you please let me know if I should resend a new patch or an incremental > based on previous one at >

Re: [PATCH 1/1] xen-netfront: do not cast grant table reference to signed short

From: Dongli Zhang Date: Mon, 31 Oct 2016 21:46:09 -0700 (PDT) > David, I am very sorry for this error and I will be careful the next time. > Would you please let me know if I should resend a new patch or an incremental > based on previous one at >

Re: BUG? genirq: irq 14 uses trigger mode 8; requested 0

On Tue, Nov 01, 2016 at 02:24:38PM +, Jon Hunter wrote: > Hi Mika, > > On 01/11/16 13:02, Mika Westerberg wrote: > > Hi, > > > > I started seeing following messages on Intel Broxton when the > > pinctrl/GPIO driver [1] loads: > > > > [0.645786] genirq: irq 14 uses trigger mode 8;

Re: BUG? genirq: irq 14 uses trigger mode 8; requested 0

On Tue, Nov 01, 2016 at 02:24:38PM +, Jon Hunter wrote: > Hi Mika, > > On 01/11/16 13:02, Mika Westerberg wrote: > > Hi, > > > > I started seeing following messages on Intel Broxton when the > > pinctrl/GPIO driver [1] loads: > > > > [0.645786] genirq: irq 14 uses trigger mode 8;

<    3   4   5   6   7   8   9   10   11   12   >