linux-next: manual merge of the kvm tree with Linus' tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/svm.c between commit: 15d45071523d ("KVM/x86: Add IBPB support") from Linus' tree and commit: 70cd94e60c73 ("KVM: SVM: VMRUN should use associated ASID when SEV is enabled") from the kvm tree. I fixed

linux-next: manual merge of the kvm tree with Linus' tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/svm.c between commit: 15d45071523d ("KVM/x86: Add IBPB support") from Linus' tree and commit: 70cd94e60c73 ("KVM: SVM: VMRUN should use associated ASID when SEV is enabled") from the kvm tree. I fixed

Re: [PATCH 2/6] genalloc: selftest

On 02/04/2018 03:03 PM, Matthew Wilcox wrote: > On Sun, Feb 04, 2018 at 02:19:22PM -0800, Randy Dunlap wrote: >>> +#ifndef __GENALLOC_SELFTEST_H__ >>> +#define __GENALLOC_SELFTEST_H__ >> >> Please use _LINUX_GENALLOC_SELFTEST_H_ > > willy@bobo:~/kernel/linux$ git grep define.*_H__$

Re: [PATCH 2/6] genalloc: selftest

On 02/04/2018 03:03 PM, Matthew Wilcox wrote: > On Sun, Feb 04, 2018 at 02:19:22PM -0800, Randy Dunlap wrote: >>> +#ifndef __GENALLOC_SELFTEST_H__ >>> +#define __GENALLOC_SELFTEST_H__ >> >> Please use _LINUX_GENALLOC_SELFTEST_H_ > > willy@bobo:~/kernel/linux$ git grep define.*_H__$

Re: [PATCH] drm/panel: lvds: tidyup header explanation

Hi Laurent > Hi Morimoto-san, > > Thank you for your patch. > > On Thursday, 1 February 2018 09:45:36 EET Kuninori Morimoto wrote: > > From: Kuninori Morimoto > > > > panel-lvds.c is for LVDS Panel Driver, > > not R-Car Display Unit CRTCs > > > >

Re: [PATCH] drm/panel: lvds: tidyup header explanation

Hi Laurent > Hi Morimoto-san, > > Thank you for your patch. > > On Thursday, 1 February 2018 09:45:36 EET Kuninori Morimoto wrote: > > From: Kuninori Morimoto > > > > panel-lvds.c is for LVDS Panel Driver, > > not R-Car Display Unit CRTCs > > > > Reported-by: Koji Matsuoka > >

Re: [PATCH] hwrng: Explicitly drop current_rng when unregistering rng device

Tom Lendacky writes: > A similar fix was already in the cryptodev tree and I thought was part of > a recent pull request. Yup, just saw it on master. I've checked and it will do pretty much the same thing as my patch, with the addition of clearing cur_rng_set_by_user,

Re: [PATCH] hwrng: Explicitly drop current_rng when unregistering rng device

Tom Lendacky writes: > A similar fix was already in the cryptodev tree and I thought was part of > a recent pull request. Yup, just saw it on master. I've checked and it will do pretty much the same thing as my patch, with the addition of clearing cur_rng_set_by_user, which is necessary. Thanks

Re: [PATCH] extcon: int3496: process id-pin first so that we start with the right status

On 2018년 02월 02일 17:10, Hans de Goede wrote: > Hi, > > On 02-02-18 01:32, Chanwoo Choi wrote: >> On 2018년 01월 26일 04:39, Hans de Goede wrote: >>> Some other drivers may be waiting for our extcon to show-up (exiting their >>> probe methods with -EPROBE_DEFER until we show up). >>> >>> These

Re: [PATCH] extcon: int3496: process id-pin first so that we start with the right status

On 2018년 02월 02일 17:10, Hans de Goede wrote: > Hi, > > On 02-02-18 01:32, Chanwoo Choi wrote: >> On 2018년 01월 26일 04:39, Hans de Goede wrote: >>> Some other drivers may be waiting for our extcon to show-up (exiting their >>> probe methods with -EPROBE_DEFER until we show up). >>> >>> These

[PATCH 3/3] vfio: disable filesystem-dax page pinning

