Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

On Thu, Feb 9, 2017 at 12:45 PM, KY Srinivasan wrote: > > >> -Original Message- >> From: Thomas Gleixner [mailto:t...@linutronix.de] >> Sent: Thursday, February 9, 2017 9:08 AM >> To: Vitaly Kuznetsov >> Cc: x...@kernel.org; Andy Lutomirski

Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

On Thu, Feb 9, 2017 at 12:45 PM, KY Srinivasan wrote: > > >> -Original Message- >> From: Thomas Gleixner [mailto:t...@linutronix.de] >> Sent: Thursday, February 9, 2017 9:08 AM >> To: Vitaly Kuznetsov >> Cc: x...@kernel.org; Andy Lutomirski ; Ingo Molnar >> ; H. Peter Anvin ; KY

[PATCH 1/1] net: ethernet: intel: e1000: add space after close brace

Fixes checkpatch.pl error: ERROR: space required after that close brace '}' Signed-off-by: Saber Rezvani --- drivers/net/ethernet/intel/e1000/e1000_param.c | 28 +- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git

[PATCH 1/1] net: ethernet: intel: e1000: add space after close brace

Fixes checkpatch.pl error: ERROR: space required after that close brace '}' Signed-off-by: Saber Rezvani --- drivers/net/ethernet/intel/e1000/e1000_param.c | 28 +- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git

Re: [PATCH v2] pci: drop link_reset

On Tue, Jan 24, 2017 at 07:35:56PM +0200, Michael S. Tsirkin wrote: > No hardware seems to actually call link_reset, and > no driver implements it as more than a nop stub. > > This drops the mentions of the callback from everywhere. > It's dropped from the documentation as well, but > the doc

Re: [PATCH v2] pci: drop link_reset

On Tue, Jan 24, 2017 at 07:35:56PM +0200, Michael S. Tsirkin wrote: > No hardware seems to actually call link_reset, and > no driver implements it as more than a nop stub. > > This drops the mentions of the callback from everywhere. > It's dropped from the documentation as well, but > the doc

Re: [PATCHv6 09/37] filemap: allocate huge page in pagecache_get_page(), if allowed

On Thu, Jan 26, 2017 at 02:57:51PM +0300, Kirill A. Shutemov wrote: > Write path allocate pages using pagecache_get_page(). We should be able > to allocate huge pages there, if it's allowed. As usually, fallback to > small pages, if failed. > > Signed-off-by: Kirill A. Shutemov

Re: [PATCHv6 09/37] filemap: allocate huge page in pagecache_get_page(), if allowed

On Thu, Jan 26, 2017 at 02:57:51PM +0300, Kirill A. Shutemov wrote: > Write path allocate pages using pagecache_get_page(). We should be able > to allocate huge pages there, if it's allowed. As usually, fallback to > small pages, if failed. > > Signed-off-by: Kirill A. Shutemov Reviewed-by:

[PATCH 3/4] [media] s5p-mfc: Set colorspace in VIDIO_{G,TRY}_FMT

The media documentation says that the V4L2_COLORSPACE_SMPTE170M colorspace should be used for SDTV and V4L2_COLORSPACE_REC709 for HDTV but the driver didn't set the colorimetry, also respect usespace setting. Use 576p display resolution as a threshold to set this. Signed-off-by: Thibault Saunier

[PATCH 1/4] [media] exynos-gsc: Use 576p instead 720p as a threshold for colorspaces

From: Javier Martinez Canillas The media documentation says that the V4L2_COLORSPACE_SMPTE170M colorspace should be used for SDTV and V4L2_COLORSPACE_REC709 for HDTV. But drivers don't agree on the display resolution that should be used as a threshold. Some drivers set

[PATCH 2/4] [media] exynos-gsc: Respect userspace colorspace setting

If the colorspace is specified by userspace we should respect it and not reset it ourself if we can support it. Signed-off-by: Thibault Saunier --- drivers/media/platform/exynos-gsc/gsc-core.c | 25 + 1 file changed, 17 insertions(+), 8

[PATCH 1/4] [media] exynos-gsc: Use 576p instead 720p as a threshold for colorspaces

From: Javier Martinez Canillas The media documentation says that the V4L2_COLORSPACE_SMPTE170M colorspace should be used for SDTV and V4L2_COLORSPACE_REC709 for HDTV. But drivers don't agree on the display resolution that should be used as a threshold. Some drivers set V4L2_COLORSPACE_REC709

[PATCH 2/4] [media] exynos-gsc: Respect userspace colorspace setting

