On Thu, Feb 02, 2017 at 02:16:39PM +0200, Mika Westerberg wrote:
> On Thu, Feb 02, 2017 at 01:35:08PM +0200, Mika Westerberg wrote:
> > On Thu, Feb 02, 2017 at 12:12:22PM +0100, Johannes Stezenbach wrote:
> > > On Thu, Feb 02, 2017 at 12:31:22PM +0200, Mika Westerberg wrote:
> > > > On Thu, Feb 02,
Hello Andrew,
On Tue, Jan 31, 2017 at 04:41:32PM -0800, Andrew Morton wrote:
> On Fri, 27 Jan 2017 20:44:31 +0200 Mike Rapoport
> wrote:
>
> > Allow userfaultfd monitor track termination of the processes that have
> > memory backed by the uffd.
> >
> > --- a/fs/userfaultfd.c
> > +++ b/fs/userf
This patch adds a driver for configuration of the Microchip USB251xB/xBi
USB 2.0 hub controller series with USB 2.0 upstream connectivity, SMBus
configuration interface and two to four USB 2.0 downstream ports.
Furthermore add myself as a maintainer for this driver.
The datasheet can be found at
Hi,
VDK config includes GRFC, not sure if it's working/used though.
The nSIM STAR is about that GRFC frequency is fixed in nSIM, but configurable
for HW/customers.
But if the frequency is configured correctly (same as cpu frequency), don't
think there's an issue.
Ruud.
-Original Message
On Thu, Feb 2, 2017 at 2:56 PM, Dmitry Vyukov wrote:
> On Thu, Feb 2, 2017 at 2:40 PM, Eric Dumazet wrote:
>> On Thu, 2017-02-02 at 13:59 +0100, Dmitry Vyukov wrote:
>>
>>>
>>> Right, I can confirm that this is not happening on net-next tip
>>> (62e13097c46c69dbd7544ab2cd585ccf48f360a4).
>>> I re
On Wed, Jan 25, 2017 at 11:44:48AM -0500, Rob Rice wrote:
>
> +static int ahash_export(struct ahash_request *req, void *out)
> +{
> + const struct iproc_reqctx_s *rctx = ahash_request_ctx(req);
> +
> + memcpy(out, rctx, offsetof(struct iproc_reqctx_s, msg_buf));
> + return 0;
> +}
The
Unless they are connected through unifying, they don't support it,
so remove one error in the logs.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/h
When a device reconnects, there is a high chance its power supply has
been changed (for a battery replacement for instance). Just forward
the battery state here.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 14 +++---
1 file changed, 11
Unifying devices are different from others because they can probed
while not connected. So we need to talk to the receiver to get some
extra information like the device name and the serial.
Instead of having conditionals while attempting to read the device name
from HID++ 2.0, have a special init
Looks like all users don't care about a disconnect.
Simplify the various variant_connect() and put the connect state check
at the beginning.
For delayed input devices, make sure we go through all other connect
values (protocol, battery) before bailing out.
Signed-off-by: Benjamin Tissoires
---
hidpp->name can't be null.
Only HID++ 2.0 and above device supports the query.
Signed-off-by: Benjamin Tissoires
---
new in v2
---
drivers/hid/hid-logitech-hidpp.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/hid/hid-logitech-hi
Simple check to add, huge improvement :)
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index 4aaf237..1cda29e 100644
--- a/dr
This way, upower can add a simple udev rule to decide whether or not
it should use the internal unifying support or just the generic kernel
one.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 20
1 file changed, 20 insertions(
From: Bastien Nocera
Without a scope defined, UPower assumes that the battery provides
power to the computer it's connected to, like a laptop battery or a UPS.
Tested-by: Peter Hutterer
Signed-off-by: Bastien Nocera
Signed-off-by: Benjamin Tissoires
---
changes in v2:
* fixed typo in commit
The Solar Keyboard uses a different feature to report the battery level.
Signed-off-by: Benjamin Tissoires
---
changes in v2:
* update state according to lux information
* do not update Lux if the event does not contain lux information
---
drivers/hid/hid-logitech-hidpp.c | 97
Register 0xB5 should be handled specially no matter what function is
used. This allows to retrieve the serial and the Quad ID from
hid-logitech-hidpp directly.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-dj.c | 17 ++---
1 file changed, 10 in
The creation of the power_supply should not be in a HID++ 2.0 specific
function.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 94 ++--
1 file changed, 43 insertions(+), 51 deletions(-)
diff --git a/drivers/hi
Also enable battery reporting for HID++ 1.0 devices through 2 registers:
0x07: battery status -> reports only 4 levels (critical, low, good, full)
0x0D: battery mileage -> reports true pourcentage
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 209
Hi,
This is the v2 of the series which aims at adding kernel support for the
power_supply reporting of the HID++ devices.
I updated the series with the comments from Bastien:
- fixed K750 battery state
- fixed the model names of the devices
I also stripped out the less than optimal patches that a
Or the device just answers a valid feature '0'.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index ef7ef9e..f7b2589 100644
-
The break_lock variable defined when GENERIC_LOCKBREAK is on is used
only in kernel/locking/spinlock.c when
defined(CONFIG_GENERIC_LOCKBREAK) && !defined(CONFIG_DEBUG_LOCK_ALLOC).
As a result, there is no point in enabling GENERIC_LOCKBREAK to
define one more variable in the spinlock structure th
v2->v3:
- Keep the original v1 patches but move patch 3 of v2 in front so
as to disable GENERIC_LOCKBREAK when DEBUG_LOCK_ALLOC is on.
v1->v2:
- Pack lockup and break_lock into a single 4-byte slot so as not
to in increase spinlock size when GENERIC_LOCKBREAK is
on. Hopefully tha
When ONLINE isn't set, upower should ignore the battery capacity, so there
is no need to overload it with some random values.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 28 +++-
1 file changed, 15 insertions(+), 13 dele
The debug spinlock code is a basic TATAS unfair lock irrespective
of what the underlying architecture specific spinlock implementation
is. As a result, it is sometimes possible to trigger a false positive
"lockup suspected" warning with all the cpu backtraces.
This patch re-implements the debug sp
When the debug spinlock code detects a lockup, it will print out an
error messages as well as the backtraces of all the CPUs. However, if
more than one CPUs are waiting on that lock, multiple lockup messages
will be printed leading to garbled output.
To reduce clutter in the console log, now only
Better forwarding the device name, manufacturer and serial to upower.
Note that serial is still empty, it will be filled in a later patch
in this series.
Signed-off-by: Benjamin Tissoires
---
changes in v2:
* model stripped of Logitech
* vendor Logitech -> Logitech, Inc.
* use hidpp->name for t
On Tue, Jan 31, 2017 at 10:51:06PM +0100, Thierry Reding wrote:
> On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
> [...]
> > As is, I'm stuck out here with my panel driver I submitted on December
> > 14th completely ignored, and no other developer will look at it because
> > their rev
On Thu, Feb 02, 2017 at 02:52:57PM +0100, Johannes Stezenbach wrote:
> Nope, as I've written earlier:
> > In ProductionKernelQuilts I found
> > DC-TI-PMIC-disable-power-button-support.patch so I guess it
> > might not be needed because it's probably handled by ACPI.
>
> [ +0.000338] input: Power
On Wed, Feb 01, 2017 at 04:50:15PM -0800, Vineet Gupta wrote:
> So far we didn't allow CPU private 64-bit RTC timer to register in SMP
> as the individual counters may not be synchronized across cores.
That is the case for the other archs and the per cpu clocksource are used, the
kernel is suppose
The new driver cannot be a loadable module, so if I2C is loadable, we get this
link error:
drivers/platform/built-in.o: In function `silead_ts_dmi_init':
silead_dmi.c:(.init.text+0x2ef): undefined reference to `i2c_bus_type'
This makes the Kconfig dependency stricter to require I2C=y.
Fixes: 9ee
The mediatek IOMMU driver enables some drivers that it does not directly
rely on, and that causes a warning for build testing:
warning: (MTK_IOMMU_V1) selects COMMON_CLK_MT2701_VDECSYS which has unmet
direct dependencies (COMMON_CLK && COMMON_CLK_MT2701)
warning: (MTK_IOMMU_V1) selects COMMON_CLK
On Wed, 25 Jan 2017 15:08:45 +0100
Petr Mladek wrote:
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 7180088cbb23..cc90c0a5ae21 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2158,19 +2158,18 @@ void console_unlock(void)
> }
>
> /*
Building this driver without PHYLIB fails:
ERROR: "mdio_driver_unregister" [drivers/phy/phy-bcm-nsp-usb3.ko] undefined!
ERROR: "mdio_driver_register" [drivers/phy/phy-bcm-nsp-usb3.ko] undefined!
ERROR: "mdiobus_write" [drivers/phy/phy-bcm-nsp-usb3.ko] undefined!
Unfortunately selecting PHYLIB wit
On Thu, 2 Feb 2017 11:02:57 +0900
Sergey Senozhatsky wrote:
> On (02/01/17 11:37), Steven Rostedt wrote:
> > This looks fine, but I'm curious if you tested it. That is, added a
> > bunch of printks to overflow the buffer. IIRC, I did it to the original
> > nmi code. If you haven't you may want to
Em Thu, Feb 02, 2017 at 11:43:03AM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
>
> Could you please consider merging it to the perf/urgent?
Fell thru the cracks, applied to perf/urgent, thanks for the reminder!
- Arnaldo
> Thanks,
> Namhyung
>
>
> On Wed, Jan 18, 2017 at 02:14:56PM +0900, Na
We get a link error when CCU_MULT is not set with the
newly added driver:
drivers/clk/sunxi-ng/ccu-sun5i.o:(.data.__compound_literal.17+0x4): undefined
reference to `ccu_mult_ops'
drivers/clk/sunxi-ng/ccu-sun5i.o:(.data.__compound_literal.5+0x4): undefined
reference to `ccu_mult_ops'
Fixes: 5e7
I ran into a stack frame size warning because of the on-stack copy of
the USB device structure:
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c: In function 'dvb_usbv2_disconnect':
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:1029:1: error: the frame size of
1104 bytes is larger than 1024 bytes [-Werr
On Thu, Feb 02, 2017 at 04:26:18PM +0200, Mika Westerberg wrote:
> On Thu, Feb 02, 2017 at 02:52:57PM +0100, Johannes Stezenbach wrote:
> > Looking at 0002-GPIO-Adding-AXP288-PMIC-GPIO-driver.patch from
> > ProductionKernelQuilts,
> > it doesn't seem hard to do the same for the TI PMIC, but it nee
Hi Nicolas,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6]
[cannot apply to next-20170202]
[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/Nicolas-Dichtel/uapi
On Wed 2017-02-01 14:02:43, Josh Poimboeuf wrote:
> On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote:
> > Here's v4, based on linux-next/master. Mostly minor changes this time,
> > primarily due to Petr's v3 comments.
>
> So far, the only review comments have been related to the fir
On Wed, 1 Feb 2017, Josh Poimboeuf wrote:
> For live patching and possibly other use cases, a stack trace is only
> useful if it can be assured that it's completely reliable. Add a new
> save_stack_trace_tsk_reliable() function to achieve that.
>
> Note that if the target task isn't the current
Putting 128 pointers on the stack is rather wasteful, in particular
on 64-bit architectures:
drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c: In function
'RxPktPendingTimeout':
drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c:92:1: warning: the frame
size of 1072 bytes is larger than 1024
This patch allows changing labels for cgroup mounts. Previously, running
chcon on cgroupfs would throw an "Operation not supported". This patch
specifically whitelist cgroupfs.
The patch could also allow containers to write only to the systemd cgroup
for instance, while the other cgroups are kept
Hi,
The following patch set is a cleanup of the AT91 PM code.
The main feautres is that it is now using a struct to pass arguments
between the C and the assembly code, allowing for more than 4 variables
to be passed.
It also removes instructions so it is actually faster.
The standby path is also
Since 2008, AT91_MC_SDRAMC_LPR is set to 0 at kernel initialization. There
is no use saving, changing and restoring it.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/
Use the pm_data struct members directly instead of caching them. This saves
a few load and store operations.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm_suspend.S | 40 +++-
1 file changed, 11 insertions(+), 29 deletions(-)
diff --git a/arch/ar
Hi,
On 02-02-17 15:25, Arnd Bergmann wrote:
The new driver cannot be a loadable module, so if I2C is loadable, we get this
link error:
drivers/platform/built-in.o: In function `silead_ts_dmi_init':
silead_dmi.c:(.init.text+0x2ef): undefined reference to `i2c_bus_type'
This makes the Kconfig de
When going to standby, there is no point calling the assembly function
at91_pm_suspend_in_sram(). It does exactly the same operations as the C
standby functions.
This allows to remove a few loads and tests in the suspend/resume path.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c
Instead of rely on the SoC type to select the memory controller type, use
the device tree ids as they are parsed anyway.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 29 +++--
1 file changed, 19 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-
On Thu 02-02-17 09:51:25, Al Viro wrote:
> I'm massaging that code (along with a lot of RTFS); the interesting questions
> related to VM side of things are
> * what are the relative costs of doing small vs. large batches? Some
> of get_user_pages_fast() instances have comments along the line
The USB clocks mask (uhp_udp_mask) depend on the pmc. Tie it to the pmc id
instead of the SoC.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 37 +++--
1 file changed, 23 insertions(+), 14 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/a
Putting a bare cpumask structure on the stack produces a warning on
large SMP configurations:
drivers/thermal/cpu_cooling.c: In function 'cpufreq_state2power':
drivers/thermal/cpu_cooling.c:644:1: warning: the frame size of 1056 bytes is
larger than 1024 bytes [-Wframe-larger-than=]
drivers/therm
Merge at91_pm_set_standby() in at91_dt_ramc as this is the only callsite.
That moves it to the init section.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm
As already explained for pm_suspend.S, the DDRSDR controller fails to put
LPDDR1 memories in self-refresh. Force the controller to think it has DDR2
memories during the self-refresh period, as the DDR2 self-refresh spec is
equivalent to LPDDR1, and is correctly implemented in the controller.
Signe
Having a local variable of 1024 bytes on 64-bit architectures is a bit
too much, and I ran into this warning while trying to see what functions
use the largest stack:
drivers/staging/fbtft/fbtft-sysfs.c: In function 'store_gamma_curve':
drivers/staging/fbtft/fbtft-sysfs.c:132:1: warning: the frame
Remove unnecessary header inclusions and reorder the remaining ones.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 21 +
1 file changed, 5 insertions(+), 16 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
index b4332b727e9c..3d28d
Instead of having separate global variables to hold IP dresses, move them
to struct at91_pm_data.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 44 +---
1 file changed, 21 insertions(+), 23 deletions(-)
diff --git a/arch/arm/mach-at91/pm.
The number of register we can safely pass to at91_pm_suspend_in_sram is
limited. Instead, pass the address to the at91_pm_data structure.
The offsets are automatically generated to avoid hardcoding them.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/Makefile | 33
Those macros are only used in pm.c, move them there so we can remove the
test on __ASSEMBLY__.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 6 ++
arch/arm/mach-at91/pm.h | 10 --
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-at91/pm.
On Thu, Feb 2, 2017 at 7:31 AM, Christoffer Dall wrote:
> Hi Jintack,
>
> On Wed, Feb 01, 2017 at 12:43:00PM -0500, Jintack Lim wrote:
>> The ARM architecture defines the EL1 physical timer and the virtual timer,
>> and it is reasonable for an OS to expect to be able to access both.
>> However, th
On large SMP builds, we can run into a build warning:
drivers/net/ethernet/hisilicon/hns/hns_enet.c: In function
'hns_set_irq_affinity.isra.27':
drivers/net/ethernet/hisilicon/hns/hns_enet.c:1242:1: warning: the frame size
of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
The solut
The Kconfig currently controlling compilation of this code is:
config RESET_ZX2967
bool "ZTE ZX2967 Reset Driver
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so that
when reading the driver there
The two i2c probe functions use a lot of stack since they put
an i2c_client structure in a local variable:
drivers/media/usb/em28xx/em28xx-camera.c: In function
'em28xx_probe_sensor_micron':
drivers/media/usb/em28xx/em28xx-camera.c:205:1: error: the frame size of 1256
bytes is larger than 1152 b
The cx231xx_do_i2c_scan function needs a lot of stack because
it puts an i2c_client structure on it:
drivers/media/usb/cx231xx/cx231xx-i2c.c: In function 'cx231xx_do_i2c_scan':
drivers/media/usb/cx231xx/cx231xx-i2c.c:518:1: error: the frame size of 1248
bytes is larger than 1152 bytes [-Werror=fr
mxl111sf uses a lot of kernel stack memory as it puts an i2c_client
structure on the stack:
drivers/media/usb/dvb-usb-v2/mxl111sf.c: In function 'mxl111sf_init':
drivers/media/usb/dvb-usb-v2/mxl111sf.c:953:1: error: the frame size of 1248
bytes is larger than 1152 bytes [-Werror=frame-larger-than
On 02/01/2017 06:54 PM, Boris Ostrovsky wrote:
On 02/01/2017 10:50 AM, Ross Lagerwall wrote:
Improve error handling during initialization. This fixes a crash when
running out of grant refs when creating many queues across many netdevs.
* Delay timer creation so that if initializing a queue fail
The PM initialization is now identical for all at91sam9. Merge the
functions.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/at91sam9.c | 45 +++
arch/arm/mach-at91/generic.h | 8 ++--
arch/arm/mach-at91/pm.c | 14 +-
3 fil
Hi Nicolas,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6]
[cannot apply to next-20170202]
[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/Nicolas-Dichtel/uapi
No that C functions are used, we can always enabled PM, putting the SDRAM
in self refresh but not disabling the main clock.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 12 +++-
arch/arm/mach-at91/pm.h | 3 +++
2 files changed, 10 insertions(+), 5 deletions(-)
diff --
Hi Nicolas,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6]
[cannot apply to next-20170202]
[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/Nicolas-Dichtel/uapi
gcc-7.0.1 warns about old code in ttpci:
In file included from drivers/media/pci/ttpci/av7110.c:63:0:
In function 'irdebi.isra.2',
inlined from 'start_debi_dma' at drivers/media/pci/ttpci/av7110.c:376:3,
inlined from 'gpioirq' at drivers/media/pci/ttpci/av7110.c:659:3:
drivers/media/pci/tt
The driver uses a relatively large data structure on the stack, which
showed up on my radar as we get a warning with the "latent entropy"
GCC plugin:
drivers/media/usb/pvrusb2/pvrusb2-eeprom.c:153:1: error: the frame size of 1376
bytes is larger than 1152 bytes [-Werror=frame-larger-than=]
The w
On Thu, Feb 2, 2017 at 4:45 PM, Hans de Goede wrote:
> Hi,
>
> On 02-02-17 15:25, Arnd Bergmann wrote:
>>
>> The new driver cannot be a loadable module, so if I2C is loadable, we get
>> this
>> link error:
>>
>> drivers/platform/built-in.o: In function `silead_ts_dmi_init':
>> silead_dmi.c:(.init.
On Thu, Feb 02, 2017 at 03:42:28PM +0100, Antonio Murdaca wrote:
> This patch allows changing labels for cgroup mounts. Previously, running
> chcon on cgroupfs would throw an "Operation not supported". This patch
> specifically whitelist cgroupfs.
>
> The patch could also allow containers to write
On Wed, Feb 01, 2017 at 11:25:31AM -0600, Rob Herring wrote:
> On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote:
> > +
> > + gpio-joystick: {
>
> Why do we need a whole new example?
I found it motivated to describe a use case with the new property, since
it is very different from "
On Thu, Feb 02, 2017 at 03:31:45PM +0100, Johannes Stezenbach wrote:
> On Thu, Feb 02, 2017 at 04:26:18PM +0200, Mika Westerberg wrote:
> > On Thu, Feb 02, 2017 at 02:52:57PM +0100, Johannes Stezenbach wrote:
> > > Looking at 0002-GPIO-Adding-AXP288-PMIC-GPIO-driver.patch from
> > > ProductionKern
On 2017-02-01 11:34, Rob Herring wrote:
On Tue, Jan 31, 2017 at 09:43:56AM -0600, eaja...@linux.vnet.ibm.com
wrote:
From: "Edward A. James"
Add code to tie the hwmon sysfs code and the POWER8 OCC code together,
as
well as probe the entire driver from the I2C bus. I2C is the
communication
me
Add the zx2967 thermal drivers as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5fb9b62..edfdea3 100644
--- a/MAINTAINERS
+++ b/MAINT
Hi,
On 02-02-17 16:01, Andy Shevchenko wrote:
On Thu, Feb 2, 2017 at 4:45 PM, Hans de Goede wrote:
Hi,
On 02-02-17 15:25, Arnd Bergmann wrote:
The new driver cannot be a loadable module, so if I2C is loadable, we get
this
link error:
drivers/platform/built-in.o: In function `silead_ts_dmi_
This patch adds thermal driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/thermal/Kconfig | 8 ++
drivers/thermal/Makefile | 1 +
drivers/thermal/zx2967_thermal.c | 265 +++
3 files changed, 274 insertions(+)
create mo
Herbert,
> On Feb 2, 2017, at 9:05 AM, Herbert Xu wrote:
>
> On Wed, Jan 25, 2017 at 11:44:48AM -0500, Rob Rice wrote:
>>
>> +static int ahash_export(struct ahash_request *req, void *out)
>> +{
>> +const struct iproc_reqctx_s *rctx = ahash_request_ctx(req);
>> +
>> +memcpy(out, rctx, o
This patch adds dt-binding documentation for zx2967 family thermal sensor.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Shawn Guo
---
.../devicetree/bindings/thermal/zx2967-thermal.txt | 114 +
1 file changed, 114 insertions(+)
create mode 100644 Documentat
On Thu, Feb 2, 2017 at 3:51 PM, Jintack Lim wrote:
> On Thu, Feb 2, 2017 at 7:31 AM, Christoffer Dall wrote:
>> Hi Jintack,
>>
>> On Wed, Feb 01, 2017 at 12:43:00PM -0500, Jintack Lim wrote:
>>> The ARM architecture defines the EL1 physical timer and the virtual timer,
>>> and it is reasonable fo
On Thu 2017-02-02 19:03:48, Sergey Senozhatsky wrote:
> On (02/02/17 10:07), Peter Zijlstra wrote:
> > On Thu, Feb 02, 2017 at 11:11:34AM +0900, Sergey Senozhatsky wrote:
> > > On (02/01/17 16:39), Petr Mladek wrote:
> > > [..]
> > > > I guess that you are talking about the introduction of
> > > >
On Thu, 2 Feb 2017 14:11:12 +0100
Andrew Lunn wrote:
> > The bootstrapping process in the PHY sets this bit. This is wrong
> > since the board lane layout is not "swapped"
>
> Ah, you mean a strapping pin? Resistor to ground/VCC?
Yes, exactly.
> That is a different matter. It makes it a lot l
This patch allows changing labels for cgroup mounts. Previously, running
chcon on cgroupfs would throw an "Operation not supported". This patch
specifically whitelist cgroupfs.
The patch could also allow containers to write only to the systemd cgroup
for instance, while the other cgroups are kept
On 26/01/17 20:41, Boris Ostrovsky wrote:
> Make sure they don't use these devices since they are not emulated
> for unprivileged PVH guest.
>
> Also don't initialize hypercall page for them in init_hvm_pv_info()
> since this has already been done.
>
> Signed-off-by: Boris Ostrovsky
Reviewed-by
From: Michal Suchánek
> Sent: 02 February 2017 11:30
...
> The word is marked correctly as __be64 in that patch because count and
> handle are swapped to BE when saved to it and the whole word is then
> swapped again when loaded. If you just load ((u64)IBMVTPM_VALID_CMD <<
> 56 | ((u64)VTPM_TPM_COM
On Friday 20 January 2017 11:47 PM, David Lechner wrote:
> On 01/20/2017 05:50 AM, Sekhar Nori wrote:
>> On Wednesday 18 January 2017 10:27 PM, David Lechner wrote:
>>> On 01/18/2017 03:50 AM, Sekhar Nori wrote:
On Saturday 14 January 2017 01:30 AM, David Lechner wrote:
> This allocates ex
Hi Nicolas,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6 next-20170202]
[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/Nicolas-Dichtel/uapi-export-all-headers
On 02/01/2017 03:43 PM, Jens Axboe wrote:
> On 02/01/2017 02:40 PM, Dan Williams wrote:
>> On Wed, Feb 1, 2017 at 2:35 PM, Jens Axboe wrote:
>>> On 02/01/2017 02:05 PM, Dan Williams wrote:
Warnings of the following form occur because scsi reuses a devt number
while the block layer still
On Thu, Feb 2, 2017 at 5:10 PM, Hans de Goede wrote:
> On 02-02-17 16:01, Andy Shevchenko wrote:
>> On Thu, Feb 2, 2017 at 4:45 PM, Hans de Goede wrote:
>>> Thank you.
>>>
>>> Acked-by: Hans de Goede
>>
>>
>> I'm a bit confused now:
>>
>> http://www.spinics.net/lists/platform-driver-x86/msg1040
-directories/20170202-213944
config: x86_64-randconfig-n0-02022216 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/media/media-device.c: In fu
On Sun 29-01-17 20:38:49, Kirill A. Shutemov wrote:
> For PTE-mapped THP page_check_address_transhuge() is not adequate: it
> cannot find all relevant PTEs, only the first one. It means we can miss
> some references of the page and it can result in suboptimal decisions by
> vmscan.
>
> Let's switc
Hi Bjorn,
Thanks for the patch!
On 01/30/2017 06:55 PM, Bjorn Andersson wrote:
> Pushing the SCM calls into the MDT loader reduces duplication in the
> callers and allows for non-remoteproc clients to use the helper for
> parsing and loading MDT files.
>
> Cc: Andy Gross
> Signed-off-by: Bjorn
This is a patch to fix "WARNING: line over 80 characters" found by
checkpatch.pl in vvp_page.c.
Signed-off-by: Zhengyi Shen
---
drivers/staging/lustre/lustre/llite/vvp_page.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/vvp_page.c
b/d
On Thu, Feb 2, 2017 at 5:22 PM, Michal Hocko wrote:
> On Thu 02-02-17 16:55:49, vinayak menon wrote:
>> On Thu, Feb 2, 2017 at 4:18 PM, Michal Hocko wrote:
>> > On Thu 02-02-17 11:44:22, Michal Hocko wrote:
>> >> On Tue 31-01-17 14:32:08, Vinayak Menon wrote:
>> >> > During global reclaim, the nr
On 02/02/2017 02:19 AM, Paolo Valente wrote:
> The scheme is clear. One comment, in case it could make sense and
> avoid more complexity: since put_rq_priv is invoked in two different
> contexts, process or interrupt, I didn't feel so confusing that, when
> put_rq_priv is invoked in the context wh
On Tue, 31 Jan 2017, Thierry Reding wrote:
> On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
>> I would love for drm-panel to be moved under -misc.
>
> Like that's going to magically motivate people to spend their time
> reviewing other patches. The only thing that group maintainershi
On Thu, Feb 2, 2017 at 9:06 AM, eajames wrote:
> On 2017-02-01 11:34, Rob Herring wrote:
>>
>> On Tue, Jan 31, 2017 at 09:43:56AM -0600, eaja...@linux.vnet.ibm.com
>> wrote:
>>>
>>> From: "Edward A. James"
>>>
>>> Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as
>>> well
201 - 300 of 765 matches
Mail list logo