Filesystem-DAX is incompatible with 'longterm' page pinning. Without page cache indirection a DAX mapping maps filesystem blocks directly. This means that the filesystem must not modify a file's block map while any page in a mapping is pinned. In order to prevent the situation of userspace holding

[PATCH 3/3] vfio: disable filesystem-dax page pinning

Filesystem-DAX is incompatible with 'longterm' page pinning. Without page cache indirection a DAX mapping maps filesystem blocks directly. This means that the filesystem must not modify a file's block map while any page in a mapping is pinned. In order to prevent the situation of userspace holding

[PATCH 0/3] vfio, dax: disable filesystem-dax and minor fixups

Alex, here is a change to vaddr_get_pfn() that we discussed in this thread: https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg07117.html Namely, drop support for passing Filesystem-DAX mappings through to guests. Perhaps in the future we can create some para-virtualized passthrough

[PATCH 2/3] dax: short circuit vma_is_fsdax() in the CONFIG_FS_DAX=n case

Do not bother looking up the file type in the case when Filesystem-DAX is disabled at build time. Cc: Alexander Viro Cc: linux-fsde...@vger.kernel.org Cc: Christoph Hellwig Cc: Jan Kara Signed-off-by: Dan Williams

[PATCH 1/3] dax: fix S_DAX definition

Make sure S_DAX is defined in the CONFIG_FS_DAX=n + CONFIG_DEV_DAX=y case. Otherwise vma_is_dax() may incorrectly return false in the Device-DAX case. Cc: Alexander Viro Cc: linux-fsde...@vger.kernel.org Cc: Christoph Hellwig Cc: Jan Kara Cc:

[PATCH 0/3] vfio, dax: disable filesystem-dax and minor fixups

Alex, here is a change to vaddr_get_pfn() that we discussed in this thread: https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg07117.html Namely, drop support for passing Filesystem-DAX mappings through to guests. Perhaps in the future we can create some para-virtualized passthrough

[PATCH 2/3] dax: short circuit vma_is_fsdax() in the CONFIG_FS_DAX=n case

Do not bother looking up the file type in the case when Filesystem-DAX is disabled at build time. Cc: Alexander Viro Cc: linux-fsde...@vger.kernel.org Cc: Christoph Hellwig Cc: Jan Kara Signed-off-by: Dan Williams --- include/linux/fs.h |2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 1/3] dax: fix S_DAX definition

