Re: linux-next: manual merge of the char-misc tree with the lightnvm tree

On 11/22/2016 08:29 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in: > > drivers/lightnvm/core.c > > between commit: > > 7b0d392f6957 ("lightnvm: remove sysfs configuration interface") > > from the lightnvm tree and commit: > >

Re: linux-next: manual merge of the char-misc tree with the lightnvm tree

On 11/22/2016 08:29 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in: > > drivers/lightnvm/core.c > > between commit: > > 7b0d392f6957 ("lightnvm: remove sysfs configuration interface") > > from the lightnvm tree and commit: > >

Re: linux-next: manual merge of the char-misc tree with the lightnvm tree

On Tue, Nov 22, 2016 at 06:29:08PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in: > > drivers/lightnvm/core.c > > between commit: > > 7b0d392f6957 ("lightnvm: remove sysfs configuration interface") > > from the lightnvm tree

Re: linux-next: manual merge of the char-misc tree with the lightnvm tree

On Tue, Nov 22, 2016 at 06:29:08PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in: > > drivers/lightnvm/core.c > > between commit: > > 7b0d392f6957 ("lightnvm: remove sysfs configuration interface") > > from the lightnvm tree

Re: [PATCH 2/3] thermal: rockchip: improve conversion error messages

On Tue, 2016-11-22 at 09:51 +0800, Caesar Wang wrote: > 在 2016年11月19日 11:31, Caesar Wang 写道: > > > > Brian, > > > > 在 2016年11月19日 07:52, Brian Norris 写道: > > > > > > These error messages don't give much information about what went > > > wrong. > > > It would be nice, for one, to see what

Re: [PATCH 2/3] thermal: rockchip: improve conversion error messages

On Tue, 2016-11-22 at 09:51 +0800, Caesar Wang wrote: > 在 2016年11月19日 11:31, Caesar Wang 写道: > > > > Brian, > > > > 在 2016年11月19日 07:52, Brian Norris 写道: > > > > > > These error messages don't give much information about what went > > > wrong. > > > It would be nice, for one, to see what

[PATCH] video: imxfb: correct the bitmask for DMACR_HM/_TM

The HM and TM fields in the LCDC DMA Control Register are 7 bits wide. Use the correct mask to allow setting all possible bits. Signed-off-by: Martin Kaiser --- This bug was discovered on a board that uses DMACR_TM(16). We ended up with TM==0 in the register, the upper three

[PATCH] video: imxfb: correct the bitmask for DMACR_HM/_TM

The HM and TM fields in the LCDC DMA Control Register are 7 bits wide. Use the correct mask to allow setting all possible bits. Signed-off-by: Martin Kaiser --- This bug was discovered on a board that uses DMACR_TM(16). We ended up with TM==0 in the register, the upper three bits were filtered

Re: [PATCH 1/3] thermal: handle get_temp() errors properly

Hi, Brian, On Fri, 2016-11-18 at 21:30 -0800, Brian Norris wrote: > Hi, > > On Fri, Nov 18, 2016 at 07:41:59PM -0800, Eduardo Valentin wrote: > > > > On Fri, Nov 18, 2016 at 03:52:55PM -0800, Brian Norris wrote: > > > > > > If using CONFIG_THERMAL_EMULATION, there's a corner case where we > >

Re: [PATCH 1/3] thermal: handle get_temp() errors properly

Hi, Brian, On Fri, 2016-11-18 at 21:30 -0800, Brian Norris wrote: > Hi, > > On Fri, Nov 18, 2016 at 07:41:59PM -0800, Eduardo Valentin wrote: > > > > On Fri, Nov 18, 2016 at 03:52:55PM -0800, Brian Norris wrote: > > > > > > If using CONFIG_THERMAL_EMULATION, there's a corner case where we > >

Re: [PATCH] ARM: dts: exynos: remove the cd-gpios property for eMMC of odroid-xu3/4

On 22.11.2016 02:24, Jaehoon Chung wrote: > On 11/22/2016 02:06 AM, Krzysztof Kozlowski wrote: >> On Mon, Nov 21, 2016 at 04:10:32PM +0900, Jaehoon Chung wrote: >>> Odroid-xu3/4 didn't need to use the cd-gpios for detecting card. >>> Because Host controller has the CDETECT register through SDx_CDN

Re: [PATCH] ARM: dts: exynos: remove the cd-gpios property for eMMC of odroid-xu3/4