If the colorspace is specified by userspace we should respect it and not reset it ourself if we can support it. Signed-off-by: Thibault Saunier --- drivers/media/platform/exynos-gsc/gsc-core.c | 25 + 1 file changed, 17 insertions(+), 8 deletions(-) diff --git

[PATCH 3/4] [media] s5p-mfc: Set colorspace in VIDIO_{G,TRY}_FMT

The media documentation says that the V4L2_COLORSPACE_SMPTE170M colorspace should be used for SDTV and V4L2_COLORSPACE_REC709 for HDTV but the driver didn't set the colorimetry, also respect usespace setting. Use 576p display resolution as a threshold to set this. Signed-off-by: Thibault Saunier

Re: [PATCH v2 2/2] drm/fb_helper: implement ioctl FBIO_WAITFORVSYNC

Hi, On 9 February 2017 at 17:01, Daniel Vetter wrote: > On Thu, Feb 02, 2017 at 11:31:57AM +0100, Maxime Ripard wrote: >> +int drm_fb_helper_ioctl(struct fb_info *info, unsigned int cmd, unsigned >> long arg) >> +{ >> + struct drm_fb_helper *fb_helper = info->par; >> +

Re: [PATCH v2 2/2] drm/fb_helper: implement ioctl FBIO_WAITFORVSYNC

Hi, On 9 February 2017 at 17:01, Daniel Vetter wrote: > On Thu, Feb 02, 2017 at 11:31:57AM +0100, Maxime Ripard wrote: >> +int drm_fb_helper_ioctl(struct fb_info *info, unsigned int cmd, unsigned >> long arg) >> +{ >> + struct drm_fb_helper *fb_helper = info->par; >> + struct drm_device

[PATCH 0/4] [media] Fixes for colorspace logic in exynos-gsc and s5p-mfc drivers

Hello, This patchset fixes a few issues on the colorspace logic for the exynos-gsc and s5p-mfc drivers. We now handle the colorspace in those drivers, and make sure to respect user setting if possible. We also now set the 'v4l2_pix_format:field' if userspace passed ANY, avoiding GStreamer

[PATCH 4/4] [media] s5p-mfc: Always check and set 'v4l2_pix_format:field' field

It is required by the standard that the field order is set by the driver. Signed-off-by: Thibault Saunier --- drivers/media/platform/s5p-mfc/s5p_mfc_dec.c | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git

[PATCH 0/4] [media] Fixes for colorspace logic in exynos-gsc and s5p-mfc drivers

Hello, This patchset fixes a few issues on the colorspace logic for the exynos-gsc and s5p-mfc drivers. We now handle the colorspace in those drivers, and make sure to respect user setting if possible. We also now set the 'v4l2_pix_format:field' if userspace passed ANY, avoiding GStreamer

[PATCH 4/4] [media] s5p-mfc: Always check and set 'v4l2_pix_format:field' field

It is required by the standard that the field order is set by the driver. Signed-off-by: Thibault Saunier --- drivers/media/platform/s5p-mfc/s5p_mfc_dec.c | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c

Re: [PATCH v3 2/3] ASoC: zx-i2s: introduce pclk for zx2967 family

On Thu, Feb 9, 2017 at 6:06 AM, Mark Brown wrote: > On Thu, Feb 09, 2017 at 09:48:09AM +0800, Shawn Guo wrote: >> On Wed, Feb 08, 2017 at 06:52:07PM -0600, Rob Herring wrote: > >> > Personally, I'd prefer "dt-bindings: sound: blah...", but not enough to >> > argue with Mark

Re: [PATCH v3 2/3] ASoC: zx-i2s: introduce pclk for zx2967 family

On Thu, Feb 9, 2017 at 6:06 AM, Mark Brown wrote: > On Thu, Feb 09, 2017 at 09:48:09AM +0800, Shawn Guo wrote: >> On Wed, Feb 08, 2017 at 06:52:07PM -0600, Rob Herring wrote: > >> > Personally, I'd prefer "dt-bindings: sound: blah...", but not enough to >> > argue with Mark about it. If that is

[PATCH resend] 9p: fix a potential acl leak

posix_acl_update_mode() could possibly clear 'acl', if so we leak the memory pointed by 'acl'. Save this pointer before calling posix_acl_update_mode() and release the memory if 'acl' really gets cleared. Reported-by: Mark Salyzyn Reviewed-by: Jan Kara

[PATCH resend] 9p: fix a potential acl leak

posix_acl_update_mode() could possibly clear 'acl', if so we leak the memory pointed by 'acl'. Save this pointer before calling posix_acl_update_mode() and release the memory if 'acl' really gets cleared. Reported-by: Mark Salyzyn Reviewed-by: Jan Kara Reviewed-by: Greg Kurz Cc: Eric Van

RE: [PATCH 3/4] cxgb4: Use more common logging style

> > Convert printks to pr_ > > Miscellanea: > > o Coalesce formats > o Realign arguments > > Signed-off-by: Joe Perches > --- > drivers/infiniband/hw/cxgb4/cm.c | 84 +++--- > drivers/infiniband/hw/cxgb4/cq.c | 8 ++-- >

RE: [PATCH 3/4] cxgb4: Use more common logging style

> > Convert printks to pr_ > > Miscellanea: > > o Coalesce formats > o Realign arguments > > Signed-off-by: Joe Perches > --- > drivers/infiniband/hw/cxgb4/cm.c | 84 +++--- > drivers/infiniband/hw/cxgb4/cq.c | 8 ++-- >

[PATCH 1/1] net: ethernet: intel: e1000: msleep() is unreliable for anything <20ms

Fix the checkpatch.pl issue: WARNING: msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt Signed-off-by: Saber Rezvani --- drivers/net/ethernet/intel/e1000/e1000_main.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 1/1] net: ethernet: intel: e1000: msleep() is unreliable for anything <20ms

Fix the checkpatch.pl issue: WARNING: msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt Signed-off-by: Saber Rezvani --- drivers/net/ethernet/intel/e1000/e1000_main.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

RE: [PATCH 1/4] cxgb3: Use more common logging style

> Subject: [PATCH 1/4] cxgb3: Use more common logging style > > Convert printks to pr_ > > Miscellanea: > > o Coalesce formats > o Realign arguments > > Signed-off-by: Joe Perches > --- > drivers/infiniband/hw/cxgb3/cxio_hal.c | 27 ++-- >

RE: [PATCH 1/4] cxgb3: Use more common logging style

> Subject: [PATCH 1/4] cxgb3: Use more common logging style > > Convert printks to pr_ > > Miscellanea: > > o Coalesce formats > o Realign arguments > > Signed-off-by: Joe Perches > --- > drivers/infiniband/hw/cxgb3/cxio_hal.c | 27 ++-- > drivers/infiniband/hw/cxgb3/cxio_hal.h

RE: [PATCH 2/4] cxgb3: Convert PDBG to pr_debug

> Subject: [PATCH 2/4] cxgb3: Convert PDBG to pr_debug > > Using the normal mechanism, not an indirected one, is clearer. > > Miscellanea: > > o Coalesce formats > o Realign arguments > > Signed-off-by: Joe Perches > --- > drivers/infiniband/hw/cxgb3/cxio_dbg.c | 35

RE: [PATCH 2/4] cxgb3: Convert PDBG to pr_debug

> Subject: [PATCH 2/4] cxgb3: Convert PDBG to pr_debug > > Using the normal mechanism, not an indirected one, is clearer. > > Miscellanea: > > o Coalesce formats > o Realign arguments > > Signed-off-by: Joe Perches > --- > drivers/infiniband/hw/cxgb3/cxio_dbg.c | 35 ++--- >

Re: [PATCH 1/4] cxgb3: Use more common logging style

On Thu, 2017-02-09 at 16:34 -0600, Steve Wise wrote: > > Subject: [PATCH 1/4] cxgb3: Use more common logging style [] > > -#define MOD "iw_cxgb3: " > > -#define PDBG(fmt, args...) pr_debug(MOD fmt, ## args) > > +#ifdef pr_fmt > > +#undef pr_fmt > > +#endif > > Is the ifdef/undef needed? I see

Re: [PATCH 1/4] cxgb3: Use more common logging style

On Thu, 2017-02-09 at 16:34 -0600, Steve Wise wrote: > > Subject: [PATCH 1/4] cxgb3: Use more common logging style [] > > -#define MOD "iw_cxgb3: " > > -#define PDBG(fmt, args...) pr_debug(MOD fmt, ## args) > > +#ifdef pr_fmt > > +#undef pr_fmt > > +#endif > > Is the ifdef/undef needed? I see

Re: [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume

From: Ivan Khoronzhuk Date: Thu, 9 Feb 2017 02:07:34 +0200 > These two patches fix suspend/resume chain. Patch 2 doesn't apply cleanly to the 'net' tree, please respin this series.

Re: [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume

From: Ivan Khoronzhuk Date: Thu, 9 Feb 2017 02:07:34 +0200 > These two patches fix suspend/resume chain. Patch 2 doesn't apply cleanly to the 'net' tree, please respin this series.

Re: [PATCH] [net-next] ARM: orion: remove unused wnr854t_switch_plat_data

From: Arnd Bergmann Date: Wed, 8 Feb 2017 22:24:19 +0100 > The other instances of this structure got removed along with the MDIO > device change, but this one was left behind and needs to be removed > as well: > > arch/arm/mach-orion5x/wnr854t-setup.c:109:44: error: >

Re: [PATCH] [net-next] ARM: orion: remove unused wnr854t_switch_plat_data

From: Arnd Bergmann Date: Wed, 8 Feb 2017 22:24:19 +0100 > The other instances of this structure got removed along with the MDIO > device change, but this one was left behind and needs to be removed > as well: > > arch/arm/mach-orion5x/wnr854t-setup.c:109:44: error: >

[PATCH] security/keys: add CONFIG_KEYS_COMPAT to Kconfig

CONFIG_KEYS_COMPAT is defined in arch-specific Kconfigs and is missing for several 64-bit architectures : arm64, mips, parisc, tile. At the moment and for those architectures, calling in 32-bit userspace the keyctl syscall would return an ENOSYS error. This patch moves the CONFIG_KEYS_COMPAT

[PATCH] security/keys: add CONFIG_KEYS_COMPAT to Kconfig

CONFIG_KEYS_COMPAT is defined in arch-specific Kconfigs and is missing for several 64-bit architectures : arm64, mips, parisc, tile. At the moment and for those architectures, calling in 32-bit userspace the keyctl syscall would return an ENOSYS error. This patch moves the CONFIG_KEYS_COMPAT

[PATCH 0/4] infiniband: chelsio

Neaten logging Joe Perches (4): cxgb3: Use more common logging style cxgb3: Convert PDBG to pr_debug cxgb4: Use more common logging style cxgb4: Convert PDBG to pr_debug drivers/infiniband/hw/cxgb3/cxio_dbg.c | 35 +-- drivers/infiniband/hw/cxgb3/cxio_hal.c | 201

[PATCH 0/4] infiniband: chelsio

Neaten logging Joe Perches (4): cxgb3: Use more common logging style cxgb3: Convert PDBG to pr_debug cxgb4: Use more common logging style cxgb4: Convert PDBG to pr_debug drivers/infiniband/hw/cxgb3/cxio_dbg.c | 35 +-- drivers/infiniband/hw/cxgb3/cxio_hal.c | 201

[PATCH 2/4] cxgb3: Convert PDBG to pr_debug

Using the normal mechanism, not an indirected one, is clearer. Miscellanea: o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb3/cxio_dbg.c | 35 ++--- drivers/infiniband/hw/cxgb3/cxio_hal.c | 174

[PATCH 2/4] cxgb3: Convert PDBG to pr_debug

Using the normal mechanism, not an indirected one, is clearer. Miscellanea: o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb3/cxio_dbg.c | 35 ++--- drivers/infiniband/hw/cxgb3/cxio_hal.c | 174

[PATCH 3/4] cxgb4: Use more common logging style

Convert printks to pr_ Miscellanea: o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb4/cm.c | 84 +++--- drivers/infiniband/hw/cxgb4/cq.c | 8 ++-- drivers/infiniband/hw/cxgb4/device.c

[PATCH 3/4] cxgb4: Use more common logging style

Convert printks to pr_ Miscellanea: o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb4/cm.c | 84 +++--- drivers/infiniband/hw/cxgb4/cq.c | 8 ++-- drivers/infiniband/hw/cxgb4/device.c | 83

[PATCH 1/4] cxgb3: Use more common logging style

Convert printks to pr_ Miscellanea: o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb3/cxio_hal.c | 27 ++-- drivers/infiniband/hw/cxgb3/cxio_hal.h | 9 +++- drivers/infiniband/hw/cxgb3/cxio_resource.c | 5

[PATCH 1/4] cxgb3: Use more common logging style

Convert printks to pr_ Miscellanea: o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb3/cxio_hal.c | 27 ++-- drivers/infiniband/hw/cxgb3/cxio_hal.h | 9 +++- drivers/infiniband/hw/cxgb3/cxio_resource.c | 5 ++-

[PATCH 4/4] cxgb4: Convert PDBG to pr_debug

Use a more typical logging style. Miscellanea: o Obsolete the c4iw_debug module parameter o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb4/cm.c | 303 + drivers/infiniband/hw/cxgb4/cq.c

[PATCH 4/4] cxgb4: Convert PDBG to pr_debug

Use a more typical logging style. Miscellanea: o Obsolete the c4iw_debug module parameter o Coalesce formats o Realign arguments Signed-off-by: Joe Perches --- drivers/infiniband/hw/cxgb4/cm.c | 303 + drivers/infiniband/hw/cxgb4/cq.c | 71

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Thu, Feb 09, 2017 at 11:29:51AM -0800, James Bottomley wrote: > On Thu, 2017-02-09 at 12:04 -0700, Jason Gunthorpe wrote: > > On Thu, Feb 09, 2017 at 05:19:22PM +0200, Jarkko Sakkinen wrote: > > > The current patch set does not define policy. The simple policy > > > addition that could be added

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Thu, Feb 09, 2017 at 11:29:51AM -0800, James Bottomley wrote: > On Thu, 2017-02-09 at 12:04 -0700, Jason Gunthorpe wrote: > > On Thu, Feb 09, 2017 at 05:19:22PM +0200, Jarkko Sakkinen wrote: > > > The current patch set does not define policy. The simple policy > > > addition that could be added

[PATCH] net: myricom: myri10ge: 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. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/myricom/myri10ge/myri10ge.c |

[PATCH] net: myricom: myri10ge: 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. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/myricom/myri10ge/myri10ge.c | 23

[PATCH] media: s5p_mfc - remove unneeded io_modes initialzation in s5p_mfc_open()

Remove unneeded io_modes initialzation in s5p_mfc_open(). It gets done right below in vdev == dev->vfd_dec conditional. Signed-off-by: Shuah Khan --- drivers/media/platform/s5p-mfc/s5p_mfc.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH] media: s5p_mfc - remove unneeded io_modes initialzation in s5p_mfc_open()

Remove unneeded io_modes initialzation in s5p_mfc_open(). It gets done right below in vdev == dev->vfd_dec conditional. Signed-off-by: Shuah Khan --- drivers/media/platform/s5p-mfc/s5p_mfc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc.c

[PATCH] media: fix s5p_mfc_set_dec_frame_buffer_v6() to print buf size in hex

Fix s5p_mfc_set_dec_frame_buffer_v6() to print buffer size in hex to be consistent with the rest of the messages in the routine. Signed-off-by: Shuah Khan --- drivers/media/platform/s5p-mfc/s5p_mfc_opr_v6.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] media: fix s5p_mfc_set_dec_frame_buffer_v6() to print buf size in hex

Fix s5p_mfc_set_dec_frame_buffer_v6() to print buffer size in hex to be consistent with the rest of the messages in the routine. Signed-off-by: Shuah Khan --- drivers/media/platform/s5p-mfc/s5p_mfc_opr_v6.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH net v3 1/2] net: ethernet: bgmac: init sequence bug