Make sure S_DAX is defined in the CONFIG_FS_DAX=n + CONFIG_DEV_DAX=y case. Otherwise vma_is_dax() may incorrectly return false in the Device-DAX case. Cc: Alexander Viro Cc: linux-fsde...@vger.kernel.org Cc: Christoph Hellwig Cc: Jan Kara Cc: Fixes: dee410792419 ("/dev/dax, core: file

Re: [PATCH 2/6] genalloc: selftest

On Sun, Feb 04, 2018 at 02:19:22PM -0800, Randy Dunlap wrote: > > +#ifndef __GENALLOC_SELFTEST_H__ > > +#define __GENALLOC_SELFTEST_H__ > > Please use _LINUX_GENALLOC_SELFTEST_H_ willy@bobo:~/kernel/linux$ git grep define.*_H__$ include/linux/*.h |wc -l 98 willy@bobo:~/kernel/linux$ git grep

Re: [PATCH 2/6] genalloc: selftest

On Sun, Feb 04, 2018 at 02:19:22PM -0800, Randy Dunlap wrote: > > +#ifndef __GENALLOC_SELFTEST_H__ > > +#define __GENALLOC_SELFTEST_H__ > > Please use _LINUX_GENALLOC_SELFTEST_H_ willy@bobo:~/kernel/linux$ git grep define.*_H__$ include/linux/*.h |wc -l 98 willy@bobo:~/kernel/linux$ git grep

Re: [PATCH 1/6] genalloc: track beginning of allocations

On 02/04/2018 08:47 AM, Igor Stoppa wrote: > The genalloc library is only capable of tracking if a certain unit of > allocation is in use or not. > > It is not capable of discerning where the memory associated to an > allocation request begins and where it ends. > > The reason is that units of

Re: [PATCH 1/6] genalloc: track beginning of allocations

On 02/04/2018 08:47 AM, Igor Stoppa wrote: > The genalloc library is only capable of tracking if a certain unit of > allocation is in use or not. > > It is not capable of discerning where the memory associated to an > allocation request begins and where it ends. > > The reason is that units of

linux-next: build failure in Linus' tree

Hi Linus, Just building you tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/usb/host/ehci-st.c: In function 'st_ehci_suspend': drivers/usb/host/ehci-st.c:300:2: error: implicit declaration of function 'pinctrl_pm_select_sleep_state'

linux-next: build failure in Linus' tree

Hi Linus, Just building you tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/usb/host/ehci-st.c: In function 'st_ehci_suspend': drivers/usb/host/ehci-st.c:300:2: error: implicit declaration of function 'pinctrl_pm_select_sleep_state'

Re: [PATCH 2/6] genalloc: selftest

On 02/04/2018 08:47 AM, Igor Stoppa wrote: > Introduce a set of macros for writing concise test cases for genalloc. > > The test cases are meant to provide regression testing, when working on > new functionality for genalloc. > > Primarily they are meant to confirm that the various allocation

Re: [PATCH 2/6] genalloc: selftest

On 02/04/2018 08:47 AM, Igor Stoppa wrote: > Introduce a set of macros for writing concise test cases for genalloc. > > The test cases are meant to provide regression testing, when working on > new functionality for genalloc. > > Primarily they are meant to confirm that the various allocation

Re: [RFCv2 02/17] videodev2.h: Add request_fd field to v4l2_buffer

Hi Alexandre, On Wed, Jan 31, 2018 at 07:24:20PM +0900, Alexandre Courbot wrote: > From: Hans Verkuil > > When queuing buffers allow for passing the request that should > be associated with this buffer. > > Signed-off-by: Hans Verkuil >

Re: [RFCv2 02/17] videodev2.h: Add request_fd field to v4l2_buffer

Hi Alexandre, On Wed, Jan 31, 2018 at 07:24:20PM +0900, Alexandre Courbot wrote: > From: Hans Verkuil > > When queuing buffers allow for passing the request that should > be associated with this buffer. > > Signed-off-by: Hans Verkuil > [acour...@chromium.org: make request ID 32-bit] >

[PATCH] random: always fill buffer in get_random_bytes_wait

In the unfortunate event that a developer fails to check the return value of get_random_bytes_wait, or simply wants to make a "best effort" attempt, for whatever that's worth, it's much better to still fill the buffer with _something_ rather than catastrophically failing in the case of an

[PATCH] random: always fill buffer in get_random_bytes_wait

In the unfortunate event that a developer fails to check the return value of get_random_bytes_wait, or simply wants to make a "best effort" attempt, for whatever that's worth, it's much better to still fill the buffer with _something_ rather than catastrophically failing in the case of an

Re: [PATCH 4/6] Protectable Memory

On 02/04/2018 08:47 AM, Igor Stoppa wrote: > The MMU available in many systems running Linux can often provide R/O > protection to the memory pages it handles. > > However, the MMU-based protection works efficiently only when said pages > contain exclusively data that will not need further

Re: [PATCH 4/6] Protectable Memory

On 02/04/2018 08:47 AM, Igor Stoppa wrote: > The MMU available in many systems running Linux can often provide R/O > protection to the memory pages it handles. > > However, the MMU-based protection works efficiently only when said pages > contain exclusively data that will not need further

Re: [PATCH 6/6] Documentation for Pmalloc

Hi, On 02/04/2018 09:00 AM, Igor Stoppa wrote: > Detailed documentation about the protectable memory allocator. > > Signed-off-by: Igor Stoppa > --- > Documentation/core-api/index.rst | 1 + > Documentation/core-api/pmalloc.rst | 114 >

Re: [PATCH 6/6] Documentation for Pmalloc

Hi, On 02/04/2018 09:00 AM, Igor Stoppa wrote: > Detailed documentation about the protectable memory allocator. > > Signed-off-by: Igor Stoppa > --- > Documentation/core-api/index.rst | 1 + > Documentation/core-api/pmalloc.rst | 114 > + > 2 files

[PATCH] drm/bridge/synopsys: dsi: readl_poll_timeout return value clean up

The readl_poll_timeout() return value is 0 in case of success so it is better to detect errors without taking care of the return value sign. Signed-off-by: Philippe Cornu --- drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 10 +- 1 file changed, 5 insertions(+), 5

[PATCH] drm/bridge/synopsys: dsi: readl_poll_timeout return value clean up

The readl_poll_timeout() return value is 0 in case of success so it is better to detect errors without taking care of the return value sign. Signed-off-by: Philippe Cornu --- drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH] drm/bridge/synopsys: dsi: Add read feature