On 22.11.2016 02:24, Jaehoon Chung wrote: > On 11/22/2016 02:06 AM, Krzysztof Kozlowski wrote: >> On Mon, Nov 21, 2016 at 04:10:32PM +0900, Jaehoon Chung wrote: >>> Odroid-xu3/4 didn't need to use the cd-gpios for detecting card. >>> Because Host controller has the CDETECT register through SDx_CDN

Re: [PATCH 2/2] phy: qcom-qmp: new qmp phy driver for qcom-chipsets

Hi Kishon, On Thu, Nov 10, 2016 at 2:33 PM, Vivek Gautam wrote: > Hi Kishon, > >>> +unsigned int msm8996_pciephy_tx_offsets[] = { 0x1000, 0x2000, 0x3000 }; >>> +unsigned int msm8996_pciephy_rx_offsets[] = { 0x1200, 0x2200, 0x3200 }; >>> +unsigned int

Re: [PATCH 2/2] phy: qcom-qmp: new qmp phy driver for qcom-chipsets

Hi Kishon, On Thu, Nov 10, 2016 at 2:33 PM, Vivek Gautam wrote: > Hi Kishon, > >>> +unsigned int msm8996_pciephy_tx_offsets[] = { 0x1000, 0x2000, 0x3000 }; >>> +unsigned int msm8996_pciephy_rx_offsets[] = { 0x1200, 0x2200, 0x3200 }; >>> +unsigned int msm8996_pciephy_pcs_offsets[] = { 0x1400,

ATTENZIONE

ATTENZIONE; La cassetta postale ha superato il limite di archiviazione, che è 5 GB come definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella

ATTENZIONE

ATTENZIONE; La cassetta postale ha superato il limite di archiviazione, che è 5 GB come definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella

linux-next: build warning after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/scsi/hpsa.c: In function 'hpsa_slave_alloc': drivers/scsi/hpsa.c:2033:5: warning: 'sd' may be used uninitialized in this function [-Wmaybe-uninitialized] if (!sd) ^

linux-next: build warning after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/scsi/hpsa.c: In function 'hpsa_slave_alloc': drivers/scsi/hpsa.c:2033:5: warning: 'sd' may be used uninitialized in this function [-Wmaybe-uninitialized] if (!sd) ^

RE: [PATCH V5 2/2] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: 21 November 2016 22:32 > To: Gabriele Paoloni > Cc: liudongdong (C); a...@arndb.de; raf...@kernel.org; > lorenzo.pieral...@arm.com; t...@semihalf.com; Wangzhou (B); > pratyush.an...@gmail.com;

RE: [PATCH V5 2/2] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: 21 November 2016 22:32 > To: Gabriele Paoloni > Cc: liudongdong (C); a...@arndb.de; raf...@kernel.org; > lorenzo.pieral...@arm.com; t...@semihalf.com; Wangzhou (B); > pratyush.an...@gmail.com;

[PATCH] devicetree: bindings: Add vendor prefix for Andes Technology Corporation

Add vendor-prefix for Andes Technology Corporation Signed-off-by: Greentime Hu --- .../devicetree/bindings/vendor-prefixes.txt|1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt

[PATCH] devicetree: bindings: Add vendor prefix for Andes Technology Corporation

Add vendor-prefix for Andes Technology Corporation Signed-off-by: Greentime Hu --- .../devicetree/bindings/vendor-prefixes.txt|1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt

Re: [PATCH 05/12] bcache: debug: avoid to access .bi_io_vec directly

On Fri, Nov 11, 2016 at 08:05:33PM +0800, Ming Lei wrote: > Instead we use standard iterator way to do that. > > Signed-off-by: Ming Lei Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH 05/12] bcache: debug: avoid to access .bi_io_vec directly

On Fri, Nov 11, 2016 at 08:05:33PM +0800, Ming Lei wrote: > Instead we use standard iterator way to do that. > > Signed-off-by: Ming Lei Looks fine, Reviewed-by: Christoph Hellwig

linux-next: manual merge of the char-misc tree with the lightnvm tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/lightnvm/core.c between commit: 7b0d392f6957 ("lightnvm: remove sysfs configuration interface") from the lightnvm tree and commit: 389b2a1c0e90 ("lightnvm: make core.c explicitly non-modular") from the

linux-next: manual merge of the char-misc tree with the lightnvm tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/lightnvm/core.c between commit: 7b0d392f6957 ("lightnvm: remove sysfs configuration interface") from the lightnvm tree and commit: 389b2a1c0e90 ("lightnvm: make core.c explicitly non-modular") from the