From: Jon Mason Date: Wed, 8 Feb 2017 16:12:56 -0500 > The code now checks to see if the adapter needs to be brought out of > reset (where as before it was doing an IDM write to bring it out of > reset regardless of whether it was in reset or not). Also, removed >

Re: [PATCH net v3 1/2] net: ethernet: bgmac: init sequence bug

From: Jon Mason Date: Wed, 8 Feb 2017 16:12:56 -0500 > The code now checks to see if the adapter needs to be brought out of > reset (where as before it was doing an IDM write to bring it out of > reset regardless of whether it was in reset or not). Also, removed > unnecessary usleeps (as there

Re: [PATCH net] net: phy: Initialize mdio clock at probe function

From: Jon Mason Date: Wed, 8 Feb 2017 17:14:26 -0500 > From: Yendapally Reddy Dhananjaya Reddy > > USB PHYs need the MDIO clock divisor enabled earlier to work. > Initialize mdio clock divisor in probe function. The ext bus > bit

Re: [PATCH net] net: phy: Initialize mdio clock at probe function

From: Jon Mason Date: Wed, 8 Feb 2017 17:14:26 -0500 > From: Yendapally Reddy Dhananjaya Reddy > > USB PHYs need the MDIO clock divisor enabled earlier to work. > Initialize mdio clock divisor in probe function. The ext bus > bit available in the same register will be used by mdio mux > to

Re: [PATCHv5 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces

From: Sainath Grandhi Date: Wed, 8 Feb 2017 13:37:09 -0800 > Tap character devices can be implemented on other virtual interfaces like > ipvlan, similar to macvtap. Source code for tap functionality in macvtap > can be re-used for this purpose. > > This patch series

Re: [PATCHv5 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces

From: Sainath Grandhi Date: Wed, 8 Feb 2017 13:37:09 -0800 > Tap character devices can be implemented on other virtual interfaces like > ipvlan, similar to macvtap. Source code for tap functionality in macvtap > can be re-used for this purpose. > > This patch series splits macvtap source into

Re: [PATCH] cpufreq: ti: move to new dev_pm_opp_set_supported_hw() API

On Thu, Feb 9, 2017 at 4:02 PM, Arnd Bergmann wrote: > We have a conflict between the interface change in one patch, and the > newly added driver using the old interface: > > drivers/cpufreq/ti-cpufreq.c: In function 'ti_cpufreq_init': > drivers/cpufreq/ti-cpufreq.c:250:6: error:

Re: [PATCH] cpufreq: ti: move to new dev_pm_opp_set_supported_hw() API

On Thu, Feb 9, 2017 at 4:02 PM, Arnd Bergmann wrote: > We have a conflict between the interface change in one patch, and the > newly added driver using the old interface: > > drivers/cpufreq/ti-cpufreq.c: In function 'ti_cpufreq_init': > drivers/cpufreq/ti-cpufreq.c:250:6: error: assignment makes

[PATCH] Do not initialise statics to NULL

This patch fixes a checkpatch.pl error in bcm2835.c ERROR: do not initialise statics to NULL Signed-off-by: William Stevenson --- drivers/staging/bcm2835-audio/bcm2835.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] Do not initialise statics to NULL

This patch fixes a checkpatch.pl error in bcm2835.c ERROR: do not initialise statics to NULL Signed-off-by: William Stevenson --- drivers/staging/bcm2835-audio/bcm2835.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/bcm2835-audio/bcm2835.c

Re: [PATCH v2 3/4] seccomp: Create an action to log before allowing

On Tue, Feb 7, 2017 at 4:33 PM, Kees Cook wrote: > On Thu, Feb 2, 2017 at 9:37 PM, Tyler Hicks wrote: >> Add a new action, SECCOMP_RET_LOG, that logs a syscall before allowing >> the syscall. At the implementation level, this action is identical to

Re: [PATCH v2 3/4] seccomp: Create an action to log before allowing

On Tue, Feb 7, 2017 at 4:33 PM, Kees Cook wrote: > On Thu, Feb 2, 2017 at 9:37 PM, Tyler Hicks wrote: >> Add a new action, SECCOMP_RET_LOG, that logs a syscall before allowing >> the syscall. At the implementation level, this action is identical to >> the existing SECCOMP_RET_ALLOW action.

Re: [PATCHv6 08/37] filemap: handle huge pages in do_generic_file_read()

On Thu, Jan 26, 2017 at 02:57:50PM +0300, Kirill A. Shutemov wrote: > +++ b/mm/filemap.c > @@ -1886,6 +1886,7 @@ static ssize_t do_generic_file_read(struct file *filp, > loff_t *ppos, > if (unlikely(page == NULL)) > goto no_cached_page; >

Re: [PATCHv6 08/37] filemap: handle huge pages in do_generic_file_read()

On Thu, Jan 26, 2017 at 02:57:50PM +0300, Kirill A. Shutemov wrote: > +++ b/mm/filemap.c > @@ -1886,6 +1886,7 @@ static ssize_t do_generic_file_read(struct file *filp, > loff_t *ppos, > if (unlikely(page == NULL)) > goto no_cached_page; >

Re: [PATCH v3] xen-netfront: Improve error handling during initialization

From: Ross Lagerwall Date: Wed, 8 Feb 2017 10:57:37 + > This fixes a crash when running out of grant refs when creating many > queues across many netdevs. > > * If creating queues fails (i.e. there are no grant refs available), > call xenbus_dev_fatal() to ensure

Re: [PATCH v3] xen-netfront: Improve error handling during initialization

From: Ross Lagerwall Date: Wed, 8 Feb 2017 10:57:37 + > This fixes a crash when running out of grant refs when creating many > queues across many netdevs. > > * If creating queues fails (i.e. there are no grant refs available), > call xenbus_dev_fatal() to ensure that the xenbus device is

[PATCH] staging: wlan_ng: fix logical continuation alignment

It appears that our coding style prefers that logical continuations have the operator at the end of the line. Fix that. While at it, stick the 'if' after 'else' where it belongs. Signed-off-by: Frans Klaver --- drivers/staging/wlan-ng/prism2mgmt.c | 11 +-- 1

[PATCH] staging: wlan_ng: fix logical continuation alignment

It appears that our coding style prefers that logical continuations have the operator at the end of the line. Fix that. While at it, stick the 'if' after 'else' where it belongs. Signed-off-by: Frans Klaver --- drivers/staging/wlan-ng/prism2mgmt.c | 11 +-- 1 file changed, 5

Re: [PATCH] jump_label: mark __start/stop___jump_table const

On Thu, Feb 09, 2017 at 11:11:32PM +0200, Michael S. Tsirkin wrote: > Attempts to assign values through these pointers would fail. > Mark them const to make sure the failure is compile time. > > Cc: Jason Baron > Cc: Peter Zijlstra > Cc: Steven Rostedt

Re: [PATCH] jump_label: mark __start/stop___jump_table const

On Thu, Feb 09, 2017 at 11:11:32PM +0200, Michael S. Tsirkin wrote: > Attempts to assign values through these pointers would fail. > Mark them const to make sure the failure is compile time. > > Cc: Jason Baron > Cc: Peter Zijlstra > Cc: Steven Rostedt > Cc: Borislav Petkov > Cc: Andrew

Re: [PATCH v3 0/2] Fixes for sierra_net driver

From: Stefan Brüns Date: Wed, 8 Feb 2017 02:46:31 +0100 > When trying to initiate a dual-stack (ipv4v6) connection, a MC7710, FW > version SWI9200X_03.05.24.00ap answers with an unsupported LSI. Add support > for this LSI. > Also the link_type should be ignored when

Re: [PATCH v3 0/2] Fixes for sierra_net driver

From: Stefan Brüns Date: Wed, 8 Feb 2017 02:46:31 +0100 > When trying to initiate a dual-stack (ipv4v6) connection, a MC7710, FW > version SWI9200X_03.05.24.00ap answers with an unsupported LSI. Add support > for this LSI. > Also the link_type should be ignored when going idle, otherwise the

Re: [PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()

> Note: Matching the driver to the I2C device requires another patch. > http://www.spinics.net/lists/linux-acpi/msg71914.html Do I get it right? With the patch applied we won't have a regression but the new feature will only be available when the above series is upstream? So, it is a "weak"

Re: [PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()

> Note: Matching the driver to the I2C device requires another patch. > http://www.spinics.net/lists/linux-acpi/msg71914.html Do I get it right? With the patch applied we won't have a regression but the new feature will only be available when the above series is upstream? So, it is a "weak"

[PATCH] net: microchip: encx24j600: 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. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/microchip/encx24j600.c | 32

[PATCH] net: microchip: encx24j600: 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. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/microchip/encx24j600.c | 32

RE: [PATCH v3 4/4] remoteproc: core: don't allocate carveout if pa or da are defined

> -Original Message- > From: Bjorn Andersson [mailto:bjorn.anders...@linaro.org] > Sent: Thursday, February 09, 2017 2:55 AM > To: Loic PALLARDY > Cc: o...@wizery.com; lee.jo...@linaro.org; linux- > remotep...@vger.kernel.org; linux-kernel@vger.kernel.org; >

Re: [PATCH] i2c: designware: Fix regression when dynamic TAR update is disabled

On Thu, 2017-02-09 at 22:07 +0200, Andy Shevchenko wrote: > On Fri, 2017-02-10 at 01:20 +0530, Shah Nehal-Bakulchandra wrote: > > The following commit causes a regression when dynamic TAR update is > > disabled: > > > >  commit 63d0f0a6952a1a02bc4f116b7da7c7887e46efa3 ("i2c: > > designware: >

RE: [PATCH v3 4/4] remoteproc: core: don't allocate carveout if pa or da are defined

> -Original Message- > From: Bjorn Andersson [mailto:bjorn.anders...@linaro.org] > Sent: Thursday, February 09, 2017 2:55 AM > To: Loic PALLARDY > Cc: o...@wizery.com; lee.jo...@linaro.org; linux- > remotep...@vger.kernel.org; linux-kernel@vger.kernel.org; > ker...@stlinux.com; Patrice

Re: [PATCH] i2c: designware: Fix regression when dynamic TAR update is disabled

On Thu, 2017-02-09 at 22:07 +0200, Andy Shevchenko wrote: > On Fri, 2017-02-10 at 01:20 +0530, Shah Nehal-Bakulchandra wrote: > > The following commit causes a regression when dynamic TAR update is > > disabled: > > > >  commit 63d0f0a6952a1a02bc4f116b7da7c7887e46efa3 ("i2c: > > designware: >

Re: [PATCH] xen-netfront: Rework the fix for Rx stall during OOM and network stress

From: Vineeth Remanan Pillai Date: Tue, 7 Feb 2017 18:59:01 + > The commit 90c311b0eeea ("xen-netfront: Fix Rx stall during network > stress and OOM") caused the refill timer to be triggerred almost on > all invocations of xennet_alloc_rx_buffers for certain workloads. >

Re: [PATCH] xen-netfront: Rework the fix for Rx stall during OOM and network stress

From: Vineeth Remanan Pillai Date: Tue, 7 Feb 2017 18:59:01 + > The commit 90c311b0eeea ("xen-netfront: Fix Rx stall during network > stress and OOM") caused the refill timer to be triggerred almost on > all invocations of xennet_alloc_rx_buffers for certain workloads. > This reworks the fix

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Wed, Feb 08, 2017 at 11:34:07AM -0500, Mike Snitzer wrote: > On Tue, Feb 07 2017 at 11:58pm -0500, > Kent Overstreet wrote: > > > On Tue, Feb 07, 2017 at 09:39:11PM +0100, Pavel Machek wrote: > > > On Mon 2017-02-06 17:49:06, Kent Overstreet wrote: > > > > On Mon,

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Wed, Feb 08, 2017 at 11:34:07AM -0500, Mike Snitzer wrote: > On Tue, Feb 07 2017 at 11:58pm -0500, > Kent Overstreet wrote: > > > On Tue, Feb 07, 2017 at 09:39:11PM +0100, Pavel Machek wrote: > > > On Mon 2017-02-06 17:49:06, Kent Overstreet wrote: > > > > On Mon, Feb 06, 2017 at 04:47:24PM

[PATCH] x86, perf: Add Top Down events to Intel Goldmont

From: Kan Liang Goldmont supports full Top Down level 1 metrics (FrontendBound, Retiring, Backend Bound and Bad Speculation). It has 3 wide pipeline. Signed-off-by: Kan Liang --- arch/x86/events/intel/core.c | 26 ++ 1 file

[PATCH] x86, perf: Add Top Down events to Intel Goldmont

From: Kan Liang Goldmont supports full Top Down level 1 metrics (FrontendBound, Retiring, Backend Bound and Bad Speculation). It has 3 wide pipeline. Signed-off-by: Kan Liang --- arch/x86/events/intel/core.c | 26 ++ 1 file changed, 26 insertions(+) diff --git

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

From: Arnd Bergmann Date: Wed, 8 Feb 2017 22:18:26 +0100 > When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large > stack frames in some functions. This goes unnoticed normally because > CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

From: Arnd Bergmann Date: Wed, 8 Feb 2017 22:18:26 +0100 > When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large > stack frames in some functions. This goes unnoticed normally because > CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit > 3f181b4d8652

Re: [PATCH] arm64: dts: mediatek: add mt8176 device tree

On 02/07/2017 06:35 AM, Yidi Lin wrote: The core configuration is the only difference between mt8173 and mt8176. Like what arm/juno and marvell/armada-ap806 did, this change splits mt8173.dtsi into mt817x.dtsi and mt8173.dtsi. mt817x.dtsi defines the common blocks for mt8173 and mt8176.

Re: [PATCH] arm64: dts: mediatek: add mt8176 device tree

On 02/07/2017 06:35 AM, Yidi Lin wrote: The core configuration is the only difference between mt8173 and mt8176. Like what arm/juno and marvell/armada-ap806 did, this change splits mt8173.dtsi into mt817x.dtsi and mt8173.dtsi. mt817x.dtsi defines the common blocks for mt8173 and mt8176.

Re: [PATCH v2] eeprom/at24: use device_property_*() functions instead of of_get_property()

On Thu, Feb 9, 2017 at 10:35 PM, kbuild test robot <l...@intel.com> wrote: > Hi Ben, > > [auto build test ERROR on char-misc/char-misc-testing] > [also build test ERROR on v4.10-rc7 next-20170209] > [if your patch is applied to the wrong git tree, please drop us a no

Re: [PATCH v2] eeprom/at24: use device_property_*() functions instead of of_get_property()

On Thu, Feb 9, 2017 at 10:35 PM, kbuild test robot wrote: > Hi Ben, > > [auto build test ERROR on char-misc/char-misc-testing] > [also build test ERROR on v4.10-rc7 next-20170209] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the s

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