This patch adds the DCS/GENERIC DSI read feature. Signed-off-by: Philippe Cornu --- Extra notes: DSI read tests have been performed with DCS & GENERIC, short & long commands, on two different panels. The maximum fifo size (32*32-bit = 128 bytes on stm32) has been verified

[PATCH] drm/bridge/synopsys: dsi: Add read feature

This patch adds the DCS/GENERIC DSI read feature. Signed-off-by: Philippe Cornu --- Extra notes: DSI read tests have been performed with DCS & GENERIC, short & long commands, on two different panels. The maximum fifo size (32*32-bit = 128 bytes on stm32) has been verified too.

Re: [PATCH v4] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection

On 4 February 2018 21:03:05 GMT, Shreeya Patel wrote: >On Sun, 2018-02-04 at 11:10 +, Jonathan Cameron wrote: >> On Sat,  3 Feb 2018 21:01:32 +0530 >> Shreeya Patel wrote: >> >> > >> > iio_dev->mlock is to be used only by the

Re: [PATCH v4] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection

On 4 February 2018 21:03:05 GMT, Shreeya Patel wrote: >On Sun, 2018-02-04 at 11:10 +, Jonathan Cameron wrote: >> On Sat,  3 Feb 2018 21:01:32 +0530 >> Shreeya Patel wrote: >> >> > >> > iio_dev->mlock is to be used only by the IIO core for protecting >> > device mode changes between

[PATCH v2 4/5] drivers: bluetooth: ath3k: Fix warning: quoted string split across lines

This patch avoided the warning: WARNING: quoted string split across lines #355: FILE: drivers/bluetooth/ath3k.c:355: + BT_ERR("Error in firmware loading err = %d," + "len = %d, size = %d", err, len, size); This patch fix this issue.

[PATCH v2 4/5] drivers: bluetooth: ath3k: Fix warning: quoted string split across lines

This patch avoided the warning: WARNING: quoted string split across lines #355: FILE: drivers/bluetooth/ath3k.c:355: + BT_ERR("Error in firmware loading err = %d," + "len = %d, size = %d", err, len, size); This patch fix this issue.

[PATCH v2 3/5] drivers: bluetooth: ath3k: remove blank line after if

Removed blank line after if. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index b16c01a0b6d4..4df5b953a40d 100644 --- a/drivers/bluetooth/ath3k.c

[PATCH v2 1/5] drivers: bluetooth: ath3k: replace hardcode numbers with define

Replaced the numbers with a readable define. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index 204afe66de92..0a5cfea44529

[PATCH v2 3/5] drivers: bluetooth: ath3k: remove blank line after if

Removed blank line after if. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index b16c01a0b6d4..4df5b953a40d 100644 --- a/drivers/bluetooth/ath3k.c +++ b/drivers/bluetooth/ath3k.c

[PATCH v2 1/5] drivers: bluetooth: ath3k: replace hardcode numbers with define

Replaced the numbers with a readable define. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index 204afe66de92..0a5cfea44529 100644 ---

[PATCH v2 5/5] drivers: bluetooth: ath3k: fix checkpatch warning

This patch fixed warning: WARNING: Prefer using '"%s...", __func__' to using 'ath3k_disconnect', this function's name, in a string #568: FILE: drivers/bluetooth/ath3k.c:568: + BT_DBG("ath3k_disconnect intf %p", intf); Signed-off-by: Maxim Zhukov ---

[PATCH v2 2/5] drivers: bluetooth: ath3k: do not init variables

Do not need to initialize variables, because further on the code they fall into the snprintf. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/ath3k.c

[PATCH v2 5/5] drivers: bluetooth: ath3k: fix checkpatch warning