Re: [PATCH 07/12] dm: use bvec iterator helpers to implement .get_page and .next_page

Jens, can you apply the non-dm patches?

Re: [PATCH 07/12] dm: use bvec iterator helpers to implement .get_page and .next_page

Jens, can you apply the non-dm patches?

Re: fsldma: t4240qds: drop "SG" CAP for DMA3

On Mon, Nov 21, 2016 at 12:52:49PM +0800, yanjiang@windriver.com wrote: > From: Yanjiang Jin > > T4240QDS DMA controller uses the external DMA control signals to start or > restart a paused DMA transfer, acknowledge a DMA transfer in progress and > also indicates

Re: fsldma: t4240qds: drop "SG" CAP for DMA3

On Mon, Nov 21, 2016 at 12:52:49PM +0800, yanjiang@windriver.com wrote: > From: Yanjiang Jin > > T4240QDS DMA controller uses the external DMA control signals to start or > restart a paused DMA transfer, acknowledge a DMA transfer in progress and > also indicates a transfer completion. >

Re: [PATCH] spi: spi-ti-qspi: reinit of completion variable

Did anybody got chance to review this patch? I feel this is a trivial yet required fix. On Tue, Nov 15, 2016 at 11:56 PM, Prahlad V wrote: > > completion variable should be reinitialized before reusing. > > Signed-off-by: Prahlad V > --- >

Re: [PATCH] spi: spi-ti-qspi: reinit of completion variable

Did anybody got chance to review this patch? I feel this is a trivial yet required fix. On Tue, Nov 15, 2016 at 11:56 PM, Prahlad V wrote: > > completion variable should be reinitialized before reusing. > > Signed-off-by: Prahlad V > --- > drivers/spi/spi-ti-qspi.c | 1 + > 1 file changed, 1

Re: [PATCH v2] iio: adc: New driver for TI ADS7950 chips

