From: Guenter Roeck
If the driver is in suspended mode, the dp block may be disabled, and
chip registers may not be accessible. Yet, the worker may be triggered
in this situation by an extcon event. If that happens, the following crash
will be seen.
cdn-dp fec0.dp: [drm:cdn_dp_pd_event_work]
From: Guenter Roeck
If no monitor is connected, suspend/resume cycles result in firmware
load errors because the driver attempts to load the firmware while
the system is in suspend state. This results in a kernel warning and
traceback.
Loading the firmware during boot fixes the problem. Note tha
From: Jeffy Chen
We're trying to lock mutex when cdn-dp shutdown, so we need to make
sure the mutex is inited in cdn-dp's probe.
Signed-off-by: Jeffy Chen
Reviewed-by: Guenter Roeck
Reviewed-by: Chris Zhong
Signed-off-by: Chris Zhong
---
Changes in v17: None
drivers/gpu/drm/rockchip/cdn-d
Sometimes the Dock is disconnected, but cdn_dp_encoder_disable is not
triggered by DRM. For example, unplug the Dock in console mode, and
re-plug it again, the cdn_dp_event_work will try to get the sink count
of Dock, since the DP is still active. But the Dock has been powered
down, it need re-powe
The cdn_dp_pd_event_work is using drm_helper_hpd_irq_event to update the
connector status, this function is used to update all connectors of
drm_device. Therefore, the detect of other connector will be call, when
cdn_dp_pd_event_work is triggered, every time. It is not necessary, and
it may cause s
With atomic modesetting the hardware will be powered off when the
mode_set function is called. We should configure the hardware in the
enable function.
Signed-off-by: Chris Zhong
---
Changes in v17: None
drivers/gpu/drm/rockchip/cdn-dp-core.c | 49 +-
1 file ch
This series adds support for the CDN DP controller to the rockchip drm
driver. This version fixes some coding style error in v16, it post by
Sean Paul, you can find it here:
https://patchwork.kernel.org/patch/9442135/
And I sorted out a few patches to fix the following problems:
- suspend/
Add support for cdn DP controller which is embedded in the rk3399
SoCs. The DP is compliant with DisplayPort Specification,
Version 1.3, This IP is compatible with the rockchip type-c PHY IP.
There is a uCPU in DP controller, it need a firmware to work,
please put the firmware file to /lib/firmware
On Sat, Feb 4, 2017 at 9:19 PM, James Bottomley
wrote:
> This allows any subtree to be uid/gid shifted and bound elsewhere. It
> does this by operating simlarly to overlayfs. Its primary use is for
> shifting the underlying uids of filesystems used to support
> unpriviliged (uid shifted) contain
On 2017年02月05日 11:42, Chris Zhong wrote:
On 02/02/2017 02:12 AM, Sean Paul wrote:
On Tue, Jan 24, 2017 at 10:27:27AM +0800, Chris Zhong wrote:
Hi Sean
On 01/24/2017 01:48 AM, Sean Paul wrote:
On Fri, Jan 20, 2017 at 06:10:49PM +0800, Chris Zhong wrote:
The MIPI DSI do not need check the va
On Fri, Feb 03, 2017 at 11:55:24AM +0100, Richard Leitner wrote:
> +/**
> + * ascii2utf16le() - Helper routine for producing UTF-16LE string descriptors
> + * @s: Null-terminated ASCII (actually ISO-8859-1) string
> + * @buf: Buffer for UTF-16LE string
> + * @len: Length (in bytes; may be odd) of U
Signed-off-by: Mark Yao
---
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 47 +++--
1 file changed, 44 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
index a6d4a02..64408bc 100644
--- a
drm crtc already has mode_fixup callback to can do mode check, but
We actually want to valid display mode on connector getmode time,
mode_fixup can't do it.
So add a private mode_valid callback to rockchip crtc, connectors can
check mode with this mode_valid callback.
Signed-off-by: Mark Yao
---
On Sat, Feb 04, 2017 at 08:22:59PM -0800, Yinghai Lu wrote:
> On Sat, Feb 4, 2017 at 3:34 PM, Lukas Wunner wrote:
> > On Sat, Feb 04, 2017 at 01:44:34PM -0800, Yinghai Lu wrote:
> >> On Sat, Feb 4, 2017 at 10:56 AM, Lukas Wunner wrote:
> >> > On Sat, Feb 04, 2017 at 09:12:54AM +0100, Lukas Wunner
On Sun, Jan 29, 2017 at 10:33:29AM +0800, Icenowy Zheng wrote:
> As 64-bit Allwinner H5 SoC has the same DMA engine with H3, the DMA
> driver should be allowed to be built for ARM64, in order to make it work on
> H5.
Applied, thanks
--
~Vinod
On Sun, 5 Feb 2017 01:29:43 +0100
Greg Kroah-Hartman wrote:
> On Sat, Feb 04, 2017 at 08:39:21PM +0100, AbdAllah-MEZITI wrote:
> > In C a static pointer will be initialized to NULL (e.g: draft C99
> > standard $6.7.8): "If an object that has static storage duration is
> > not initialized explicit
This was causing a build failure for openrisc when using musl and
gcc 5.4.0 since the file is not available in the toolchain.
It doesnt seem this is needed and removing it does not cause any build
warnings for me.
Signed-off-by: Stafford Horne
---
net/ceph/snapshot.c | 2 --
1 file changed, 2 d
Building on openrisc musl toolchain this causes the allyesconfig build
to fail.
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c:42:20:
fatal error: stddef.h: No such file or directory
Removing this causes no issues with the build.
Signed-off-by: Stafford Horne
---
drivers/st
Hi All,
These were causing openrisc build to fail when building with allyesconfig
using a musl toolchain. Removing them doesnt seem to cause any issues.
The line removed was:
#include
Perhaps what was wanted was 'linux/stddef.h' but there did seem to be any
special uses so I just removed i
Hi,
This patches replaces bio_clone() with bio_fast_clone() in
bio_clone_mddev() because:
1) bio_clone_mddev() is used in raid normal I/O and isn't in
resync I/O path, and all the direct access to bvec table in
raid happens on resync I/O only except for write behind of raid1.
Write behind is trea
md still need bio clone(not the fast version) for behind write,
and it is more efficient to use bio_clone_bioset_partial().
The idea is simple and just copy the bvecs range specified from
parameters.
Signed-off-by: Ming Lei
---
block/bio.c | 61 +-
In raid1/raid10, most users of bio_clone_mddev() need bio_trim() too,
that means only part of the bio is required to be cloned, and not
necessary to clone the whole bio each time, and it is just enough
to clone the specified bvecs range.
So this patch introduces bio_clone_slow_mddev_partial() to i
Firstly bio_clone_mddev() is used in raid normal I/O and isn't
in resync I/O path.
Secondly all the direct access to bvec table in raid happens on
resync I/O except for write behind of raid1, in which we still
use bio_clone() for allocating new bvec table.
So this patch replaces bio_clone() with
Write behind need to replace pages in bio's bvecs, and we have
to clone a fresh bio with new bvec table, so use the introduced
bio_clone_slow_mddev_partial() for it.
For other bio_clone_mddev() cases, we will use fast clone since
they don't need to touch bvec table.
Signed-off-by: Ming Lei
---
On Thu, Feb 02, 2017 at 10:17:15AM +0530, Anup Patel wrote:
> +config BCM_SBA_RAID
> +tristate "Broadcom SBA RAID engine support"
> +depends on (ARM64 && MAILBOX && RAID6_PQ) || COMPILE_TEST
> +select DMA_ENGINE
> +select DMA_ENGINE_RAID
> + select ASYNC_TX_ENABL
On Sat, Feb 4, 2017 at 8:22 PM, Yinghai Lu wrote:
> On Sat, Feb 4, 2017 at 3:34 PM, Lukas Wunner wrote:
>> On Sat, Feb 04, 2017 at 01:44:34PM -0800, Yinghai Lu wrote:
>>> On Sat, Feb 4, 2017 at 10:56 AM, Lukas Wunner wrote:
>>> > On Sat, Feb 04, 2017 at 09:12:54AM +0100, Lukas Wunner wrote:
>>>
Hi Guenter,
On Sat, Feb 04, 2017 at 08:29:27PM -0800, Guenter Roeck wrote:
> Yes. One of the problems is that the patch doesn't apply to my tree
> (which is based on v4.10-rc3), and it doesn't have a common anchestor,
> meaning it is most likely not based on mainline. I would prefer to avoid
> con
On 02/04/2017 07:45 PM, Shawn Guo wrote:
Hi Baoyou,
On Sun, Feb 05, 2017 at 10:36:38AM +0800, Baoyou Xie wrote:
On 5 February 2017 at 08:05, Guenter Roeck wrote:
On 02/03/2017 05:34 PM, Baoyou Xie wrote:
Add the zx2967 watchdog controller driver as maintained by ARM ZTE
architecture mainta
On Sat, Feb 4, 2017 at 3:34 PM, Lukas Wunner wrote:
> On Sat, Feb 04, 2017 at 01:44:34PM -0800, Yinghai Lu wrote:
>> On Sat, Feb 4, 2017 at 10:56 AM, Lukas Wunner wrote:
>> > On Sat, Feb 04, 2017 at 09:12:54AM +0100, Lukas Wunner wrote:
>> > Section 6.7.3.4 of the PCIe Base spec seems to support
On Wed, 2017-01-25 at 11:38 +0800, Guochun Mao wrote:
> Add Mediatek nor flash node.
>
> Signed-off-by: Guochun Mao
> ---
> arch/arm/boot/dts/mt2701-evb.dts | 25 +
> arch/arm/boot/dts/mt2701.dtsi| 12
> 2 files changed, 37 insertions(+)
>
> diff --g
Reference the power domain incase dw-mipi power down when
in use.
Signed-off-by: Chris Zhong
Reviewed-by: Sean Paul
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 16
1 file changed, 16 insertions(+)
diff --git a/driv
Signed-off-by: Chris Zhong
Acked-by: Rob Herring
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
.../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/rockchip/dw_
The MIPI DSI do not need check the validity of resolution, the max
resolution should depend VOP. Hence, remove rk3288_mipi_dsi_mode_valid
here.
Signed-off-by: Chris Zhong
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 39 ---
The vopb/vopl switch register of RK3399 mipi is different from RK3288,
the default setting for mipi dsi mode is different too, so add a
of_device_id structure to distinguish them, and make sure set the
correct mode before mipi phy init.
Signed-off-by: Chris Zhong
Signed-off-by: Mark Yao
---
Ch
Hi all
This patch serial is for RK3399 MIPI DSI. The MIPI DSI controller of
RK3399 is almost the same as RK3288, except a little bit of difference
in phy clock controlling and port id selection register. These patches
add RK3399 support and the power domain support.
And these patches base on John
The dw-mipi-dsi of rk3399 is almost the same as rk3288, the rk3399 has
additional phy config clock.
Signed-off-by: Chris Zhong
Acked-by: Rob Herring
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
.../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 4 +++-
correct the coding style, according the checkpatch scripts
Signed-off-by: Chris Zhong
Reviewed-by: Sean Paul
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 33 -
1 file changed, 16 insertions(+), 17 dele
Hi Baoyou,
On Sun, Feb 05, 2017 at 10:36:38AM +0800, Baoyou Xie wrote:
> On 5 February 2017 at 08:05, Guenter Roeck wrote:
>
> > On 02/03/2017 05:34 PM, Baoyou Xie wrote:
> >
> >> Add the zx2967 watchdog controller driver as maintained by ARM ZTE
> >> architecture maintainers, as they're parts o
On 02/02/2017 02:12 AM, Sean Paul wrote:
On Tue, Jan 24, 2017 at 10:27:27AM +0800, Chris Zhong wrote:
Hi Sean
On 01/24/2017 01:48 AM, Sean Paul wrote:
On Fri, Jan 20, 2017 at 06:10:49PM +0800, Chris Zhong wrote:
The MIPI DSI do not need check the validity of resolution, the max
resolution s
The original posting on Jan 19th have not received any responses, so I resend
them.
The Current default dwc2 just handle one clock named otg, however, it may have
two or more clock need to manage for some new SoCs(such as RK3328), so this
adds change clk to clk's array of dwc2_hsotg to handle mor
Originally, dwc2 just handle one clock named otg, however, it may have
two or more clock need to manage for some new SoCs, so this adds
change clk to clk's array of dwc2_hsotg to handle more clocks operation.
Signed-off-by: Frank Wang
---
drivers/usb/dwc2/core.h | 5 -
drivers/usb/dwc2/
On Sat, Feb 04, 2017 at 11:11:27PM +0100, Miklos Szeredi wrote:
> Well, it's not historical; at least not yet. The deadlock is there
> alright: mmap fuse file to addr; read byte from mapped page -> page
> locked; this triggeres read request served in same process but
> separate thread; write addr
Hi Emese,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: a572a1b999489efb591287632279c6c9eca3e4ed
commit: 543c37cb165049c3be24a0d4733e67caa2b33eef Add sancov plugin
date: 8 months ago
config: x86_64-randconfig-in0
On 02/04/2017 05:17 PM, kbuild test robot wrote:
> Hi Cameron,
>
> [auto build test ERROR on input/next]
> [also build test ERROR on v4.10-rc6 next-20170203]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/
Hi Mylène,
[auto build test ERROR on asoc/for-next]
[also build test ERROR on v4.10-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Myl-ne-Josserand/Add-sun8i-A33-audio-driver/20170202-17302
On 02/04/2017 12:05 PM, Luis R. Rodriguez wrote:
I could not boot next-20170203 on my x86_64 qemu instance. It stalls at:
[0.015549] CPU: Physical Processor ID: 0
[0.015842] mce: CPU supports 10 MCE banks
[0.016032] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[0.016393] Last lev
Hi Cameron,
[auto build test ERROR on input/next]
[also build test ERROR on v4.10-rc6 next-20170203]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Cameron-Gutman/Correctly-support-some-quirky-X
On 02/04/2017 01:32 PM, Dmitry Osipenko wrote:
On 04.02.2017 21:41, Larry Finger wrote:
On 02/04/2017 10:58 AM, Dmitry Osipenko wrote:
Seems the problem is caused by rtl92c_dm_*() casting .priv to "struct
rtl_pci_priv", while it is "struct rtl_usb_priv".
Those routines are shared by rtl8192ce
On 01/30/2017 09:18 AM, Alexandre Belloni wrote:
.config is used to cache a part of WDT_MR at probe time and is not used
afterwards. Instead of doing that, actually cache MR and avoid reading it
every time it is modified.
Signed-off-by: Alexandre Belloni
Reviewed-by: Guenter Roeck
[ hoping
From: Ross Lagerwall
Date: Wed, 1 Feb 2017 15:50:22 +
> * Delay timer creation so that if initializing a queue fails, the timer
> has not been setup yet.
setup_timer() doesn't do anything that must be "undone" if an error
occurs and we have to cleanup.
It just assigns some values to some ti
On Saturday, February 4, 2017 2:59:05 AM EST, Greg KH wrote:
On Fri, Feb 03, 2017 at 11:07:08PM -0500, Ed Tomlinson wrote:
Hi,
Any reports of 4.9.7 breaking X?
I run arch and keep it up to date. With todays updates and
4.9.7 built here
X will not start kde correctly. Reverting to 4.9.6 fixe
The state of pad LEDs can be inconsistent when the system is
woken up after sleep. Rather than leaving the controllers blinking,
let's resend the last LED command to Xbox 360 pads on resume.
Since Xbox One pads stop flashing only when reinitialized, we'll
send them the initialization packet so the
Some PowerA pads require a rumble packet to start sending
input reports.
Signed-off-by: Cameron Gutman
---
drivers/input/joystick/xpad.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
index 3f19f32b..13f298d 100644
--- a/d
Without sending this packet, the Titanfall 2 pad (0x0e6f:0x0165)
continuously attempts to handshake with the PC and never sends
any input reports.
The Hori gamepad (0x0f0d:0x0067) analog sticks don't work if
this isn't sent, though other buttons do work without it.
Signed-off-by: Cameron Gutman
The Xbox One S requires an ack to its mode button report
otherwise it continuously retransmits the report. This
makes the mode button appear to be stuck down after it
is pressed for the first time.
Signed-off-by: Cameron Gutman
---
drivers/input/joystick/xpad.c | 33 +
There are a bunch of quirky Xbox One pads that depend on weird
initialization things that the Microsoft pads don't. In this series,
I've incorporated quirk handling from Valve's Steam Link driver[0]
and the 360Controller project[1] for macOS.
Patches 1 - 3 are split that way in case 2 or 3 introdu
This is preparatory work for supporting some 3rd party
pads that need more initialization packets than just
one. No initialization behavior change expected.
Signed-off-by: Cameron Gutman
---
drivers/input/joystick/xpad.c | 40 +++-
1 file changed, 27 insertion
On Sat, Feb 04, 2017 at 08:39:21PM +0100, AbdAllah-MEZITI wrote:
> In C a static pointer will be initialized to NULL (e.g: draft C99 standard
> $6.7.8):
> "If an object that has static storage duration is not initialized
> explicitly, then:
> __ if it has pointer type, it is initialized to a null
On Fri, Feb 03, 2017 at 02:47:29PM -0500, Sebastien Bourdelin wrote:
> This watchdog is instantiated in a FPGA and can only be access using a
> GPIOs bit-banged bus, called the NBUS by Technologic Systems.
> The watchdog is made of only one register, called the feed register.
> Writing to this regi
On 02/03/2017 05:34 PM, Baoyou Xie wrote:
This patch adds watchdog controller driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
Reviewed-by: Guenter Roeck
---
drivers/watchdog/Kconfig | 10 ++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/zx2967_wdt.c | 291 +++
On 02/03/2017 05:34 PM, Baoyou Xie wrote:
Add the zx2967 watchdog controller driver as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
Reviewed-by: Guenter Roeck
I assume you'll submit this patch through the arm tree ?
Guenter
--
On 02/03/2017 05:34 PM, Baoyou Xie wrote:
This patch adds dt-binding documentation for zx2967 family
watchdog controller.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Guenter Roeck
---
.../bindings/watchdog/zte,zx2967-wdt.txt | 32 ++
1 file
On 01/30/2017 09:18 AM, Alexandre Belloni wrote:
When resuming for the deepest state on sama5d2, it is necessary to restore
MR as the registers are lost.
Signed-off-by: Alexandre Belloni
---
drivers/watchdog/sama5d4_wdt.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/d
On 02/04/2017 03:12 PM, Alexey Khoroshilov wrote:
There is no remove of w83791d_group_fanpwm45 sysfs group.
Fix the problem by switching to hwmon_device_register_with_groups().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/hwmon/w
On 01/31/2017 07:43 AM, eaja...@linux.vnet.ibm.com wrote:
From: "Edward A. James"
Add core support for polling the OCC for it's sensor data and parsing that
data into sensor-specific information.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ|
Hi all,
On Sun, 5 Feb 2017 10:17:29 +1100 Stephen Rothwell
wrote:
>
> On Sat, 4 Feb 2017 12:05:42 -0800 "Luis R. Rodriguez"
> wrote:
> >
> > though so it seems something with my configuration and boot. I
> > bisected next-20170203 between its latest commit and v4.10-rc6 and
> > ended up with t
Commit-ID: 4d8bb00604b182b62e7786bae0e58e0befeeff85
Gitweb: http://git.kernel.org/tip/4d8bb00604b182b62e7786bae0e58e0befeeff85
Author: Piotr Luc
AuthorDate: Fri, 20 Jan 2017 14:22:37 +0100
Committer: Thomas Gleixner
CommitDate: Sun, 5 Feb 2017 00:19:52 +0100
x86/cpufeature: Enable RING
Hi Luis,
On Sat, 4 Feb 2017 12:05:42 -0800 "Luis R. Rodriguez" wrote:
>
> though so it seems something with my configuration and boot. I
> bisected next-20170203 between its latest commit and v4.10-rc6 and
> ended up with this bad commit:
>
> 104a519fe1732b4e503ebc7b4ac71b6f0b8a0b62
>
> $ git s
When vmemmap_populate() allocates space for the memmap it does so in 2MB
sized chunks. The libnvdimm-pfn driver incorrectly accounts for this
when the alignment of the device is set to 4K. When this happens we
trigger memory allocation failures in altmap_alloc_block_buf() and
trigger warnings of th
There is no remove of w83791d_group_fanpwm45 sysfs group.
Fix the problem by switching to hwmon_device_register_with_groups().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/hwmon/w83791d.c | 40 +++---
On Fri, 3 Feb 2017, Steven Rostedt (VMware) wrote:
> From: "Steven Rostedt (VMware)"
>
> Running my likely/unlikely profiler, I discovered that the test in
> shmem_write_begin() that tests for info->seals as unlikely, is
> always incorrect. This is because shmem_get_inode() sets info->seals to
>
On 2/3/2017 2:11 PM, Eric Dumazet wrote:
Transmit completion might happen on another cpu, regardless of ldom.
Therefore you need smp_rmb() here ( like mellanox/mlx4/en_tx.c) , or
even smp_mb() as bnx2x does.
dma_rmb() is never used in this context.
In that case, it looks like there are a co
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/intel/i40evf/i40evf_ethtool.c | 31 +
Diving the divider by the multiplier before applying to the input.
When this would "divide by zero", divide the multiplier by the divider
first then multiply the input by this value.
Currently user2creds outputs zero when input value is bigger than the
number of slices and lower than scale.
This
Hi Pavel,
On Sat, Feb 04, 2017 at 10:56:10PM +0100, Pavel Machek wrote:
> Hi!
>
> > > > > +Required properties
> > > > > +===
> > > > > +
> > > > > +compatible : must contain "video-bus-switch"
> > > >
> > > > How generic is this? Should we have e.g. nokia,video-bus-switch? And
On Sat, Feb 4, 2017 at 8:26 PM, Al Viro wrote:
> On Sat, Feb 04, 2017 at 03:08:42AM +, Al Viro wrote:
> What am I missing here? Looks like those checks in fuse_copy_page() are
> dead code... They had been there since the initial merge, but AFAICS
> they were just as useless in 2.6.14. Rudi
On Sat, Feb 4, 2017 at 4:08 AM, Al Viro wrote:
> On Thu, Feb 02, 2017 at 09:51:25AM +, Al Viro wrote:
>
>> * fuse_copy_fill(). I'm not at all sure that iov_iter_get_pages()
>> is a good idea there - fuse_copy_do() could bloody well just use
>> copy_{to,from}_iter().
>
> Miklos, could yo
Hi!
> > > > +Required properties
> > > > +===
> > > > +
> > > > +compatible : must contain "video-bus-switch"
> > >
> > > How generic is this? Should we have e.g. nokia,video-bus-switch? And if
> > > so,
> > > change the file name accordingly.
> >
> > Generic for "single GPI
On 02/04/2017 10:44 PM, Arnd Bergmann wrote:
> On Sat, Feb 4, 2017 at 10:11 PM, Marek Vasut wrote:
>> On 02/03/2017 06:01 PM, Arnd Bergmann wrote:
>>> diff --git a/drivers/iio/adc/rcar-gyroadc.c b/drivers/iio/adc/rcar-gyroadc.c
>>> index 0c44f72c32a8..331ff9a673be 100644
>>> --- a/drivers/iio/adc/
Hi Thomas,
It looks like there is a typo with the line with 'break' - it should be
semicolon there.
Could you fix it, please?
Thx,
Piotr
>
> Signed-off-by: Piotr Luc
> Cc: piotr@intel.com
> Cc: dave.han...@linux.intel.com
> Link: http://lkml.kernel.org/r/1484918557-15481-6-git-send-email-
On Sat, Feb 4, 2017 at 10:11 PM, Marek Vasut wrote:
> On 02/03/2017 06:01 PM, Arnd Bergmann wrote:
>> diff --git a/drivers/iio/adc/rcar-gyroadc.c b/drivers/iio/adc/rcar-gyroadc.c
>> index 0c44f72c32a8..331ff9a673be 100644
>> --- a/drivers/iio/adc/rcar-gyroadc.c
>> +++ b/drivers/iio/adc/rcar-gyroad
Le 02/04/17 à 09:23, Andrew Lunn a écrit :
> On Sat, Feb 04, 2017 at 04:47:47PM +0100, Lukasz Majewski wrote:
>> Add the documentation to avoid PHY lane swapping. This is a boolean
>> entry to notify the phy device drivers that the TX/RX lanes NO need
>
> that the TX/RX lanes should not be swapped
On 02/03/2017 10:49 AM, Arnd Bergmann wrote:
> kernelci.org reports a warning for this driver, as it copies a local
> variable into a 'const char *' string:
>
> drivers/mtd/maps/pmcmsp-flash.c:149:30: warning: passing argument 1 of
> 'strncpy' discards 'const' qualifier from pointer target ty
On 02/03/2017 06:01 PM, Arnd Bergmann wrote:
> If we get an unknown 'childmode' value, a number of variables are not
> initialized properly:
>
> drivers/iio/adc/rcar-gyroadc.c: In function 'rcar_gyroadc_probe':
> drivers/iio/adc/rcar-gyroadc.c:390:5: error: 'num_channels' may be used
> uninitiali
On Sat, Feb 4, 2017 at 1:04 PM, James Bottomley
wrote:
> On Sat, 2017-02-04 at 12:37 -0800, Dan Williams wrote:
>> On Sat, Feb 4, 2017 at 12:36 PM, Dan Williams <
>> dan.j.willi...@intel.com> wrote:
>> > On Fri, Feb 3, 2017 at 11:09 PM, kernel test robot
>> > wrote:
>> > >
>> > > FYI, we noticed
On Sat, 2017-02-04 at 12:37 -0800, Dan Williams wrote:
> On Sat, Feb 4, 2017 at 12:36 PM, Dan Williams <
> dan.j.willi...@intel.com> wrote:
> > On Fri, Feb 3, 2017 at 11:09 PM, kernel test robot
> > wrote:
> > >
> > > FYI, we noticed the following commit:
> > >
> > > commit: 0dba1314d4f81115dce7
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/intel/i40e/i40e_ethtool.c | 224 ++---
In preparation for using this function in net/dsa/dsa2.c, rename the function
to make its scope DSA specific, and export it.
Signed-off-by: Florian Fainelli
---
include/net/dsa.h | 1 +
net/dsa/dsa.c | 5 +++--
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/net/dsa.h
Utilize the ability to pass board specific MDIO bus information towards a
particular MDIO device thus allowing us to provide the per-port switch layout
to the Marvell 88E6XXX switch driver.
Since we would end-up with conflicting registration paths, do not register the
"dsa" platform device anymore
Allow board support code to collect pre-declarations for MDIO devices by
registering them with mdiobus_register_board_info(). SPI and I2C buses
have a similar feature, we were missing this for MDIO devices, but this
is particularly useful for e.g: MDIO-connected switches which need to
provide their
Hi all,
This is not exactly new, and was sent before, although back then, I did not
have an user of the pre-declared MDIO board information, but now we do. Note
that I have additional changes queued up to have b53 register platform data for
MIPS bcm47xx and bcm63xx.
Yes I know that we should have
Allow drivers to use the new DSA API with platform data. Most of the
code in net/dsa/dsa2.c does not rely so much on device_nodes and can get
the same information from platform_data instead.
We purposely do not support distributed configurations with platform
data, so drivers should be providing a
Hi all,
This is not exactly new, and was sent before, although back then, I did not
have an user of the pre-declared MDIO board information, but now we do. Note
that I have additional changes queued up to have b53 register platform data for
MIPS bcm47xx and bcm63xx.
Yes I know that we should have
On Sat, Feb 4, 2017 at 12:36 PM, Dan Williams wrote:
> On Fri, Feb 3, 2017 at 11:09 PM, kernel test robot
> wrote:
>>
>> FYI, we noticed the following commit:
>>
>> commit: 0dba1314d4f81115dce711292ec7981d17231064 ("scsi, block: fix
>> duplicate bdi name registration crashes")
>> https://git.ker
On Fri, Feb 3, 2017 at 11:09 PM, kernel test robot
wrote:
>
> FYI, we noticed the following commit:
>
> commit: 0dba1314d4f81115dce711292ec7981d17231064 ("scsi, block: fix duplicate
> bdi name registration crashes")
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
> for-4.
On Thu, Feb 2, 2017 at 5:28 AM, Andrew Jeffery wrote:
> 1736f75d35e47409ad776273133d0f558a4c8253 is a (v2) patch which had
> unresolved review comments[1]. Address the comments by removing the use
> of macros from the consumer header (this patch represents the diff
> between v2 and v3[2]).
>
> [1
Hi Rob,
On Sat, Feb 4, 2017 at 1:36 AM, Rob Herring wrote:
> diff --git a/drivers/gpu/drm/mxsfb/mxsfb_out.c
> b/drivers/gpu/drm/mxsfb/mxsfb_out.c
> index fa8d17399407..f7d729aa09bd 100644
> --- a/drivers/gpu/drm/mxsfb/mxsfb_out.c
> +++ b/drivers/gpu/drm/mxsfb/mxsfb_out.c
> @@ -19,6 +19,7 @@
>
On Fri, 2017-02-03 at 18:36 -0600, Trevor Cordes wrote:
> On 2017-02-01 Michal Hocko wrote:
> > On Wed 01-02-17 03:29:28, Trevor Cordes wrote:
> > > On 2017-01-30 Michal Hocko wrote:
> >
> > [...]
> > > > Testing with Valinall rc6 released just yesterday would be a
> > > > good
> > > > fit. Ther
I could not boot next-20170203 on my x86_64 qemu instance. It stalls at:
[0.015549] CPU: Physical Processor ID: 0
[0.015842] mce: CPU supports 10 MCE banks
[0.016032] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[0.016393] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[0.
On Sat, Feb 4, 2017 at 12:39 PM, Jonathan Cameron wrote:
> On 03/02/17 19:40, Linus Walleij wrote:
>>> + if (ret) {
>>> + dev_err(&pdev->dev, "request IRQ %d failed\n", irq);
>>> + return ret;
>>> + }
>>
>> Here you need some
1 - 100 of 230 matches
Mail list logo