This patch fixed warning: WARNING: Prefer using '"%s...", __func__' to using 'ath3k_disconnect', this function's name, in a string #568: FILE: drivers/bluetooth/ath3k.c:568: + BT_DBG("ath3k_disconnect intf %p", intf); Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 2 +- 1

[PATCH v2 2/5] drivers: bluetooth: ath3k: do not init variables

Do not need to initialize variables, because further on the code they fall into the snprintf. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index

[PATCH v2 0/5] lite fixes for ath3k

Sorry for the last series of patches Maxim Zhukov (5): drivers: bluetooth: ath3k: replace hardcode numbers with define drivers: bluetooth: ath3k: do not init variables drivers: bluetooth: ath3k: remove blank line after if drivers: bluetooth: ath3k: Fix warning: quoted string split across

[PATCH v2 0/5] lite fixes for ath3k

Sorry for the last series of patches Maxim Zhukov (5): drivers: bluetooth: ath3k: replace hardcode numbers with define drivers: bluetooth: ath3k: do not init variables drivers: bluetooth: ath3k: remove blank line after if drivers: bluetooth: ath3k: Fix warning: quoted string split across

[PATCH 5/5] drivers: bluetooth: ath3k: fix checkpatch warning

This patch fixed warning: WARNING: Prefer using '"%s...", __func__' to using 'ath3k_disconnect', this function's name, in a string #568: FILE: drivers/bluetooth/ath3k.c:568: + BT_DBG("ath3k_disconnect intf %p", intf); Signed-off-by: Maxim Zhukov ---

[PATCH 5/5] drivers: bluetooth: ath3k: fix checkpatch warning

This patch fixed warning: WARNING: Prefer using '"%s...", __func__' to using 'ath3k_disconnect', this function's name, in a string #568: FILE: drivers/bluetooth/ath3k.c:568: + BT_DBG("ath3k_disconnect intf %p", intf); Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 2 +- 1

[PATCH 4/5] drivers: bluetooth: ath3k: Fix warning: quoted string split across lines

This patch avoided the warning: WARNING: quoted string split across lines #355: FILE: drivers/bluetooth/ath3k.c:355: + BT_ERR("Error in firmware loading err = %d," + "len = %d, size = %d", err, len, size); This patch fix this issue.

[PATCH 4/5] drivers: bluetooth: ath3k: Fix warning: quoted string split across lines

This patch avoided the warning: WARNING: quoted string split across lines #355: FILE: drivers/bluetooth/ath3k.c:355: + BT_ERR("Error in firmware loading err = %d," + "len = %d, size = %d", err, len, size); This patch fix this issue.

[PATCH 1/5] drivers: bluetooth: ath3k: replace hardcode numbers with define

Replaced the numbers with a readable define. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index 204afe66de92..0a5cfea44529

[PATCH 1/5] drivers: bluetooth: ath3k: replace hardcode numbers with define

Replaced the numbers with a readable define. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index 204afe66de92..0a5cfea44529 100644 ---

[PATCH 3/5] drivers: bluetooth: ath3k: remove blank line after if

Removed blank line after if. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index b16c01a0b6d4..4df5b953a40d 100644 --- a/drivers/bluetooth/ath3k.c

[PATCH 3/5] drivers: bluetooth: ath3k: remove blank line after if

Removed blank line after if. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index b16c01a0b6d4..4df5b953a40d 100644 --- a/drivers/bluetooth/ath3k.c +++ b/drivers/bluetooth/ath3k.c

[PATCH 2/5] drivers: bluetooth: ath3k: do not init variables

Do not need to initialize variables, because further on the code they fall into the snprintf. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/ath3k.c

[PATCH 2/5] drivers: bluetooth: ath3k: do not init variables

Do not need to initialize variables, because further on the code they fall into the snprintf. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index

Re: [PATCH v4] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection

On Sun, 2018-02-04 at 11:10 +, Jonathan Cameron wrote: > On Sat,  3 Feb 2018 21:01:32 +0530 > Shreeya Patel wrote: > > > > > iio_dev->mlock is to be used only by the IIO core for protecting > > device mode changes between INDIO_DIRECT and INDIO_BUFFER. > > > >