On 21 November 2016 22:54:24 GMT+00:00, Peter Meerwald-Stadler wrote: > >> > +static int ti_ads7950_read_raw(struct iio_dev *indio_dev, >> > + struct iio_chan_spec const *chan, >> > + int *val, int *val2, long m) >> > +{ >> > +

Re: [PATCH v2] iio: adc: New driver for TI ADS7950 chips

On 21 November 2016 22:54:24 GMT+00:00, Peter Meerwald-Stadler wrote: > >> > +static int ti_ads7950_read_raw(struct iio_dev *indio_dev, >> > + struct iio_chan_spec const *chan, >> > + int *val, int *val2, long m) >> > +{ >> > + struct

[PATCH v3 2/3] spi: spi-fsl-dspi: Fix continuous selection format

Current DMA implementation was not handling the continuous selection format viz. SPI chip select would be deasserted even between sequential serial transfers. Use existing dspi_data_to_pushr function to restructure the transmit code path and set or reset the CONT bit on same lines as code path in

[PATCH v3 2/3] spi: spi-fsl-dspi: Fix continuous selection format

Current DMA implementation was not handling the continuous selection format viz. SPI chip select would be deasserted even between sequential serial transfers. Use existing dspi_data_to_pushr function to restructure the transmit code path and set or reset the CONT bit on same lines as code path in

[PATCH v3 0/3] Fixes for Vybrid SPI DMA implementation

Hello, This v3 set of patches have fixes for Vybrid SPI DMA implementation and is rebased on top of latest topic/fsl-dspi. http://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/log/?h=topic/fsl-dspi The patches have been tested on a Toradex Colibri Vybrid VF61 module and now incoporate

[PATCH v3 3/3] spi: spi-fsl-dspi: Fix incorrect freeing of DMA allocated buffers

Buffers allocated with a call to dma_alloc_coherent should be freed with dma_free_coherent instead of the currently used devm_kfree. Signed-off-by: Sanchayan Maity --- drivers/spi/spi-fsl-dspi.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

[PATCH v3 1/3] spi: spi-fsl-dspi: Fix incorrect DMA setup

Currently dmaengine_prep_slave_single was being called with length set to the complete DMA buffer size. This resulted in unwanted bytes being transferred to the SPI register leading to clock and MOSI lines having unwanted data even after chip select got deasserted and the required bytes having

[PATCH v3 0/3] Fixes for Vybrid SPI DMA implementation

Hello, This v3 set of patches have fixes for Vybrid SPI DMA implementation and is rebased on top of latest topic/fsl-dspi. http://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/log/?h=topic/fsl-dspi The patches have been tested on a Toradex Colibri Vybrid VF61 module and now incoporate

[PATCH v3 3/3] spi: spi-fsl-dspi: Fix incorrect freeing of DMA allocated buffers

Buffers allocated with a call to dma_alloc_coherent should be freed with dma_free_coherent instead of the currently used devm_kfree. Signed-off-by: Sanchayan Maity --- drivers/spi/spi-fsl-dspi.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/spi/spi-fsl-dspi.c

[PATCH v3 1/3] spi: spi-fsl-dspi: Fix incorrect DMA setup

Currently dmaengine_prep_slave_single was being called with length set to the complete DMA buffer size. This resulted in unwanted bytes being transferred to the SPI register leading to clock and MOSI lines having unwanted data even after chip select got deasserted and the required bytes having

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

Hi Arnaldo, Could you please take a look at this? Thanks, Namhyung On Wed, Nov 16, 2016 at 03:06:26PM +0900, Namhyung Kim wrote: > Hello, > > This patchset is a rebased version of David's sched timehist work [1]. > I plan to improve perf sched command more and think that having > timehist

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

Hi Arnaldo, Could you please take a look at this? Thanks, Namhyung On Wed, Nov 16, 2016 at 03:06:26PM +0900, Namhyung Kim wrote: > Hello, > > This patchset is a rebased version of David's sched timehist work [1]. > I plan to improve perf sched command more and think that having > timehist

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

Hi Jiri, On Wed, Nov 16, 2016 at 04:34:28PM +0100, Jiri Olsa wrote: > On Wed, Nov 16, 2016 at 03:06:26PM +0900, Namhyung Kim wrote: > > Hello, > > > > This patchset is a rebased version of David's sched timehist work [1]. > > I plan to improve perf sched command more and think that having > >

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

Hi Jiri, On Wed, Nov 16, 2016 at 04:34:28PM +0100, Jiri Olsa wrote: > On Wed, Nov 16, 2016 at 03:06:26PM +0900, Namhyung Kim wrote: > > Hello, > > > > This patchset is a rebased version of David's sched timehist work [1]. > > I plan to improve perf sched command more and think that having > >

Re: [PATCH 2/2] tools lib traceevent: Use USECS_PER_SEC instead of hardcoded number

On Mon, Nov 21, 2016 at 11:41:49AM -0500, Steven Rostedt wrote: > On Fri, 18 Nov 2016 20:40:22 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Fri, Nov 18, 2016 at 05:54:01PM -0500, Steven Rostedt escreveu: > > > From: "Steven Rostedt (Red Hat)" > > > > >

Re: [PATCH 2/2] tools lib traceevent: Use USECS_PER_SEC instead of hardcoded number

On Mon, Nov 21, 2016 at 11:41:49AM -0500, Steven Rostedt wrote: > On Fri, 18 Nov 2016 20:40:22 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Fri, Nov 18, 2016 at 05:54:01PM -0500, Steven Rostedt escreveu: > > > From: "Steven Rostedt (Red Hat)" > > > > > > Instead of using 100, define a

Re: [PATCH 1/2] tools lib traceevent: Add retrieval of preempt count and latency flags

Hi Steve, On Fri, Nov 18, 2016 at 05:54:00PM -0500, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > Add a way to retrieve the preempt count as well as the latency flags from a > pevent_record. > > int pevent_data_pc(pevent, record); I think

Re: [PATCH 1/2] tools lib traceevent: Add retrieval of preempt count and latency flags

Hi Steve, On Fri, Nov 18, 2016 at 05:54:00PM -0500, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > Add a way to retrieve the preempt count as well as the latency flags from a > pevent_record. > > int pevent_data_pc(pevent, record); I think pevent_data_preempt_count() is

Re: [PATCH 2/2] mmc: sdhci-pci: Use ACPI to get max frequency for Intel byt sdio controller sub-vended by NI

On 22/11/16 01:04, Zach Brown wrote: > On NI 9037 boards the max SDIO frequency is limited by trace lengths > and other layout choices. The max SDIO frequency is stored in an ACPI > table. > > The driver reads the ACPI entry MXFQ during sdio_probe_slot and sets the > f_max field of the host. > >

Re: [PATCH 2/2] mmc: sdhci-pci: Use ACPI to get max frequency for Intel byt sdio controller sub-vended by NI

On 22/11/16 01:04, Zach Brown wrote: > On NI 9037 boards the max SDIO frequency is limited by trace lengths > and other layout choices. The max SDIO frequency is stored in an ACPI > table. > > The driver reads the ACPI entry MXFQ during sdio_probe_slot and sets the > f_max field of the host. > >

Re: [RFC][PATCH 3/3] usb: dwc2: Make sure we disconnect the gadget state

On Mon, Nov 21, 2016 at 7:23 PM, John Youn wrote: > On 11/15/2016 1:47 PM, John Stultz wrote: >> I had seen some odd behavior with HiKey's usb-gadget interface >> that I finally seemed to have chased down. Basically every other >> time I pluged in the OTG port, the gadget

Re: [RFC][PATCH 3/3] usb: dwc2: Make sure we disconnect the gadget state

On Mon, Nov 21, 2016 at 7:23 PM, John Youn wrote: > On 11/15/2016 1:47 PM, John Stultz wrote: >> I had seen some odd behavior with HiKey's usb-gadget interface >> that I finally seemed to have chased down. Basically every other >> time I pluged in the OTG port, the gadget interface would >>

[PATCH] Input: elan_i2c - Add new ic and modify some functions for new IC infomation Signed-off-by: KT Liao <kt.l...@emc.com.tw>

--- drivers/input/mouse/elan_i2c.h | 6 ++- drivers/input/mouse/elan_i2c_core.c | 40 +-- drivers/input/mouse/elan_i2c_i2c.c | 74 drivers/input/mouse/elan_i2c_smbus.c | 9 - 4 files changed, 108 insertions(+), 21 deletions(-)

[PATCH] Input: elan_i2c - Add new ic and modify some functions for new IC infomation Signed-off-by: KT Liao

--- drivers/input/mouse/elan_i2c.h | 6 ++- drivers/input/mouse/elan_i2c_core.c | 40 +-- drivers/input/mouse/elan_i2c_i2c.c | 74 drivers/input/mouse/elan_i2c_smbus.c | 9 - 4 files changed, 108 insertions(+), 21 deletions(-)

Re: [PATCH] zram: Fix unbalanced idr management at hot removal

A correction, On (11/22/16 10:09), Sergey Senozhatsky wrote: [..] > > > Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1010970 > > > Reported-and-tested-by: David Disseldorp > > > Reviewed-by: David Disseldorp > > > Cc: > > >

Re: [PATCH] zram: Fix unbalanced idr management at hot removal

A correction, On (11/22/16 10:09), Sergey Senozhatsky wrote: [..] > > > Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1010970 > > > Reported-and-tested-by: David Disseldorp > > > Reviewed-by: David Disseldorp > > > Cc: > > > Signed-off-by: Takashi Iwai > > > > Acked-by: Minchan

[PATCH] ipv6:ipv6_pinfo dereferenced after NULL check

From: Rohit Thapliyal np checked for NULL and then dereferenced. It should be modified for NULL case. Signed-off-by: Rohit Thapliyal Signed-off-by: Manjeet Pawar --- net/ipv6/ip6_output.c | 9 + 1 file changed,

[PATCH] ipv6:ipv6_pinfo dereferenced after NULL check

From: Rohit Thapliyal np checked for NULL and then dereferenced. It should be modified for NULL case. Signed-off-by: Rohit Thapliyal Signed-off-by: Manjeet Pawar --- net/ipv6/ip6_output.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/net/ipv6/ip6_output.c

Re: [mm PATCH v3 21/23] mm: Add support for releasing multiple instances of a page

On Mon, 21 Nov 2016 08:21:39 -0800 Alexander Duyck wrote: > >> + __free_pages_ok(page, order); > >> + } > >> +} > >> +EXPORT_SYMBOL(__page_frag_drain); > > > > It's an exported-to-modules library function. It should be documented, > > please?

