I need your assistance to invest!!!

Dear Sir, I need your support to relocate and invest in your country. I ask your assistance because I don’t have knowledge about business and the rules that guide your country for safe investment. Will you promise to be sincere with me? Please contact me for more information details! With

I need your assistance to invest!!!

Dear Sir, I need your support to relocate and invest in your country. I ask your assistance because I don’t have knowledge about business and the rules that guide your country for safe investment. Will you promise to be sincere with me? Please contact me for more information details! With

Re: [PATCH] orinoco: Use shash instead of ahash for MIC calculations

On Mon, Dec 12, 2016 at 12:55:55PM -0800, Andy Lutomirski wrote: > +int orinoco_mic(struct crypto_shash *tfm_michael, u8 *key, > u8 *da, u8 *sa, u8 priority, > u8 *data, size_t data_len, u8 *mic) > { > - AHASH_REQUEST_ON_STACK(req, tfm_michael); > - struct

Re: [PATCH] orinoco: Use shash instead of ahash for MIC calculations

On Mon, Dec 12, 2016 at 12:55:55PM -0800, Andy Lutomirski wrote: > +int orinoco_mic(struct crypto_shash *tfm_michael, u8 *key, > u8 *da, u8 *sa, u8 priority, > u8 *data, size_t data_len, u8 *mic) > { > - AHASH_REQUEST_ON_STACK(req, tfm_michael); > - struct

Re: [PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

[...] >>> + >>> +Optional properties: >>> +For eMMC configuration, supported speed modes are not indicated by the >>> SDHCI >>> +Capabilities Register. Instead, the following properties should be >>> specified >>> +if supported. See mmc.txt for details. >>> +- mmc-ddr-1_8v >>> +- mmc-ddr-1_2v

Re: [PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

[...] >>> + >>> +Optional properties: >>> +For eMMC configuration, supported speed modes are not indicated by the >>> SDHCI >>> +Capabilities Register. Instead, the following properties should be >>> specified >>> +if supported. See mmc.txt for details. >>> +- mmc-ddr-1_8v >>> +- mmc-ddr-1_2v

Re: [PATCH] clk: imx: pllv3: support fractional multiplier on vf610 PLL1/PLL2

>> diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c >> index 19f9b622981a..24a9e914e0d5 100644 >> --- a/drivers/clk/imx/clk-pllv3.c >> +++ b/drivers/clk/imx/clk-pllv3.c >> @@ -288,6 +291,87 @@ static const struct clk_ops clk_pllv3_av_ops = { >> .set_rate =

Re: [PATCH] clk: imx: pllv3: support fractional multiplier on vf610 PLL1/PLL2

>> diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c >> index 19f9b622981a..24a9e914e0d5 100644 >> --- a/drivers/clk/imx/clk-pllv3.c >> +++ b/drivers/clk/imx/clk-pllv3.c >> @@ -288,6 +291,87 @@ static const struct clk_ops clk_pllv3_av_ops = { >> .set_rate =

Re: netlink: GPF in sock_sndtimeo

On 2016-12-09 23:40, Cong Wang wrote: > On Fri, Dec 9, 2016 at 8:13 PM, Cong Wang wrote: > > On Fri, Dec 9, 2016 at 3:01 AM, Richard Guy Briggs wrote: > >> On 2016-12-08 22:57, Cong Wang wrote: > >>> On Thu, Dec 8, 2016 at 10:02 PM, Richard Guy Briggs

Re: netlink: GPF in sock_sndtimeo

On 2016-12-09 23:40, Cong Wang wrote: > On Fri, Dec 9, 2016 at 8:13 PM, Cong Wang wrote: > > On Fri, Dec 9, 2016 at 3:01 AM, Richard Guy Briggs wrote: > >> On 2016-12-08 22:57, Cong Wang wrote: > >>> On Thu, Dec 8, 2016 at 10:02 PM, Richard Guy Briggs > >>> wrote: > >>> > I also tried to

Re: [PATCH] clk: imx: pllv3: support fractional multiplier on vf610 PLL1/PLL2

>> diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c >> index 19f9b622981a..24a9e914e0d5 100644 >> --- a/drivers/clk/imx/clk-pllv3.c >> +++ b/drivers/clk/imx/clk-pllv3.c >> @@ -288,6 +291,87 @@ static const struct clk_ops clk_pllv3_av_ops = { >> .set_rate =

Re: [PATCH] clk: imx: pllv3: support fractional multiplier on vf610 PLL1/PLL2

>> diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c >> index 19f9b622981a..24a9e914e0d5 100644 >> --- a/drivers/clk/imx/clk-pllv3.c >> +++ b/drivers/clk/imx/clk-pllv3.c >> @@ -288,6 +291,87 @@ static const struct clk_ops clk_pllv3_av_ops = { >> .set_rate =

[PATCH v5 1/2] usb: host: plat: Enable xhci plat runtime PM

Enable the xhci plat runtime PM for parent device to suspend/resume xhci. Also call pm_runtime_get_noresume() in probe() function in case the parent device doesn't call suspend/resume callback by runtime PM now. Signed-off-by: Baolin Wang --- Changes since v4: - No

[PATCH v5 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

For some mobile devices with strict power management, we also want to suspend the host when the slave is detached for power saving. Thus we add the host suspend/resume functions to support this requirement. Signed-off-by: Baolin Wang --- Changes since v4: - Remove

[PATCH v5 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

For some mobile devices with strict power management, we also want to suspend the host when the slave is detached for power saving. Thus we add the host suspend/resume functions to support this requirement. Signed-off-by: Baolin Wang --- Changes since v4: - Remove Kconfig and just enable host

[PATCH v5 1/2] usb: host: plat: Enable xhci plat runtime PM

Enable the xhci plat runtime PM for parent device to suspend/resume xhci. Also call pm_runtime_get_noresume() in probe() function in case the parent device doesn't call suspend/resume callback by runtime PM now. Signed-off-by: Baolin Wang --- Changes since v4: - No updates. Changes since v3:

Re: epoll_wait inaccurate timeout

On Mon, Dec 12, 2016 at 2:34 PM, Eric Wong wrote: > +Cc folks who may know about timer stuff on epoll. > > Dmitry Banschikov wrote: >> Hi! >> >> I have a problem caused by inaccurate timeouts in epoll_wait(2). >> Here are some parts of strace -tt output: > >

Re: epoll_wait inaccurate timeout

On Mon, Dec 12, 2016 at 2:34 PM, Eric Wong wrote: > +Cc folks who may know about timer stuff on epoll. > > Dmitry Banschikov wrote: >> Hi! >> >> I have a problem caused by inaccurate timeouts in epoll_wait(2). >> Here are some parts of strace -tt output: > > Which kernel version are you using?

[PATCHv2 4/5] perf tools: Allow to ignore missing pid

On Tue, Dec 13, 2016 at 01:58:25AM +0900, Namhyung Kim wrote: SNIP > > } > > > > +static bool ignore_missing_thread(struct perf_evsel *evsel, > > + struct thread_map *threads, > > + int thread, int err) > > +{ > > + if

[PATCHv2 4/5] perf tools: Allow to ignore missing pid

On Tue, Dec 13, 2016 at 01:58:25AM +0900, Namhyung Kim wrote: SNIP > > } > > > > +static bool ignore_missing_thread(struct perf_evsel *evsel, > > + struct thread_map *threads, > > + int thread, int err) > > +{ > > + if

Re: [PATCH] Input: ar1021-i2c - fix too long name in driver's device table

2016-12-13 0:57 GMT+01:00 Dmitry Torokhov : > The name field in structure i2c_device_id is 20 characters, and we > expect it to be NULL-terminated, however we are trying to stuff it with > 21 bytes and thus NULL-terminator is lost. This causes issues when one > creates

Re: [PATCH] Input: ar1021-i2c - fix too long name in driver's device table

2016-12-13 0:57 GMT+01:00 Dmitry Torokhov : > The name field in structure i2c_device_id is 20 characters, and we > expect it to be NULL-terminated, however we are trying to stuff it with > 21 bytes and thus NULL-terminator is lost. This causes issues when one > creates device with name

Re: [PATCH] clk: imx: pllv3: support fractional multiplier on vf610 PLL1/PLL2

On 12/09, Nikita Yushchenko wrote: > diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c > index 19f9b622981a..24a9e914e0d5 100644 > --- a/drivers/clk/imx/clk-pllv3.c > +++ b/drivers/clk/imx/clk-pllv3.c > @@ -288,6 +291,87 @@ static const struct clk_ops clk_pllv3_av_ops = { >

Re: [PATCH] clk: imx: pllv3: support fractional multiplier on vf610 PLL1/PLL2

On 12/09, Nikita Yushchenko wrote: > diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c > index 19f9b622981a..24a9e914e0d5 100644 > --- a/drivers/clk/imx/clk-pllv3.c > +++ b/drivers/clk/imx/clk-pllv3.c > @@ -288,6 +291,87 @@ static const struct clk_ops clk_pllv3_av_ops = { >

Re: [PATCH 3/5] firmware: revamp firmware documentation

On 12/13/2016 04:08 AM, Luis R. Rodriguez wrote: Understanding this code is getting out of control without any notes. Give the firmware_class driver a much needed documentation love, and while at it convert it to the new sphinx documentation format. It does help to understand the class/API,

Re: [PATCH 3/5] firmware: revamp firmware documentation

On 12/13/2016 04:08 AM, Luis R. Rodriguez wrote: Understanding this code is getting out of control without any notes. Give the firmware_class driver a much needed documentation love, and while at it convert it to the new sphinx documentation format. It does help to understand the class/API,

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Mon, 12 Dec 2016 10:48:47 +0100 Stanislav Kozina wrote: > A runtime check is still done, with per-module vermagic which distros > can change when they bump the ABI version. Is it really necessary to > have more than that (i.e., per-symbol versioning)? >

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Mon, 12 Dec 2016 10:48:47 +0100 Stanislav Kozina wrote: > A runtime check is still done, with per-module vermagic which distros > can change when they bump the ABI version. Is it really necessary to > have more than that (i.e., per-symbol versioning)? > >>> From my point of

Issue with DRM and "reimplement IDR and IDA using the radix tree"

Hi Matthew, Trying the latest -next on the Jetson TK1 board (with two different DRM devices and display and render), I noticed that the GPU device probe always failed with error -ENOSPC. After investigating I figured out that this was due to the minor device allocation failing when a second DRM

Issue with DRM and "reimplement IDR and IDA using the radix tree"

Hi Matthew, Trying the latest -next on the Jetson TK1 board (with two different DRM devices and display and render), I noticed that the GPU device probe always failed with error -ENOSPC. After investigating I figured out that this was due to the minor device allocation failing when a second DRM

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On 10/12/16 05:27 AM, Benjamin Herrenschmidt wrote: > On Fri, 2016-12-09 at 14:35 +0100, Daniel Vetter wrote: >>> As for multi userspace client, well, swapping an mmap between HW and >>> memory backing store is a somewhat solved problem already. >> >> Hm, I didn't know that, but then all existing

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On 10/12/16 05:27 AM, Benjamin Herrenschmidt wrote: > On Fri, 2016-12-09 at 14:35 +0100, Daniel Vetter wrote: >>> As for multi userspace client, well, swapping an mmap between HW and >>> memory backing store is a somewhat solved problem already. >> >> Hm, I didn't know that, but then all existing

[RFC][PATCH 1/5] usb: dwc2: Avoid sleeping while holding hsotg->lock

Basically when plugging in various cables in different orders, I'm occasionally seeing the following BUG splat: [ 86.215403] BUG: scheduling while atomic: kworker/u16:2/53/0x0002 [ 86.219164] usb 1-1: USB disconnect, device number 9 [ 86.226845] Preemption disabled at:[ 86.230218] []

[RFC][PATCH 4/5] usb: dwc2: Avoid suspending if we're in gadget mode

I've found when booting HiKey with the usb gadget cable attached if I then try to connect via adb, I get an infinite spew of: dwc2 f72c.usb: dwc2_hsotg_ep_sethalt(ep ffc0790ecb18 ep1out, 0) dwc2 f72c.usb: dwc2_hsotg_ep_sethalt(ep ffc0790eca18 ep1in, 0) It seems that the usb

[RFC][PATCH 1/5] usb: dwc2: Avoid sleeping while holding hsotg->lock

Basically when plugging in various cables in different orders, I'm occasionally seeing the following BUG splat: [ 86.215403] BUG: scheduling while atomic: kworker/u16:2/53/0x0002 [ 86.219164] usb 1-1: USB disconnect, device number 9 [ 86.226845] Preemption disabled at:[ 86.230218] []

[RFC][PATCH 4/5] usb: dwc2: Avoid suspending if we're in gadget mode

I've found when booting HiKey with the usb gadget cable attached if I then try to connect via adb, I get an infinite spew of: dwc2 f72c.usb: dwc2_hsotg_ep_sethalt(ep ffc0790ecb18 ep1out, 0) dwc2 f72c.usb: dwc2_hsotg_ep_sethalt(ep ffc0790eca18 ep1in, 0) It seems that the usb

[RFC][PATCH 2/5] usb: dwc2: Workaround case where GOTGCTL state is wrong

When removing a USB-A to USB-otg adapter cable, we get a change status irq, and then in dwc2_conn_id_status_change, we erroniously see the GOTGCTL_CONID_B flag set. This causes us to get stuck in the "while (!dwc2_is_device_mode(hsotg))" loop, spitting out "Waiting for Peripheral Mode, Mode=Host"

[RFC][PATCH 2/5] usb: dwc2: Workaround case where GOTGCTL state is wrong

When removing a USB-A to USB-otg adapter cable, we get a change status irq, and then in dwc2_conn_id_status_change, we erroniously see the GOTGCTL_CONID_B flag set. This causes us to get stuck in the "while (!dwc2_is_device_mode(hsotg))" loop, spitting out "Waiting for Peripheral Mode, Mode=Host"

[RFC][PATCH 0/5] Fixes and workarounds for dwc2 on HiKey board

I just wanted to send out my current queue of patches for dwc2 controller on the HiKey board. This does exclude my patchset[1] to add extcon support to dwc2, which John Youn suspects a pending rework of the dwc2 fifo init logic might make unnecssary. So in the meantime, I wanted to send out the

[RFC][PATCH 0/5] Fixes and workarounds for dwc2 on HiKey board

I just wanted to send out my current queue of patches for dwc2 controller on the HiKey board. This does exclude my patchset[1] to add extcon support to dwc2, which John Youn suspects a pending rework of the dwc2 fifo init logic might make unnecssary. So in the meantime, I wanted to send out the

[RFC][PATCH 5/5] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220

From: Chen Yu The Hi6220's usb controller is limited in that it does not support "Split Transactions", so it does not support communicating with low-speed and full-speed devices behind a high-speed hub. Thus it requires a quirk so that we can manually drop the usb speed

[RFC][PATCH 3/5] usb: dwc2: Force port resume on switching to device mode

From: Chen Yu We've seen failures when switching between host and gadget mode, which was diagnosed as being caused due to the bus being auto-suspended when we switched. So this patch forces a port resume when switching to device mode if the bus is suspended. Cc: Wei Xu

[RFC][PATCH 5/5] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220

From: Chen Yu The Hi6220's usb controller is limited in that it does not support "Split Transactions", so it does not support communicating with low-speed and full-speed devices behind a high-speed hub. Thus it requires a quirk so that we can manually drop the usb speed when low/full-speed are

[RFC][PATCH 3/5] usb: dwc2: Force port resume on switching to device mode

From: Chen Yu We've seen failures when switching between host and gadget mode, which was diagnosed as being caused due to the bus being auto-suspended when we switched. So this patch forces a port resume when switching to device mode if the bus is suspended. Cc: Wei Xu Cc: Guodong Xu Cc:

[GIT PULL] s390 patches for 4.10 merge window #1

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: The main bulk of the s390 patches for the 4.10 merge window: * Add support for the contiguous memory allocator. * The recovery

[GIT PULL] s390 patches for 4.10 merge window #1

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: The main bulk of the s390 patches for the 4.10 merge window: * Add support for the contiguous memory allocator. * The recovery

[GIT PULL] xen: features and fixes for 4.10 rc0

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.10-rc0-tag xen: features and fixes for 4.10 rc0 These are some fixes, a move of some arm related headers to share them between arm and arm64 and a series introducing a helper to

[GIT PULL] xen: features and fixes for 4.10 rc0

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.10-rc0-tag xen: features and fixes for 4.10 rc0 These are some fixes, a move of some arm related headers to share them between arm and arm64 and a series introducing a helper to

Re: [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86

Hi Sai, On Wed, Dec 07, 2016 at 12:13:28PM -0800, Sai Praneeth Prakhya wrote: > On Wed, 2016-12-07 at 20:04 +, Matt Fleming wrote: > > On Wed, 07 Dec, at 11:01:06AM, Sai Praneeth Prakhya wrote: > > > > > > Thanks Matt! > > > > > > Would you like to see a new version of these patch series

Re: [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86

Hi Sai, On Wed, Dec 07, 2016 at 12:13:28PM -0800, Sai Praneeth Prakhya wrote: > On Wed, 2016-12-07 at 20:04 +, Matt Fleming wrote: > > On Wed, 07 Dec, at 11:01:06AM, Sai Praneeth Prakhya wrote: > > > > > > Thanks Matt! > > > > > > Would you like to see a new version of these patch series

Re: CVE-2016-7097 causes acl leak

On Mon, Dec 12, 2016 at 4:26 PM, Mark Salyzyn wrote: > > The leaks were introduced in 9p, gfs2, jfs and xfs drivers only. Only the 9p case is obvious to me: diff --git a/fs/9p/acl.c b/fs/9p/acl.c index b3c2cc7..082d227 100644 --- a/fs/9p/acl.c +++ b/fs/9p/acl.c @@ -277,6

Re: CVE-2016-7097 causes acl leak

On Mon, Dec 12, 2016 at 4:26 PM, Mark Salyzyn wrote: > > The leaks were introduced in 9p, gfs2, jfs and xfs drivers only. Only the 9p case is obvious to me: diff --git a/fs/9p/acl.c b/fs/9p/acl.c index b3c2cc7..082d227 100644 --- a/fs/9p/acl.c +++ b/fs/9p/acl.c @@ -277,6 +277,7 @@ static int

Re: [PATCH] SPCR: check bit width for the 16550 UART

On 12/07/2016 10:23 AM, Mark Salter wrote: > On Tue, 2016-12-06 at 01:34 -0500, Jon Masters wrote: >> On 12/05/2016 10:55 PM, Duc Dang wrote: >>> On Mon, Dec 5, 2016 at 6:27 PM, Jon Masters wrote: HOWEVER while the console does come up, the use of "earlycon" on the

Re: [PATCH] SPCR: check bit width for the 16550 UART

On 12/07/2016 10:23 AM, Mark Salter wrote: > On Tue, 2016-12-06 at 01:34 -0500, Jon Masters wrote: >> On 12/05/2016 10:55 PM, Duc Dang wrote: >>> On Mon, Dec 5, 2016 at 6:27 PM, Jon Masters wrote: HOWEVER while the console does come up, the use of "earlycon" on the command line (with

Re: [PATCH 4/5] firmware: add SmPL report for custom fallback mechanism

On Mon, 12 Dec 2016, Luis R. Rodriguez wrote: > Even though most distributions today disable the fallback mechanism > by default we've determined that we cannot remove them from the kernel. > This is not well understood so document the reason and logic behind that. > > Recent discussions

Re: [PATCH 4/5] firmware: add SmPL report for custom fallback mechanism

On Mon, 12 Dec 2016, Luis R. Rodriguez wrote: > Even though most distributions today disable the fallback mechanism > by default we've determined that we cannot remove them from the kernel. > This is not well understood so document the reason and logic behind that. > > Recent discussions

Re: [PATCH v3 1/4] pinctrl: aspeed: Read and write bits in LPC and GFX controllers

On Mon, 2016-12-12 at 10:27 -0600, Rob Herring wrote: > On Tue, Dec 06, 2016 at 02:11:49PM +1100, Andrew Jeffery wrote: > > The System Control Unit IP block in the Aspeed SoCs is typically where > > the pinmux configuration is found, but not always. A number of pins > > depend on state in one of

Re: [PATCH v3 1/4] pinctrl: aspeed: Read and write bits in LPC and GFX controllers

On Mon, 2016-12-12 at 10:27 -0600, Rob Herring wrote: > On Tue, Dec 06, 2016 at 02:11:49PM +1100, Andrew Jeffery wrote: > > The System Control Unit IP block in the Aspeed SoCs is typically where > > the pinmux configuration is found, but not always. A number of pins > > depend on state in one of

linux-next: Tree for Dec 13

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161212: The hid tree lost its build failure. The spi tree lost its build failure. Non-merge commits (relative to Linus' tree): 8829 7664 files

linux-next: Tree for Dec 13

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161212: The hid tree lost its build failure. The spi tree lost its build failure. Non-merge commits (relative to Linus' tree): 8829 7664 files

[PATCH v2] btrfs: limit async_work allocation and worker func duration

Problem statement: unprivileged user who has read-write access to more than one btrfs subvolume may easily consume all kernel memory (eventually triggering oom-killer). Reproducer (./mkrmdir below essentially loops over mkdir/rmdir): [root@kteam1 ~]# cat prep.sh DEV=/dev/sdb mkfs.btrfs -f $DEV

[PATCH v2] btrfs: limit async_work allocation and worker func duration

Problem statement: unprivileged user who has read-write access to more than one btrfs subvolume may easily consume all kernel memory (eventually triggering oom-killer). Reproducer (./mkrmdir below essentially loops over mkdir/rmdir): [root@kteam1 ~]# cat prep.sh DEV=/dev/sdb mkfs.btrfs -f $DEV

[PATCH v2] kasan: Support for r/w instrumentation control

This provide option to control sanity of read and write operations Both read and write instrumentation increase size of uImage, So using this option read or write instrumentation can be avoided if not required. Useful in case of module sanity, using this uImage sanity can be avoided. Also user

[PATCH v2] kasan: Support for r/w instrumentation control

This provide option to control sanity of read and write operations Both read and write instrumentation increase size of uImage, So using this option read or write instrumentation can be avoided if not required. Useful in case of module sanity, using this uImage sanity can be avoided. Also user

Re: [PATCH] Input: ar1021-i2c - fix too long name in driver's device table

On Mon, Dec 12, 2016 at 03:57:02PM -0800, Dmitry Torokhov wrote: > The name field in structure i2c_device_id is 20 characters, and we > expect it to be NULL-terminated, however we are trying to stuff it with > 21 bytes and thus NULL-terminator is lost. This causes issues when one > creates device

Re: [PATCH] Input: ar1021-i2c - fix too long name in driver's device table

On Mon, Dec 12, 2016 at 03:57:02PM -0800, Dmitry Torokhov wrote: > The name field in structure i2c_device_id is 20 characters, and we > expect it to be NULL-terminated, however we are trying to stuff it with > 21 bytes and thus NULL-terminator is lost. This causes issues when one > creates device

[GIT PULL] Thermal management updates for v4.10-rc1

Hi, Linus, Please pull from   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next to receive the latest Thermal Management updates for v4.10-rc1 with top-most commit 0faf7dd5a947006978b549dfe29a01b710becf4a:   MAINTAINERS: Samsung: Update maintainer for PWM FAN and SAMSUNG

[GIT PULL] Thermal management updates for v4.10-rc1

Hi, Linus, Please pull from   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next to receive the latest Thermal Management updates for v4.10-rc1 with top-most commit 0faf7dd5a947006978b549dfe29a01b710becf4a:   MAINTAINERS: Samsung: Update maintainer for PWM FAN and SAMSUNG

[PATCH RFC] [media] m5mols: add missing dependency on VIDEO_IR_I2C

tings include MEDIA_SUBDRV_AUTOSELECT=y the "I2C module for IR" submenu (CONFIG_VIDEO_IR_I2C) is not displayed adding the VIDEO_IR_I2C to the dependency list makes this clear Q: should a patch like this carry a Fixes: tag ? Patch was tested against: x86_64_defconfig Patch is against 4.9.

[PATCH RFC] [media] m5mols: add missing dependency on VIDEO_IR_I2C

SUBDRV_AUTOSELECT=y the "I2C module for IR" submenu (CONFIG_VIDEO_IR_I2C) is not displayed adding the VIDEO_IR_I2C to the dependency list makes this clear Q: should a patch like this carry a Fixes: tag ? Patch was tested against: x86_64_defconfig Patch is against 4.9.0 (localversion-next

DO YOU NEED A LOAN??

Are you in need of a loan? Apply for more details.

DO YOU NEED A LOAN??

Are you in need of a loan? Apply for more details.

[PATCH] [media] m5mols: set usleep_range delta greater 0

config + CONFIG_MEDIA_SUPPORT=m MEDIA_CAMERA_SUPPORT=y, VIDEO_V4L2_SUBDEV_API, MEDIA_DIGITAL_TV-_SUPPORT=y MEDIA_RC_SUPPORT=y, MEDIA_CONTROLLER=y, VIDEO_V4L2_SUBDEV_API=y MEDIA_SUBDRV_AUTOSELECT=n, CONFIG_VIDEO_M5MOLS=m Patch is against 4.9.0 (localversion-next is next-20161212) drivers/media/i2c/m5mols/m5mols_

[PATCH] [media] m5mols: set usleep_range delta greater 0

MEDIA_CAMERA_SUPPORT=y, VIDEO_V4L2_SUBDEV_API, MEDIA_DIGITAL_TV-_SUPPORT=y MEDIA_RC_SUPPORT=y, MEDIA_CONTROLLER=y, VIDEO_V4L2_SUBDEV_API=y MEDIA_SUBDRV_AUTOSELECT=n, CONFIG_VIDEO_M5MOLS=m Patch is against 4.9.0 (localversion-next is next-20161212) drivers/media/i2c/m5mols/m5mols_core.c | 5 +++-- 1 file

Re: [PATCH v2] audit: use proper refcount locking on audit_sock

On 2016-12-12 15:18, Paul Moore wrote: > On Mon, Dec 12, 2016 at 5:03 AM, Richard Guy Briggs wrote: > > Resetting audit_sock appears to be racy. > > > > audit_sock was being copied and dereferenced without using a refcount on > > the source sock. > > > > Bump the refcount on the

Re: [PATCH v2] audit: use proper refcount locking on audit_sock

On 2016-12-12 15:18, Paul Moore wrote: > On Mon, Dec 12, 2016 at 5:03 AM, Richard Guy Briggs wrote: > > Resetting audit_sock appears to be racy. > > > > audit_sock was being copied and dereferenced without using a refcount on > > the source sock. > > > > Bump the refcount on the underlying sock

Re: [PATCH v3 6/6] mfd: dt: Move syscon bindings to syscon subdirectory

On Mon, 2016-12-12 at 09:39 -0600, Rob Herring wrote: > On Tue, Dec 06, 2016 at 01:53:21PM +1100, Andrew Jeffery wrote: > > The use of syscons is growing, lets collate them in their own part of > > the bindings tree. > > > > > > Signed-off-by: Andrew Jeffery > > --- > >  

Re: [PATCH v3 6/6] mfd: dt: Move syscon bindings to syscon subdirectory

On Mon, 2016-12-12 at 09:39 -0600, Rob Herring wrote: > On Tue, Dec 06, 2016 at 01:53:21PM +1100, Andrew Jeffery wrote: > > The use of syscons is growing, lets collate them in their own part of > > the bindings tree. > > > > > > Signed-off-by: Andrew Jeffery > > --- > >  

Re: [PATCH v2] audit: use proper refcount locking on audit_sock

On 2016-12-12 12:10, Paul Moore wrote: > On Mon, Dec 12, 2016 at 5:03 AM, Richard Guy Briggs wrote: > > Resetting audit_sock appears to be racy. > > > > audit_sock was being copied and dereferenced without using a refcount on > > the source sock. > > > > Bump the refcount on the

Re: [PATCH v2] audit: use proper refcount locking on audit_sock

On 2016-12-12 12:10, Paul Moore wrote: > On Mon, Dec 12, 2016 at 5:03 AM, Richard Guy Briggs wrote: > > Resetting audit_sock appears to be racy. > > > > audit_sock was being copied and dereferenced without using a refcount on > > the source sock. > > > > Bump the refcount on the underlying sock

Re: [PATCH v3 4/6] mfd: dt: Add bindings for the Aspeed LPC Host Controller (LHC)

On Mon, 2016-12-12 at 09:30 -0600, Rob Herring wrote: > On Tue, Dec 06, 2016 at 01:53:19PM +1100, Andrew Jeffery wrote: > > The LPC bus pinmux configuration on fifth generation Aspeed SoCs depends > > on bits in both the System Control Unit and the LPC Host Controller. > > > > The Aspeed LPC Host

Re: [PATCH v3 4/6] mfd: dt: Add bindings for the Aspeed LPC Host Controller (LHC)

On Mon, 2016-12-12 at 09:30 -0600, Rob Herring wrote: > On Tue, Dec 06, 2016 at 01:53:19PM +1100, Andrew Jeffery wrote: > > The LPC bus pinmux configuration on fifth generation Aspeed SoCs depends > > on bits in both the System Control Unit and the LPC Host Controller. > > > > The Aspeed LPC Host

Re: [PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Hi Rob. 2016-12-13 2:14 GMT+09:00 Rob Herring : >> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-cadence.txt >> b/Documentation/devicetree/bindings/mmc/sdhci-cadence.txt >> new file mode 100644 >> index 000..750374f >> --- /dev/null >> +++

Re: [PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Hi Rob. 2016-12-13 2:14 GMT+09:00 Rob Herring : >> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-cadence.txt >> b/Documentation/devicetree/bindings/mmc/sdhci-cadence.txt >> new file mode 100644 >> index 000..750374f >> --- /dev/null >> +++

Re: [PATCH V2 for-next 00/11] Code improvements & fixes for HNS RoCE driver

On 11/15/2016 1:10 PM, Salil Mehta wrote: > This patchset introduces some code improvements and fixes > for the identified problems in the HNS RoCE driver. > > Lijun Ou (4): > IB/hns: Add the interface for querying QP1 > IB/hns: add self loopback for CM > IB/hns: Modify the condition of

Re: [PATCH V2 for-next 00/11] Code improvements & fixes for HNS RoCE driver

On 11/15/2016 1:10 PM, Salil Mehta wrote: > This patchset introduces some code improvements and fixes > for the identified problems in the HNS RoCE driver. > > Lijun Ou (4): > IB/hns: Add the interface for querying QP1 > IB/hns: add self loopback for CM > IB/hns: Modify the condition of

Re: [GIT pull] x86/cache: Updates for 4.10

On Mon, Dec 12, 2016 at 1:53 AM, Thomas Gleixner wrote: > > This update provides the support for Intel Cache Allocation Technology, a > cache partitioning mechanism. Ugh, this is some funky stuff. And it's entirely x86-specific, with a rather odd special filesystem interface.

Re: [GIT pull] x86/cache: Updates for 4.10

On Mon, Dec 12, 2016 at 1:53 AM, Thomas Gleixner wrote: > > This update provides the support for Intel Cache Allocation Technology, a > cache partitioning mechanism. Ugh, this is some funky stuff. And it's entirely x86-specific, with a rather odd special filesystem interface. It looks pretty

[PATCH v2] ACPI/NUMA: Do not map pxm to node when NUMA is turned off

Otherwise we may unexpectedly reference a non-zero node via, for example, acpi_get_node() while other parts of the kernel assume that only node 0 (which is what NUMA_NO_NODE is supposed to be converted to) is available. Signed-off-by: Boris Ostrovsky --- V2: * Drop

[PATCH v2] ACPI/NUMA: Do not map pxm to node when NUMA is turned off

Otherwise we may unexpectedly reference a non-zero node via, for example, acpi_get_node() while other parts of the kernel assume that only node 0 (which is what NUMA_NO_NODE is supposed to be converted to) is available. Signed-off-by: Boris Ostrovsky --- V2: * Drop __initdata from x86's numa_off

RE: [PATCH v2 9/9] NTB: Add ntb.h comments

From: Serge Semin > > Signed-off-by: Serge Semin > > --- > include/linux/ntb.h | 17 +++-- > 1 file changed, 11 insertions(+), 6 deletions(-) > > diff --git a/include/linux/ntb.h b/include/linux/ntb.h > index fe0437c..c5a369c 100644 > ---

RE: [PATCH v2 9/9] NTB: Add ntb.h comments

From: Serge Semin > > Signed-off-by: Serge Semin > > --- > include/linux/ntb.h | 17 +++-- > 1 file changed, 11 insertions(+), 6 deletions(-) > > diff --git a/include/linux/ntb.h b/include/linux/ntb.h > index fe0437c..c5a369c 100644 > --- a/include/linux/ntb.h > +++

RE: [PATCH v2 7/9] NTB: Add new Memory Windows API documentation

From: Serge Semin > Since the new API slightly changes the way a typical NTB client driver > works, the documentation file needs to be appropriately updated. > > Signed-off-by: Serge Semin Acked-by: Allen Hubbe > > --- > Documentation/ntb.txt |

RE: [PATCH v2 8/9] NTB: Add PCIe Gen4 link speed

From: Serge Semin > > Signed-off-by: Serge Semin Acked-by: Allen Hubbe > > --- > include/linux/ntb.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/linux/ntb.h b/include/linux/ntb.h > index 90746df..fe0437c 100644 > ---

RE: [PATCH v2 7/9] NTB: Add new Memory Windows API documentation

From: Serge Semin > Since the new API slightly changes the way a typical NTB client driver > works, the documentation file needs to be appropriately updated. > > Signed-off-by: Serge Semin Acked-by: Allen Hubbe > > --- > Documentation/ntb.txt | 99 >

RE: [PATCH v2 8/9] NTB: Add PCIe Gen4 link speed

From: Serge Semin > > Signed-off-by: Serge Semin Acked-by: Allen Hubbe > > --- > include/linux/ntb.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/linux/ntb.h b/include/linux/ntb.h > index 90746df..fe0437c 100644 > --- a/include/linux/ntb.h > +++ b/include/linux/ntb.h

RE: [PATCH v2 6/9] NTB: Add Messaging NTB API

From: Serge Semin > Some IDT NTB-capable PCIe-switches have message registers to communicate with > peer devices. This patch adds new NTB API callback methods, which can be used > to utilize these registers functionality: > ntb_msg_count(); - get number of message registers > ntb_msg_inbits(); -

RE: [PATCH v2 6/9] NTB: Add Messaging NTB API

From: Serge Semin > Some IDT NTB-capable PCIe-switches have message registers to communicate with > peer devices. This patch adds new NTB API callback methods, which can be used > to utilize these registers functionality: > ntb_msg_count(); - get number of message registers > ntb_msg_inbits(); -

RE: [PATCH v2 5/9] NTB: Alter Scratchpads API to support multi-ports devices

From: Serge Semin > Even though there is no any real NTB hardware, which would have both more > than two ports and Scratchpad registers, it is logically correct to have > Scratchpad API accepting a peer port index as well. Intel/AMD drivers utilize > Primary and Secondary topology to split

RE: [PATCH v2 5/9] NTB: Alter Scratchpads API to support multi-ports devices

From: Serge Semin > Even though there is no any real NTB hardware, which would have both more > than two ports and Scratchpad registers, it is logically correct to have > Scratchpad API accepting a peer port index as well. Intel/AMD drivers utilize > Primary and Secondary topology to split

  1   2   3   4   5   6   7   8   9   10   >