Re: [PATCH v4] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection

On Sun, 2018-02-04 at 11:10 +, Jonathan Cameron wrote: > On Sat,  3 Feb 2018 21:01:32 +0530 > Shreeya Patel wrote: > > > > > iio_dev->mlock is to be used only by the IIO core for protecting > > device mode changes between INDIO_DIRECT and INDIO_BUFFER. > > > > This patch replaces the use

[PATCH 5/5] drivers: bluetooth: ath3k: fix

This patch fixed warning: WARNING: Prefer using '"%s...", __func__' to using 'ath3k_disconnect', this function's name, in a string #568: FILE: drivers/bluetooth/ath3k.c:568: + BT_DBG("ath3k_disconnect intf %p", intf); Signed-off-by: Maxim Zhukov ---

[PATCH 5/5] drivers: bluetooth: ath3k: fix

This patch fixed warning: WARNING: Prefer using '"%s...", __func__' to using 'ath3k_disconnect', this function's name, in a string #568: FILE: drivers/bluetooth/ath3k.c:568: + BT_DBG("ath3k_disconnect intf %p", intf); Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 2 +- 1

[PATCH 4/5] drivers: bluetooth: ath3k: Fix warning: quoted string split across lines

This patch avoided the warning: WARNING: quoted string split across lines #355: FILE: drivers/bluetooth/ath3k.c:355: + BT_ERR("Error in firmware loading err = %d," + "len = %d, size = %d", err, len, size); This patch fix this issue.

[PATCH 4/5] drivers: bluetooth: ath3k: Fix warning: quoted string split across lines

This patch avoided the warning: WARNING: quoted string split across lines #355: FILE: drivers/bluetooth/ath3k.c:355: + BT_ERR("Error in firmware loading err = %d," + "len = %d, size = %d", err, len, size); This patch fix this issue.

[PATCH 2/5] drivers: bluetooth: ath3k: do not init variables

Do not need to initialize variables, because further on the code they fall into the snprintf. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/ath3k.c

[PATCH 3/5] drivers: bluetooth: ath3k: remove blank line after if

Removed blank line after if. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index b16c01a0b6d4..4df5b953a40d 100644 --- a/drivers/bluetooth/ath3k.c

[PATCH 2/5] drivers: bluetooth: ath3k: do not init variables

Do not need to initialize variables, because further on the code they fall into the snprintf. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index

[PATCH 3/5] drivers: bluetooth: ath3k: remove blank line after if

Removed blank line after if. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index b16c01a0b6d4..4df5b953a40d 100644 --- a/drivers/bluetooth/ath3k.c +++ b/drivers/bluetooth/ath3k.c

[PATCH 1/5] drivers: bluetooth: ath3k: replace hardcode numbers with define

Replaced the numbers with a readable define. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index 204afe66de92..0a5cfea44529

[PATCH 1/5] drivers: bluetooth: ath3k: replace hardcode numbers with define

Replaced the numbers with a readable define. Signed-off-by: Maxim Zhukov --- drivers/bluetooth/ath3k.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index 204afe66de92..0a5cfea44529 100644 ---

Re: [PATCH 1/2] ARM: kvm: fix building with gcc-8

On Sun, Feb 4, 2018 at 7:45 PM, Christoffer Dall wrote: > Hi Arnd, > > On Fri, Feb 02, 2018 at 04:07:34PM +0100, Arnd Bergmann wrote: >> In banked-sr.c, we use a top-level '__asm__(".arch_extension virt")' >> statement to allow compilation of a multi-CPU kernel for

Re: [PATCH 1/2] ARM: kvm: fix building with gcc-8

On Sun, Feb 4, 2018 at 7:45 PM, Christoffer Dall wrote: > Hi Arnd, > > On Fri, Feb 02, 2018 at 04:07:34PM +0100, Arnd Bergmann wrote: >> In banked-sr.c, we use a top-level '__asm__(".arch_extension virt")' >> statement to allow compilation of a multi-CPU kernel for ARMv6 >> and older ARMv7-A that

[RFC PATCH 2/3] pcmcia: use proper printk format for resource