Re: [mm PATCH v3 21/23] mm: Add support for releasing multiple instances of a page

On Mon, 21 Nov 2016 08:21:39 -0800 Alexander Duyck wrote: > >> + __free_pages_ok(page, order); > >> + } > >> +} > >> +EXPORT_SYMBOL(__page_frag_drain); > > > > It's an exported-to-modules library function. It should be documented, > > please? The page-frag API is only

[GIT PULL] SCSI fixes for 4.9-rc6

Two small fixes. One prevents timeouts on mpt3sas when trying to use the secure erase protocol which causes the erase protocol to be aborted. The second is a regression in a prior fix which causes all commands to abort during PCI extended error recovery, which is incorrect because PCI EEH is

[GIT PULL] SCSI fixes for 4.9-rc6

Two small fixes. One prevents timeouts on mpt3sas when trying to use the secure erase protocol which causes the erase protocol to be aborted. The second is a regression in a prior fix which causes all commands to abort during PCI extended error recovery, which is incorrect because PCI EEH is

Re: [PATCH v2 1/5] ARM: memory: da8xx-ddrctl: new driver

Hi Frank, On Tuesday 22 November 2016 07:13 AM, Frank Rowand wrote: > On 11/21/16 08:33, Sekhar Nori wrote: >> On Monday 31 October 2016 08:15 PM, Bartosz Golaszewski wrote: >>> +static int da8xx_ddrctl_probe(struct platform_device *pdev) >>> +{ >>> + const struct da8xx_ddrctl_config_knob

Re: [PATCH v2 1/5] ARM: memory: da8xx-ddrctl: new driver

Hi Frank, On Tuesday 22 November 2016 07:13 AM, Frank Rowand wrote: > On 11/21/16 08:33, Sekhar Nori wrote: >> On Monday 31 October 2016 08:15 PM, Bartosz Golaszewski wrote: >>> +static int da8xx_ddrctl_probe(struct platform_device *pdev) >>> +{ >>> + const struct da8xx_ddrctl_config_knob

Re: [PATCH] Lock down drivers that can have io ports, io mem, irqs and dma changed

On Mon, Nov 21, 2016 at 11:10:52PM +, David Howells wrote: > One Thousand Gnomes wrote: > > > You need to filter or lock down kernel module options because a lot of > > modules let you set the I/O port or similar (eg mmio) which means you can > > hack the entire

Re: [PATCH] Lock down drivers that can have io ports, io mem, irqs and dma changed

On Mon, Nov 21, 2016 at 11:10:52PM +, David Howells wrote: > One Thousand Gnomes wrote: > > > You need to filter or lock down kernel module options because a lot of > > modules let you set the I/O port or similar (eg mmio) which means you can > > hack the entire machine with say the 8250

Re: [PATCH v2 4/4] spi: spi-fsl-dspi: Minor code cleanup and error path fixes

On 16-11-21 15:22:09, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Code cleanup for improving code readability and error path fixes > > and cleanup removing use of devm_kfree. > > Two things in one, not very nice. Especially the dma_free_coherent is > really a bug and the

Re: [PATCH v2 4/4] spi: spi-fsl-dspi: Minor code cleanup and error path fixes

On 16-11-21 15:22:09, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Code cleanup for improving code readability and error path fixes > > and cleanup removing use of devm_kfree. > > Two things in one, not very nice. Especially the dma_free_coherent is > really a bug and the

Re: [PATCH v2 2/4] spi: spi-fsl-dspi: Fix continuous selection format

On 16-11-21 15:15:41, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Current DMA implementation was not handling the continuous selection > > format viz. SPI chip select would be deasserted even between sequential > > serial transfers. Use the cs_change variable and

Re: [PATCH v2 2/4] spi: spi-fsl-dspi: Fix continuous selection format

On 16-11-21 15:15:41, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Current DMA implementation was not handling the continuous selection > > format viz. SPI chip select would be deasserted even between sequential > > serial transfers. Use the cs_change variable and

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

Hi Michael On 11/22/16 at 05:01pm, Michael Ellerman wrote: > Thiago Jung Bauermann writes: > > Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young: > >> On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote: > >> > powerpc's purgatory.ro has 12 relocation

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

Hi Michael On 11/22/16 at 05:01pm, Michael Ellerman wrote: > Thiago Jung Bauermann writes: > > Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young: > >> On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote: > >> > powerpc's purgatory.ro has 12 relocation types when built as > >> > a

Re: [PATCH 00/36] cputime: Convert core use of cputime_t to nsecs

On Mon, 21 Nov 2016 17:20:06 +0100 Frederic Weisbecker wrote: > On Mon, Nov 21, 2016 at 07:59:56AM +0100, Martin Schwidefsky wrote: > > On Fri, 18 Nov 2016 15:47:02 +0100 > > Frederic Weisbecker wrote: > > > > The do_account_vtime function is called once

Re: [PATCH 00/36] cputime: Convert core use of cputime_t to nsecs

On Mon, 21 Nov 2016 17:20:06 +0100 Frederic Weisbecker wrote: > On Mon, Nov 21, 2016 at 07:59:56AM +0100, Martin Schwidefsky wrote: > > On Fri, 18 Nov 2016 15:47:02 +0100 > > Frederic Weisbecker wrote: > > > > The do_account_vtime function is called once per jiffy and once per task > > > >

[GIT PULL] extcon next for v4.10

Dear Greg, This is extcon-next pull request for v4.10. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: Linux 4.9-rc5 (2016-11-13

[GIT PULL] extcon next for v4.10

Dear Greg, This is extcon-next pull request for v4.10. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: Linux 4.9-rc5 (2016-11-13

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

Thiago Jung Bauermann writes: > Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young: >> On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote: >> > powerpc's purgatory.ro has 12 relocation types when built as >> > a relocatable object. To implement support

Re: [PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

Thiago Jung Bauermann writes: > Am Sonntag, 20. November 2016, 10:45:46 BRST schrieb Dave Young: >> On 11/10/16 at 01:27am, Thiago Jung Bauermann wrote: >> > powerpc's purgatory.ro has 12 relocation types when built as >> > a relocatable object. To implement support for them requires >> >

[PATCH 2/2] virtio_ring: fix complaint by sparse

# make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/ drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment (different base types) drivers/virtio/virtio_ring.c:423:19:expected unsigned int [unsigned] [assigned] i drivers/virtio/virtio_ring.c:423:19:got restricted

[PATCH 2/2] virtio_ring: fix complaint by sparse

# make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/ drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment (different base types) drivers/virtio/virtio_ring.c:423:19:expected unsigned int [unsigned] [assigned] i drivers/virtio/virtio_ring.c:423:19:got restricted

Re: [PATCH] zram: Fix unbalanced idr management at hot removal

On Tue, 22 Nov 2016 02:39:13 +0100, Sergey Senozhatsky wrote: > > On (11/22/16 10:33), Minchan Kim wrote: > > On Tue, Nov 22, 2016 at 10:28:12AM +0900, Sergey Senozhatsky wrote: > > > On (11/22/16 10:22), Minchan Kim wrote: > > > [..] > > > > > > Acked-by: Minchan Kim > > > >

[PATCH 1/2] virtio_pci_modern: fix complaint by sparse

drivers/virtio/virtio_pci_modern.c:66:40: warning: incorrect type in argument 2 (different base types) drivers/virtio/virtio_pci_modern.c:66:40:expected unsigned int [noderef] [usertype] *addr drivers/virtio/virtio_pci_modern.c:66:40:got restricted __le32 [noderef] [usertype] *lo

Re: [PATCH] zram: Fix unbalanced idr management at hot removal

On Tue, 22 Nov 2016 02:39:13 +0100, Sergey Senozhatsky wrote: > > On (11/22/16 10:33), Minchan Kim wrote: > > On Tue, Nov 22, 2016 at 10:28:12AM +0900, Sergey Senozhatsky wrote: > > > On (11/22/16 10:22), Minchan Kim wrote: > > > [..] > > > > > > Acked-by: Minchan Kim > > > > > > > > > > Link:

[PATCH 1/2] virtio_pci_modern: fix complaint by sparse

drivers/virtio/virtio_pci_modern.c:66:40: warning: incorrect type in argument 2 (different base types) drivers/virtio/virtio_pci_modern.c:66:40:expected unsigned int [noderef] [usertype] *addr drivers/virtio/virtio_pci_modern.c:66:40:got restricted __le32 [noderef] [usertype] *lo

[PATCH 0/2] virtio: fix complaint by sparse

I found some warnings reported by sparse in the virtio code when I checked virtio-crypto's driver stuff. Let's fix them. Gonglei (2): virtio_pci_modern: fix complaint by sparse virtio_ring: fix complaint by sparse drivers/virtio/virtio_pci_modern.c | 8 drivers/virtio/virtio_ring.c

[PATCH 0/2] virtio: fix complaint by sparse

I found some warnings reported by sparse in the virtio code when I checked virtio-crypto's driver stuff. Let's fix them. Gonglei (2): virtio_pci_modern: fix complaint by sparse virtio_ring: fix complaint by sparse drivers/virtio/virtio_pci_modern.c | 8 drivers/virtio/virtio_ring.c

linux-next: manual merge of the tip tree with the pm tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/idle/Kconfig drivers/idle/i7300_idle.c between commits: f2f31bb3f50b ("idle / i7300: Add CONFIG_PCI dependency") ccd29e2ed6bc ("i7300_idle: avoid theoretical uninitialized data usage") 881ef1847b2d

linux-next: manual merge of the tip tree with the pm tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/idle/Kconfig drivers/idle/i7300_idle.c between commits: f2f31bb3f50b ("idle / i7300: Add CONFIG_PCI dependency") ccd29e2ed6bc ("i7300_idle: avoid theoretical uninitialized data usage") 881ef1847b2d

Re: [HMM v13 01/18] mm/memory/hotplug: convert device parameter bool to set of flags

On 11/21/2016 05:57 PM, Jerome Glisse wrote: > On Mon, Nov 21, 2016 at 12:11:50PM +0530, Anshuman Khandual wrote: >> On 11/18/2016 11:48 PM, Jérôme Glisse wrote: > > [...] > >>> @@ -956,7 +963,7 @@ kernel_physical_mapping_remove(unsigned long start, >>> unsigned long end) >>>

Re: [RFC PATCH net v2 2/3] dt: bindings: add ethernet phy eee-disable-advert option documentation

Le 21/11/2016 à 08:47, Andrew Lunn a écrit : >> What I did not realize when doing this patch for the realtek driver is >> that there is already 6 valid modes defined in the kernel >> >> #define MDIO_EEE_100TX MDIO_AN_EEE_ADV_100TX /* >> 100TX EEE cap */ >> #define MDIO_EEE_1000T

Re: [HMM v13 01/18] mm/memory/hotplug: convert device parameter bool to set of flags

On 11/21/2016 05:57 PM, Jerome Glisse wrote: > On Mon, Nov 21, 2016 at 12:11:50PM +0530, Anshuman Khandual wrote: >> On 11/18/2016 11:48 PM, Jérôme Glisse wrote: > > [...] > >>> @@ -956,7 +963,7 @@ kernel_physical_mapping_remove(unsigned long start, >>> unsigned long end) >>>

Re: [RFC PATCH net v2 2/3] dt: bindings: add ethernet phy eee-disable-advert option documentation

Le 21/11/2016 à 08:47, Andrew Lunn a écrit : >> What I did not realize when doing this patch for the realtek driver is >> that there is already 6 valid modes defined in the kernel >> >> #define MDIO_EEE_100TX MDIO_AN_EEE_ADV_100TX /* >> 100TX EEE cap */ >> #define MDIO_EEE_1000T

[PATCH 1/1] ACPI: Document _OSI and _REV for Linux BIOS writers

From: Len Brown Based on a recent session at the Linux Plumber's Conference, we need to be more clear about how a BIOS should use _OSI to properly support Linux. Signed-off-by: Len Brown --- Documentation/acpi/osi.txt | 187

[PATCH 1/1] ACPI: Document _OSI and _REV for Linux BIOS writers

From: Len Brown Based on a recent session at the Linux Plumber's Conference, we need to be more clear about how a BIOS should use _OSI to properly support Linux. Signed-off-by: Len Brown --- Documentation/acpi/osi.txt | 187 + 1 file changed, 187

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

Hi Paul, Today's linux-next merge of the audit tree got a conflict in: include/uapi/linux/audit.h between commit: 7ff89ac608d9 ("audit: add exclude filter extension to feature bitmap") from Linus' tree and commit: 0489410368df ("audit: add support for session ID user filter") from the

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

Hi Paul, Today's linux-next merge of the audit tree got a conflict in: include/uapi/linux/audit.h between commit: 7ff89ac608d9 ("audit: add exclude filter extension to feature bitmap") from Linus' tree and commit: 0489410368df ("audit: add support for session ID user filter") from the

Re: [GIT PULL 4/4] bcm2835-defconfig-64-next-2016-11-18

Le 18/11/2016 à 10:58, Eric Anholt a écrit : > Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) > > are available in the git repository at: > > https://github.com/anholt/linux tags/bcm2835-defconfig-64-next-2016-11-18 > > for you to fetch changes up to ac178e4280e65f4d0d14b13a7bfec3a43ff90e66: >

Re: [GIT PULL 4/4] bcm2835-defconfig-64-next-2016-11-18

Le 18/11/2016 à 10:58, Eric Anholt a écrit : > Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) > > are available in the git repository at: > > https://github.com/anholt/linux tags/bcm2835-defconfig-64-next-2016-11-18 > > for you to fetch changes up to ac178e4280e65f4d0d14b13a7bfec3a43ff90e66: >

  1   2   3   4   5   6   7   8   9   10   >