Add a sysfs cpu_capacity attribute with which it is possible to read and
write (thus over-writing default values) CPUs capacity. This might be
useful in situations where values needs changing after boot.
The new attribute shows up as:
/sys/devices/system/cpu/cpu*/cpu_capacity
Cc: Russell King
Add a sysfs cpu_capacity attribute with which it is possible to read and
write (thus over-writing default values) CPUs capacity. This might be
useful in situations where values needs changing after boot.
The new attribute shows up as:
/sys/devices/system/cpu/cpu*/cpu_capacity
Cc: Catalin
On 7/19/2016 6:37 AM, Mark Rutland wrote:
>> Required properties:
>> > -- compatible: must contain "qcom,hidma-1.0"
>> > +- compatible: must contain "qcom,hidma-1.0" for initial HW or
>> > "qcom,hidma-1.1"
>> > +for MSI capable HW.
> Don't we need properties to describe the MSI details (e.g.
Add Juno cpu capacity-dmips-mhz bindings information.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: Catalin Marinas
Am 19.07.2016 um 14:01 schrieb Wei Yongjun:
From: Wei Yongjun
Using list_move() instead of list_del() + list_add().
Signed-off-by: Wei Yongjun
Reviewed-by: Christian König
---
Add Juno r2 cpu capacity-dmips-mhz bindings information.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: Catalin Marinas
Am 19.07.2016 um 14:15 schrieb Wei Yongjun:
From: Wei Yongjun
In case of error, the function debugfs_create_file() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test
in the return value check should be replaced with NULL test.
On Tue, Jul 19, 2016 at 08:24:06AM -0400, Vivek Goyal wrote:
> On Tue, Jul 19, 2016 at 11:52:00AM +0100, Mark Rutland wrote:
> > Regardless, this extended syscall changes some underlying assumptions
> > made with the development of kexec_file_load, and I think treating this
> > as an extension is
Hi,
On Tue, Jul 19, 2016 at 11:02:29AM +0200, Sebastian Andrzej Siewior wrote:
> +static int arm_pmu_hp_init(void)
> +{
> + int ret;
> +
> + ret = cpuhp_setup_state_nocalls(CPUHP_AP_PERF_ARM_STARTING,
> + "AP_PERF_ARM_STARTING",
> +
On Tuesday, July 19, 2016 12:03:11 PM CEST Cyrille Pitchen wrote:
>
> Indeed I added the ARM dependency for the COMPILE_TEST case only for
> _memcpy_toio() and _memcpy_fromio(). I thought it would be enough.
>
> Also, I use _memcpy_toio() and _memcpy_fromio() on purpose as opposed to
>
On Tue, 19 Jul 2016, Gaurav Jindal (Gaurav Jindal) wrote:
> On Tue, Jul 19, 2016 at 10:47:37AM +0200, Thomas Gleixner wrote:
> > On Thu, 14 Jul 2016, Gaurav Jindal (Gaurav Jindal) wrote:
> > >
> > > tick_nohz_start_idle is called before checking the condition if the idle
> > > tick
> > > can be
Changes V6 suggested by Jacek Anaszewski:
* indentation/tab of macro values
* use inline for some helper functions
* define constant 12 (CS reference point) as semantic macro
2016-07-19 11:40:07: Changes V5 suggested by Jacek Anaszewski:
* update macros/function for audio gain
* mention PWM in
This is a driver for the Integrated Silicon Solution Inc. LED driver
chips series IS31FL319x. They can drive 1, 3, 6 or up to 9
LEDs.
Each LED is individually controllable in brightness (through pwm)
in 256 steps so that RGB LEDs can show any of ca. 16 Mio colors.
The maximum current of the
The firmware in several ZTE devices (at least the MF823/831/910
modems/mifis) use OS fingerprinting to determine which type of device to
export. In addition, these devices export a REST API which can be used to
control the type of device. So far, on Linux, the devices have been seen as
RNDIS or
> On Tue, Jul 19, 2016 at 10:30 AM, Lars Melin wrote:
> > On 2016-07-19 13:40, Kristian Evensen wrote:
> >
> >> I guess I can match on the VID/PID in usbnet, but won't it be cleaner
> >> to add a new bind() function (in cdc_ether) which matches the two PIDs
> >> and leave
(Adding Greg KH)
Hi Greg,
On 19 July 2016 at 17:45, Sumit Semwal wrote:
> Hi Greg,
>
>
> On 12 July 2016 at 23:38, Gustavo Padovan wrote:
>> From: Gustavo Padovan
>>
>> Create sync_file->fence to abstract the type
On Tuesday, July 19, 2016 05:48:07 AM Wolfram Sang wrote:
>
> > > Well, not knowing much about ACPI, I just need the conflict resolution
> > > for my latest i2c/for-next and your above branch. If you want to do it,
> > > fine with me. But maybe Jarkko will be back to office on Monday, too.
> >
>
On Tuesday, July 19, 2016 10:40:16 AM CEST Jamie Lentin wrote:
> On Mon, 18 Jul 2016, Arnd Bergmann wrote:
>
> > On Monday, July 18, 2016 11:44:24 AM CEST Thomas Petazzoni wrote:
> >>
> >> On Sun, 17 Jul 2016 22:41:35 +0200, Arnd Bergmann wrote:
> >>
> >>> I would assume that the PCIe port should
This change achieves up to 10% of speed-up for cpudl_set() calls, as
measured with a andomly generated workload of 1K,10K,100K random heap
insertions and deletions (75% cpudl_set() calls with is_valid=1 and
25% with is_valid=0), and randomly generated cpu IDs, with up to 256
CPUs, as measured on
These 2 exercise independent code paths and need different arguments.
Now you call
cpudl_clear(cp, cpu)
cpudl_set(cp, cpu, dl)
instead of
cpudl_set(cp, cpu, 0 /* dl */, 0 /* is_valid */)
cpudl_set(cp, cpu, dl, 1 /* is_valid */)
Cc: Peter Zijlstra
Cc: Juri Lelli
Hi,
this is a rework of the cpudeadline bugfix and speed-up patch-set, that
integrates all comments received so far from Luca and Juri.
The first patch is a minimally invasive (1-line) fix for the deadline
wrap-around bug. This leaves some weirdness in how cpudl_change_key() is
called.
Current code in cpudeadline.c has a bug in re-heapifying when adding a
new element at the end of the heap, because a deadline value of 0 is
temporarily set in the new elem, then cpudl_change_key() is called
with the actual elem deadline as param. However, the function compares
the new deadline to
1. heapify up factored out in new dedicated function heapify_up()
(avoids repeatition of same code)
2. call to cpudl_change_key() replaced with heapify_up() when
cpudl_set actually inserts a new node in the heap
Cc: Peter Zijlstra
Cc: Juri Lelli
Hi,
On 20/06/2016 at 12:06:38 -0400, Joe Lawrence wrote :
> Hello Alessandro and Alexandre,
>
> I noticed an interesting cmos_rtc.rtc.aie_timer on a Stratus machine
> running the 4.6 kernel, with an expiration time that puts the alarm way
> out into next year. This is easily reproducible on
Hi CK,
On Mon, 2016-07-18 at 14:58 +0800, CK Hu wrote:
> Hi, YT:
>
> One comment inline.
>
> On Fri, 2016-07-15 at 18:07 +0800, YT Shen wrote:
> > This patch add support for the Mediatek MT2701 DISP subsystem.
> > There is only one OVL engine in MT2701.
> >
> > Signed-off-by: YT Shen
From: Wei Yongjun
Add the missing clk_disable_unprepare() before return in the
error handling case.
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hi Greg,
On 12 July 2016 at 23:38, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Create sync_file->fence to abstract the type of fence we are using for
> each sync_file. If only one fence is present we use a normal struct fence
> but
From: Wei Yongjun
In case of error, the function debugfs_create_*() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test
in the return value check should be replaced with NULL test.
(defined(CONFIG_DEBUG_FS) make sure debugfs is enabled)
From: Wei Yongjun
In case of error, the function debugfs_create_file() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test
in the return value check should be replaced with NULL test.
(defined(CONFIG_DEBUG_FS) make sure debugfs is enabled)
On 07/15/2016 08:38 PM, Charles Gong wrote:
"SYSRQ + J" triggers a call to emergency_thaw_all(). Currently, this is an
infinite loop. Once we trigger it, we'll need to do a hard power-cycle. There
are users reporting this bug from 2012 to 2016, for example, at
This patch allows flock, posix locks, ofd locks and leases to work
correctly on overlayfs.
Instead of using the underlying inode for storing lock context use the
overlay inode. This allows locks to be persistent across copy-up.
This is done by introducing locks_inode() helper and using it
On overlayfs relatime_need_update() needs inode times to be correct on
overlay inode. But i_mtime and i_ctime are updated by filesystem code on
underlying inode only, so they will be out-of-date on the overlay inode.
This patch copies the times from the underlying inode if needed. This
can't be
The documentation of touch_atime() doesn't match the location of the
definition and list of parameters anymore. Updating it.
Fixes: e8d2e3f31127 ("vfs: update ovl inode before relatime check")
Signed-off-by: Luis de Bethencourt
---
Hi,
This patch is based on Miklos'
On Mon, Jul 18, 2016 at 12:27:42PM -0700, Joe Perches wrote:
> Using \b isn't good enough to isolate what appears to be a
> commit id in a commit message.
>
> Make sure there is a space or a quote like character after
> a continuous run of hexadecimal characters that could be
> a commit id.
>
>
On Tue, Jul 19, 2016 at 07:13:24PM +1000, Michael Ellerman wrote:
>
> I'll assume patch 2 has your ack :)
Sure,
Acked-by: Herbert Xu
Thanks,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key:
From: Kuninori Morimoto
rcar-thermal is supporting both thermal_zone_of_sensor_register() and
thermal_zone_device_register(). But thermal_zone_of_sensor_register()
doesn't enable hwmon as default.
This patch enables it to keep compatibility
Signed-off-by:
On Tue, Jul 19, 2016 at 10:47:37AM +0200, Thomas Gleixner wrote:
> On Thu, 14 Jul 2016, Gaurav Jindal (Gaurav Jindal) wrote:
> >
> > tick_nohz_start_idle is called before checking the condition if the idle
> > tick
> > can be stopped. In case when can_stop_idle_tick returns 0, the function
> >
On 27/06/2016 at 13:36:04 -0400, Joe Lawrence wrote :
> Ping? This isn't a major problem, but can setup endless RTC interrupts
> under certain conditions on said hardware.
>
Well like said in my previous mail, I don't think the rollover is the
issue here but I'm interested in knowing what
People complain about the driver saying there's no valid RAPL domains
in a VM, and doing so at KERN_ERR severity. Downgrade this to KERN_INFO
if running on a hypervisor, since it is basically stating the obvious.
Suggested-by: Peter Zijlstra
Cc: Jacob Pan
> BUG: KASAN: use-after-free in proc_map_files_readdir+0x2e3/0x5a0 at addr
> 88044feb2044
Just in case can you addr2line this address or post disassembly?
On Tue, 19 Jul 2016 12:50:19 +0200
Paolo Bonzini wrote:
> People complain about the driver saying there's no valid RAPL domains
> in a VM, and doing so at KERN_ERR severity. Downgrade this to
> KERN_INFO if running on a hypervisor, since it is basically stating
> the
Signed-off-by: H. Nikolaus Schaller
---
.../devicetree/bindings/leds/is31fl319x.txt| 59 ++
1 file changed, 59 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/is31fl319x.txt
diff --git
On 13 June 2016 at 10:54, Baolin Wang wrote:
> When mmc host HW supports busy signalling (using R1B as response), We
> shouldn't use 'host->max_busy_timeout' as the limitation when deciding
> the max discard sectors that we tell the generic BLOCK layer about.
> Instead, we
Andrew,
On Mon 20-06-16 14:43:48, Michal Hocko wrote:
> From: Michal Hocko
>
> The only case where the oom_reaper is not triggered for the oom victim
> is when it shares the memory with a kernel thread (aka use_mm) or with
> the global init. After "mm, oom: skip vforked tasks
From: Wei Yongjun
Fixes the following sparse warnings:
drivers/gpu/drm/arc/arcpgu_drv.c:52:5: warning:
symbol 'arcpgu_gem_mmap' was not declared. Should it be static?
drivers/gpu/drm/arc/arcpgu_drv.c:134:48: warning:
Using plain integer as NULL pointer
From: Wei Yongjun
In case of error, the function debugfs_create_*() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test
in the return value check should be replaced with NULL test.
(defined(CONFIG_DEBUG_FS) make sure debugfs is enabled)
Hi,
> Am 19.07.2016 um 14:29 schrieb Jacek Anaszewski :
>
> Tweaked the tabulation of macro values a bit more and applied
thanks!
I think you better know how you want to have them exactly (checkpatch didn't
complain).
> the patches to the for-4.9 branch of
On Thu, 14 Jul 2016, Luck, Tony wrote:
> So the core part of __intel_rdt_sched_in() will look like:
>
> /*
>* Precedence rules:
>* Processes assigned to an rdtgroup use that group
>* wherever they run. If they don't have an rdtgroup
>* we see if the current
From: Wei Yongjun
Fixes the following sparse warning:
drivers/gpu/drm/virtio/virtgpu_display.c:349:37: warning:
symbol 'virtio_mode_config_helpers' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
Some callers of __irq_set_trigger() masks all flags besides trigger mode
flags. Actually it is unnecessary operation now, because the
__irq_set_trigger() already does this before usage of flags.
Signed-off-by: Alexander Kuleshov
---
kernel/irq/chip.c | 1 -
Hi Zhang
These are resend patches for rcar-thermal hwmon.
Kuninori Morimoto (2):
thermal: rcar-thermal: enable hwmon when thermal_zone
thermal: hwmon: EXPORT_SYMBOL_GPL for thermal hwmon sysfs
drivers/thermal/rcar_thermal.c | 20 ++--
On Mon, 18 Jul 2016, Arnd Bergmann wrote:
On Monday, July 18, 2016 11:44:24 AM CEST Thomas Petazzoni wrote:
On Sun, 17 Jul 2016 22:41:35 +0200, Arnd Bergmann wrote:
I would assume that the PCIe port should work out of the box with the driver
Unfortunately, no. The PCIe on Orion5x requires
Hi all,
Le 18/07/2016 à 21:59, Arnd Bergmann a écrit :
> On Monday, July 18, 2016 12:55:11 PM CEST Brian Norris wrote:
>> On Mon, Jul 18, 2016 at 09:35:39PM +0200, Arnd Bergmann wrote:
>>> On Friday, July 15, 2016 5:45:07 PM CEST Brian Norris wrote:
Applied to l2-mtd.git with that fixup.
>>>
On Mon, Jul 18, 2016 at 02:39:28PM -0400, Sinan Kaya wrote:
> Adding a new binding for qcom,hidma-1.1 to distinguish HW supporting
> MSI interrupts from the older revision.
>
> Signed-off-by: Sinan Kaya
> ---
> Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt | 3
Hi Brian,
Le 16/07/2016 à 02:45, Brian Norris a écrit :
> Hi Cyrille,
>
> On Wed, Jul 13, 2016 at 06:32:42PM -0700, Brian Norris wrote:
>> On Mon, Jun 13, 2016 at 05:10:26PM +0200, Cyrille Pitchen wrote:
>>> This driver add support to the new Atmel QSPI controller embedded into
>>> sama5d2x
Hi CK,
On Tue, 2016-07-19 at 13:39 +0800, CK Hu wrote:
> Hi, YT:
>
> Some comments inline.
>
> On Fri, 2016-07-15 at 18:07 +0800, YT Shen wrote:
> > From: shaoming chen
> >
> > add dsi interrupt control
> >
> > Signed-off-by: shaoming chen
From: Thomas Gleixner
Straight forward conversion w/o bells and whistles.
Signed-off-by: Thomas Gleixner
Signed-off-by: Anna-Maria Gleixner
Reviewed-by: Sebastian Andrzej Siewior
Acked-by: Mark Rutland
Hi Sargun,
On 07/19/2016 11:32 AM, Sargun Dhillon wrote:
This allows user memory to be written to during the course of a kprobe.
It shouldn't be used to implement any kind of security mechanism
because of TOC-TOU attacks, but rather to debug, divert, and
manipulate execution of semi-cooperative
> From: 'Dave Young' [mailto:dyo...@redhat.com]
> Sent: Tuesday, July 19, 2016 3:52 PM
> Hi,
> On 07/19/16 at 05:51am, 河合英宏 / KAWAI,HIDEHIRO wrote:
> > Hi,
> >
> > > From: 'Dave Young' [mailto:dyo...@redhat.com]
> > > Sent: Monday, July 18, 2016 6:02 PM
> > > On 07/15/16 at 11:50am, 河合英宏 /
The recent update in the reset subsystem requires all reset consumers
to be explicit when requesting reset lines. For detail, see the log
of commit 3c35f6edc09b ("reset: Reorder inline reset_control_get*()
wrappers").
The devm_reset_control_get_optional() is deprecated, and falls into
the
On Tue, Jul 19, 2016 at 11:52:00AM +0100, Mark Rutland wrote:
> On Tue, Jul 19, 2016 at 08:55:56AM +0800, Dave Young wrote:
> > On 07/18/16 at 11:07am, Mark Rutland wrote:
> > > On Mon, Jul 18, 2016 at 10:30:24AM +0800, Dave Young wrote:
> > > > I do not think it is worth to add another syscall
On Tue, 19 Jul 2016 12:32:42 +0800
Minfei Huang wrote:
> From: Minfei Huang
>
> We do a lot of memory allocation in function init_vq, and don't handle
> the allocation failure properly. Then this function will return 0,
> although initialization fails due
There is no need for a semi-colon at the end of a switch statement so
remove it.
Signed-off-by: Charles Keepax
---
drivers/extcon/extcon-arizona.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/extcon/extcon-arizona.c
ARM systems may be configured to have cpus with different power/performance
characteristics within the same chip. In this case, additional information
has to be made available to the kernel (the scheduler in particular) for it
to be aware of such differences and take decisions accordingly.
On Tue, Jul 19, 2016 at 5:42 AM, Vinay Simha wrote:
> just to be inline with the existing code (funcs:
> mipi_dsi_dcs_get_power_mode, mipi_dsi_dcs_get_pixel_format) in
> drivers/gpu/drm/drm_mipi_dsi.c followed the same for
> mipi_dsi_dcs_get_display_brightness
>
> We may need
On Tue, 19 Jul 2016, Chen Yu wrote:
> On 2016年07月19日 16:36, Thomas Gleixner wrote:
> > On Tue, 19 Jul 2016, Chen Yu wrote:
> > > Further investigation shows that, the problem is caused by setting
> > > /sys/power/pm_trace to 1 before the 1st hibernation, since once
> > > pm_trace is enabled, the
PM_DEBUG and PM_ADVANCED_DEBUG bring some information useful for
development and they should not cause any significant overhead. Enable
them in default configuration so debugging would be slightly easier.
Signed-off-by: Krzysztof Kozlowski
---
On 07/15/2016 08:00 AM, Leon Romanovsky wrote:
> On Thu, Jul 14, 2016 at 09:46:14AM +0300, Netanel Belgazal wrote:
>> This is a driver for the ENA family of networking devices.
>>
>> Signed-off-by: Netanel Belgazal
>> ---
>>
>> Notes:
> ...
>
>> - Increase driver
Hi Philipp, CK,
Thanks for the review.
On Mon, 2016-07-18 at 10:36 +0200, Philipp Zabel wrote:
> Hi CK, YT,
>
> Am Montag, den 18.07.2016, 14:32 +0800 schrieb CK Hu:
> > Hi, YT:
> >
> > One comment inline.
> >
> >
> > On Fri, 2016-07-15 at 18:07 +0800, YT Shen wrote:
> > > We need to acquire
Hello,
On 19 July 2016 at 00:59, Mark Brown wrote:
> On Tue, Jul 19, 2016 at 12:35:40AM +0200, Michal Suchanek wrote:
>
>> config SPI_SPIDEV
>> - tristate "User mode SPI device driver support"
>> + bool "User mode SPI device driver support"
>
> This is a step back,
Commit ebb657babfa9 ("staging: comedi: ni_mio_common: clarify the
cmd->start_arg validation and use") introduced a backwards compatibility
issue in the use of asynchronous commands on the AO subdevice when
`start_src` is `TRIG_EXT`. Valid values for `start_src` are `TRIG_INT`
(for internal,
From: Wei Yongjun
Remove duplicated include.
Signed-off-by: Wei Yongjun
---
drivers/hwtracing/coresight/coresight-etm4x.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/hwtracing/coresight/coresight-etm4x.c
From: Wei Yongjun
Remove duplicated include.
Signed-off-by: Wei Yongjun
---
arch/arm/mach-ux500/cpu-db8500.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-ux500/cpu-db8500.c b/arch/arm/mach-ux500/cpu-db8500.c
From: Wei Yongjun
There is a error message within devm_ioremap_resource
already, so remove the dev_err call to avoid redundant
error message.
Signed-off-by: Wei Yongjun
---
drivers/mtd/spi-nor/atmel-quadspi.c | 2 --
1 file
Commit-ID: 1f3b0f8243cb934307f59bd4d8e43b868e61d4d9
Gitweb: http://git.kernel.org/tip/1f3b0f8243cb934307f59bd4d8e43b868e61d4d9
Author: Gaurav Jindal
AuthorDate: Thu, 14 Jul 2016 12:04:20 +
Committer: Thomas Gleixner
CommitDate: Tue,
On 18/07/2016 15:02, Maxime Ripard wrote:
> On Fri, Jul 15, 2016 at 11:59:13AM +0200, Quentin Schulz wrote:
>> The Allwinner SoCs all have an ADC that can also act as a touchscreen
>> controller and a thermal sensor. For now, only the ADC and the thermal
>> sensor drivers are probed by the MFD,
From: Wei Yongjun
Using list_move() instead of list_del() + list_add().
Signed-off-by: Wei Yongjun
---
mm/slab.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
index 32c2296..cc6d816
From: Wei Yongjun
Remove duplicated include.
Signed-off-by: Wei Yongjun
---
arch/x86/platform/ce4100/ce4100.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/platform/ce4100/ce4100.c
Am 19.07.2016 um 14:14 schrieb Wei Yongjun:
From: Wei Yongjun
In case of error, the function debugfs_create_*() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test
in the return value check should be replaced with NULL test.
With the introduction of cpu capacity-dmips-mhz bindings, CPU capacities
can now be calculated from values extracted from DT and information
coming from cpufreq. Add parsing of DT information at boot time, and
complement it with cpufreq information. Also, store such information
using per CPU
Hi all,
version 6 of "CPUs capacity information for heterogeneous systems" patchset [1]
(please refer to previous postings to get some context).
A few changes from v5:
- rebase on top of mainline (4.7-rc6)
- documentation fixes
- kcalloc() for raw_capacity array
- pr_err() only for partial
On Tue, Jul 19, 2016 at 11:04:23AM +0200, Quentin Schulz wrote:
> >> +/* TP_CTRL1 bits */
> >> +#define SUNXI_GPADC_STYLUS_UP_DEBOUNCE(x) ((x) << 12) /* 8 bits */
> >> +#define SUNXI_GPADC_STYLUS_UP_DEBOUNCE_EN BIT(9)
> >> +#define SUNXI_GPADC_TOUCH_PAN_CALI_EN BIT(6)
> >> +#define
Add TC2 cpu capacity binding information.
Cc: Liviu Dudau
Cc: Sudeep Holla
Cc: Lorenzo Pieralisi
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian
Am 19.07.2016 um 14:15 schrieb Wei Yongjun:
From: Wei Yongjun
In case of error, the function debugfs_create_*() returns NULL
pointer not ERR_PTR() if debugfs is enabled. The IS_ERR() test
in the return value check should be replaced with NULL test.
On Fri, Jul 01, 2016 at 11:45:45AM +0300, Jarkko Sakkinen wrote:
> On Fri, Jul 01, 2016 at 11:43:23AM +0300, Jarkko Sakkinen wrote:
> > On Thu, Jun 30, 2016 at 10:25:43AM -0700, apro...@chromium.org wrote:
> > > From: Andrey Pronin
> > >
> > > Some chips incorrectly support
On 19 July 2016 at 05:27, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Remove duplicated include.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/hwtracing/coresight/coresight-etm4x.c | 1 -
> 1 file changed, 1
On Tue, 19 Jul 2016, Eric Auger wrote:
> msi_doorbell_pages sum up the number of iommu pages of a given order
adding () to the function name would make it immediately clear that
msi_doorbell_pages is a function.
> +/**
> + * msi_doorbell_pages: compute the number of iommu pages of size 1 <<
On Tue, 19 Jul 2016 10:49:54 -0400
Sinan Kaya wrote:
> On 7/18/2016 8:24 PM, Alex Williamson wrote:
> >>> nit, might make sense to replace EPERM with ENOENT and use EINVAL here.
> >>> > >
> >> >
> >> > Sure, will take carr of it.
> >> >
> >> > Anything else I need
For rtl8188ee, we pass -Idrivers/net/wireless/rtlwifi/ to gcc,
however that directy no longer exists, so evidently this option
is no longer required here and can be removed to avoid a warning
when building with 'make W=1' or 'gcc -Wmissing-include-dirs'
Signed-off-by: Arnd Bergmann
Compiling the rtlwifi drivers for ARM with gcc -Wextra warns about lots of
incorrect code that results from 'char' being unsigned here, e.g.
staging/rtl8192e/rtl8192e/r8192E_phy.c:1072:36: error: comparison is always
false due to limited range of data type [-Werror=type-limits]
Using "goto" in that "switch" statement only makes it harder to follow
control flow and doesn't bring any advantages. Rewrite the code to avoid
using "goto".
Signed-off-by: Andrey Smirnov
---
drivers/mtd/nand/nand_base.c | 13 +
1 file changed, 5
A recent commit added a write to the watchdog test code for doing the "magic
close", but that caused a compile-time warning:
Documentation/watchdog/src/watchdog-test.c: In function ‘main’:
Documentation/watchdog/src/watchdog-test.c:94:5: warning: ignoring return value
of ‘write’, declared with
If no user specified chip->select_chip() function is provided, code in
nand_base.c will automatically set this hook to nand_select_chip(),
which in turn depends on chip->cmd_ctrl() hook being valid. Not
providing both of those functions in NAND controller driver (for example
by mistake) will
On Tue 19-07-16 09:54:26, Johannes Weiner wrote:
> On Mon, Jul 18, 2016 at 10:41:24AM +0200, Michal Hocko wrote:
> > The original intention of f9054c70d28b was to help with the OOM
> > situations where the oom victim depends on mempool allocation to make a
> > forward progress. We can handle that
On Mon, Jul 18, 2016 at 09:26:00PM -0700, Florian Fainelli wrote:
> Le 18/07/2016 à 20:24, Andrew Lunn a écrit :
> > On Mon, Jul 18, 2016 at 08:45:38PM -0400, Vivien Didelot wrote:
> >> Add a new function for DSA drivers to handle the switchdev
> >> SWITCHDEV_ATTR_ID_BRIDGE_AGEING_TIME attribute.
Previously sc16is7xx_power was called in order to set the device to a
low power mode.
However since SC16IS7XX_EFR_ENABLE_BIT was not set beforehand this
suspend request had not effect.
Also, soft-reset the device prior to port initialization. It may
otherwise be in a state (interrupt
Hi,
On 18/07/2016 at 17:17:44 +0530, Pratyush Anand wrote :
> Hi RTC-Maintainers,
>
>
> On Mon, Jul 4, 2016 at 9:49 PM, Pratyush Anand wrote:
> > On 27/06/2016:10:19:07 AM, Pratyush Anand wrote:
> >> On 21/06/2016:10:25:34 AM, Pratyush Anand wrote:
> >> > We have observed on
> Hi Vivien
>
> This is doing a read/modify/write, so should really hold the mutex.
Upps. The mutex is held. Sorry for the noise.
Andrew
[[lkp] [x86] eb008eb6f8:
kmsg.glue_helper:Unknown_symbol_blkcipher_walk_done(err#)] On 19/07/2016 (Tue
10:23) kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit
On 07/19/16 02:24, Arnd Bergmann wrote:
> A recent commit added a write to the watchdog test code for doing the "magic
> close", but that caused a compile-time warning:
>
> Documentation/watchdog/src/watchdog-test.c: In function ‘main’:
> Documentation/watchdog/src/watchdog-test.c:94:5: warning:
401 - 500 of 1940 matches
Mail list logo