Even though it is just in a dev_dbg statement, improve the printk format to use %pr instead of plain %p. Signed-off-by: Dominik Brodowski --- drivers/pcmcia/rsrc_nonstatic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[RFC PATCH 2/3] pcmcia: use proper printk format for resource

Even though it is just in a dev_dbg statement, improve the printk format to use %pr instead of plain %p. Signed-off-by: Dominik Brodowski --- drivers/pcmcia/rsrc_nonstatic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pcmcia/rsrc_nonstatic.c

[RFC PATCH 3/3] pcmcia: soc_common: Handle return value of clk_prepare_enable

From: Arvind Yadav clk_prepare_enable() can fail here and we must check its return value. Signed-off-by: Arvind Yadav CC: Russell King Signed-off-by: Dominik Brodowski ---

[RFC PATCH 1/3] pcmcia: remove mailing list, update MAINTAINERS

In recent years, the linux-pcmcia mailing list gained a pretty bad signal-to-noise ratio. It does not seem worth the hassle to keep it any longer. Thanks to David for hosting the list for the last couple of years! Acked-by: David Woodhouse CC: Russell King

[RFC PATCH 3/3] pcmcia: soc_common: Handle return value of clk_prepare_enable

From: Arvind Yadav clk_prepare_enable() can fail here and we must check its return value. Signed-off-by: Arvind Yadav CC: Russell King Signed-off-by: Dominik Brodowski --- drivers/pcmcia/soc_common.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

[RFC PATCH 1/3] pcmcia: remove mailing list, update MAINTAINERS

In recent years, the linux-pcmcia mailing list gained a pretty bad signal-to-noise ratio. It does not seem worth the hassle to keep it any longer. Thanks to David for hosting the list for the last couple of years! Acked-by: David Woodhouse CC: Russell King Signed-off-by: Dominik Brodowski ---

[RFC PATCH 0/3] pcmcia: odd fixes for v4.16-rc1

In the past couple of years, the linux-pcmcia mailing list had a pretty bad signal-to-noise ratio. Therefore, it was shut down for good. This means an update to MAINTAINERS is in order. If no-one else steps in, I will try to route the few odd fixes for pcmcia upstream. Also, throw in two odd fixes

[RFC PATCH 0/3] pcmcia: odd fixes for v4.16-rc1

In the past couple of years, the linux-pcmcia mailing list had a pretty bad signal-to-noise ratio. Therefore, it was shut down for good. This means an update to MAINTAINERS is in order. If no-one else steps in, I will try to route the few odd fixes for pcmcia upstream. Also, throw in two odd fixes

Re: [PATCH] drm/bridge/synopsys: dsi: Add 1.31 version support

Hi Archit, and many thanks for your comments On 02/04/2018 04:13 PM, Archit wrote: > Hi Phillipe, > > On Saturday 03 February 2018 03:49 AM, Philippe CORNU wrote: >> Hi Archit, Andrzej, Laurent & Brian, >> >> What is your opinion regarding this patch? Do you have any advice for >> handling hw

Re: [PATCH] drm/bridge/synopsys: dsi: Add 1.31 version support

Hi Archit, and many thanks for your comments On 02/04/2018 04:13 PM, Archit wrote: > Hi Phillipe, > > On Saturday 03 February 2018 03:49 AM, Philippe CORNU wrote: >> Hi Archit, Andrzej, Laurent & Brian, >> >> What is your opinion regarding this patch? Do you have any advice for >> handling hw

Re: [RFC 1/3] seccomp: add a return code to trap to userspace

On Sun, Feb 4, 2018 at 8:01 PM, Tycho Andersen wrote: > Hi Andy, > > On Sun, Feb 04, 2018 at 05:36:33PM +, Andy Lutomirski wrote: >> > The actual implementation of this is fairly small, although getting the >> > synchronization right was/is slightly complex. Also worth noting

Re: [RFC 1/3] seccomp: add a return code to trap to userspace

On Sun, Feb 4, 2018 at 8:01 PM, Tycho Andersen wrote: > Hi Andy, > > On Sun, Feb 04, 2018 at 05:36:33PM +, Andy Lutomirski wrote: >> > The actual implementation of this is fairly small, although getting the >> > synchronization right was/is slightly complex. Also worth noting that there >> >

Re: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

On Sun, 2018-02-04 at 19:43 +0100, Thomas Gleixner wrote: > > __x86_return_thunk would look like this: > > __x86_return_thunk: > testl   $0xf, PER_CPU_VAR(call_depth) > jnz 1f   > stuff_rsb >    1: > declPER_CPU_VAR(call_depth) > ret > > The

Re: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

On Sun, 2018-02-04 at 19:43 +0100, Thomas Gleixner wrote: > > __x86_return_thunk would look like this: > > __x86_return_thunk: > testl   $0xf, PER_CPU_VAR(call_depth) > jnz 1f   > stuff_rsb >    1: > declPER_CPU_VAR(call_depth) > ret > > The

Re: Dell docking station & Dell Embedded Controller & PS/2 devices

On Thursday 01 February 2018 21:23:40 mario.limoncie...@dell.com wrote: > > -Original Message- > > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] > > Sent: Thursday, February 1, 2018 3:14 PM > > To: Limonciello, Mario > > Cc: Pali Rohár

Re: Dell docking station & Dell Embedded Controller & PS/2 devices

On Thursday 01 February 2018 21:23:40 mario.limoncie...@dell.com wrote: > > -Original Message- > > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] > > Sent: Thursday, February 1, 2018 3:14 PM > > To: Limonciello, Mario > > Cc: Pali Rohár ; linux-in...@vger.kernel.org; lkml > >

Re: [RFC 1/3] seccomp: add a return code to trap to userspace

Hi Andy, On Sun, Feb 04, 2018 at 05:36:33PM +, Andy Lutomirski wrote: > > The actual implementation of this is fairly small, although getting the > > synchronization right was/is slightly complex. Also worth noting that there > > is one race still present: > > > > 1. a task does a

Re: [RFC 1/3] seccomp: add a return code to trap to userspace

Hi Andy, On Sun, Feb 04, 2018 at 05:36:33PM +, Andy Lutomirski wrote: > > The actual implementation of this is fairly small, although getting the > > synchronization right was/is slightly complex. Also worth noting that there > > is one race still present: > > > > 1. a task does a

Re: [GIT pull] More melted spectrum mitigations for 4.16

On Sun, Feb 4, 2018 at 7:31 AM, Thomas Gleixner wrote: > > That said, I'm taking a belated christmas vacation for a week and hope that > everything is magically solved when I'm back on Feb. 12th. Snort. Good luck with that. Linus

Re: [GIT pull] More melted spectrum mitigations for 4.16

On Sun, Feb 4, 2018 at 7:31 AM, Thomas Gleixner wrote: > > That said, I'm taking a belated christmas vacation for a week and hope that > everything is magically solved when I'm back on Feb. 12th. Snort. Good luck with that. Linus

Re: [tip:x86/pti] x86/speculation: Use Indirect Branch Prediction Barrier in context switch

On Thu, Feb 01, 2018 at 08:31:53AM +, David Woodhouse wrote: > On Wed, 2018-01-31 at 08:03 +0100, Dominik Brodowski wrote: > > Whether a process needs protection by IBPB on context switches is a > > different question to whether a process should be allowed to be dumped, > > though the former

Re: [tip:x86/pti] x86/speculation: Use Indirect Branch Prediction Barrier in context switch

On Thu, Feb 01, 2018 at 08:31:53AM +, David Woodhouse wrote: > On Wed, 2018-01-31 at 08:03 +0100, Dominik Brodowski wrote: > > Whether a process needs protection by IBPB on context switches is a > > different question to whether a process should be allowed to be dumped, > > though the former

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sun, Feb 4, 2018 at 7:30 AM, Mathieu Desnoyers wrote: > > I agree with your arguments. A consequence of those arguments is that > function-based tracing should be expected to be used by kernel engineers > and experts who can adapt their scripts to follow code

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sun, Feb 4, 2018 at 7:30 AM, Mathieu Desnoyers wrote: > > I agree with your arguments. A consequence of those arguments is that > function-based tracing should be expected to be used by kernel engineers > and experts who can adapt their scripts to follow code changes, and tune > the script

<    1   2   3   4   5   6   7   8   9   >