If only 1 of the 2 'ioremap' fails, then there is a small leak.
Signed-off-by: Christophe JAILLET
---
arch/cris/arch-v32/drivers/mach-fs/nandflash.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/cris/arch-v32/drivers/mach-fs/nandflash.c
b/arch/cris/arch-v32
On 04/26/2017 01:25 AM, lixi...@cmss.chinamobile.com wrote:
> From: Xiubo Li
>
> For each target there will be one ring, when the target number
> grows larger and larger, it could eventually runs out of the
> system memories.
>
> In this patch for each target ring, currently for the cmd area
> t
get_reg() can be reentered on architectures with prioritized interrupts
(m68k in this case), causing f->reg_index to be incremented after the
range check. Out of bounds memory access past the pt_regs struct results.
This will go mostly undetected unless access is beyond end of memory.
Prevent the
On Sat, Apr 29, 2017 at 07:54:30PM +0200, Cezary Gapinski wrote:
> Sparse spits out a warnings about __le16 and unsigned short assignment.
> Change the type of size and event members of struct hostif_hdr
> to __le16 and correct conversion to the proper cpu type.
I believe that this patch is correc
This driver is predominantly used by device tree systems, all
of which can deal with modern GPIO descriptors. The legacy
GPIO API is only used by one SH board so make the GPIO
descriptor the default way to deal with it.
As an intended side effect we do not need to look around in
the device tree fo
The option to invert the output of the GPIO (active low) is
not used by the only platform still using platform data to
set up a GPIO backlight (one SH board). Delete the option
as we do not expect to expand the use of board files for
this driver, and GPIO descriptors intrinsically keep track
of any
Do you need a loan to pay up bill or to start a business? Email Us
On Fri, Apr 28, 2017 at 05:26:17PM +0300, Dan Carpenter wrote:
> On Fri, Apr 28, 2017 at 04:19:28PM +0200, Ilia Sergachev wrote:
> > Checkpatch emits WARNING: Avoid line continuations in quoted strings.
> >
> > Remove line continuations - split strings using quotes.
> >
> > Signed-off-by: Ilia Se
On Fri, Apr 28, 2017 at 03:01:32PM +0200, Ilia Sergachev wrote:
> On Fri, 28 Apr 2017 14:20:21 +0200
> Greg Kroah-Hartman wrote:
>
> >
> > Nope, the whole thing still doesn't apply:
> >
> > checking file drivers/staging/ks7010/ks_wlan_net.c
> > Hunk #1 FAILED at 230.
> > Hunk #2 FAILED at 343.
On 30/04/2017 04:11, Tetsuo Handa wrote:
> Casey Schaufler wrote:
>> On 4/29/2017 12:02 PM, Mickael Salaun wrote:
>>> Check if the registering LSM already registered hooks just before. This
>>> enable to split hook declarations into multiple files without
>>> registering multiple time the same LSM
On Sun, Apr 30, 2017 at 03:07:58PM +0900, J. R. Okajima wrote:
> Hello,
>
> Since v4.11-rc7 I can see the workqueue stops on my development/test system.
> Git-bisecting tells me the suspicious commit is
> c053b5a 2017-04-11 drm/i915: Don't call synchronize_rcu_expedited under
> struct_mutex
Commit-ID: 2006cddf3c2fd6b4114c704229552a903f180c71
Gitweb: http://git.kernel.org/tip/2006cddf3c2fd6b4114c704229552a903f180c71
Author: Sebastian Andrzej Siewior
AuthorDate: Fri, 28 Apr 2017 12:01:05 +0100
Committer: Thomas Gleixner
CommitDate: Sun, 30 Apr 2017 11:19:01 +0200
jump_label
Commit-ID: d54bb72551b999ddf7ceef87ed58fb4cb2ee6dfc
Gitweb: http://git.kernel.org/tip/d54bb72551b999ddf7ceef87ed58fb4cb2ee6dfc
Author: Mark Rutland
AuthorDate: Fri, 28 Apr 2017 12:01:06 +0100
Committer: Thomas Gleixner
CommitDate: Sun, 30 Apr 2017 11:19:01 +0200
arm64/cpufeature: Use s
Commit-ID: 216646e4d82e847791f0ba66c439dedd36cb119f
Gitweb: http://git.kernel.org/tip/216646e4d82e847791f0ba66c439dedd36cb119f
Author: Wei Yongjun
AuthorDate: Thu, 27 Apr 2017 15:21:13 +
Committer: Thomas Gleixner
CommitDate: Sun, 30 Apr 2017 11:21:16 +0200
irqchip/mbigen: Fix retu
This coding style issue was found by checkpatch.pl script. Using
__func__ instead of hardcoded function name should help in future
refactoring of this code. This patch also uses a more common logging
format.
Signed-off-by: Dhiru Kholia
---
drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +-
From: Alexander Usyskin
mei_cl_bus_rescan is used only in bus.c,
so make it local to the file and mark static.
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 2 +-
drivers/misc/mei/mei_dev.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
notifcation -> notification
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hw.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/mei/hw.h b/drivers/misc/mei/hw.h
index e1e4d47d4d7d..5c8286b40b62 100644
--- a/drivers/misc/mei/hw.h
+++ b/drivers/misc/mei/hw.h
@@
On Sat, Apr 29, 2017 at 10:21:33AM -0700, Joe Perches wrote:
> On Sat, 2017-04-29 at 22:17 +0530, Dhiru Kholia wrote:
> > This coding style issue was found by checkpatch.pl script. Using
> > __func__ instead of hardcoded function name should help in future
> > refactoring of this code.
> >
> >
On 2017年04月30日 13:48, Mike Christie wrote:
On 04/26/2017 01:25 AM, lixi...@cmss.chinamobile.com wrote:
for_each_sg(data_sg, sg, data_nents, i) {
@@ -275,22 +371,26 @@ static void alloc_and_scatter_data_area(struct tcmu_dev
*udev,
from = kmap_atomic(sg_page(sg)) + sg->off
[...]
+
+static bool tcmu_get_empty_blocks(struct tcmu_dev *udev,
+ struct tcmu_cmd *tcmu_cmd,
+ uint32_t blocks_needed)
Can drop blocks_needed.
Will fix it.
[...]
-static void *tcmu_get_block_addr(struct tcmu_dev *udev, uin
kmem_cache is a frequently used data in kernel. During the code reading, I
found maybe we could save some space in some cases.
1. On 64bit arch, type int will occupy a word if it doesn't sit well.
2. cpu_slab->partial is just used when CONFIG_SLUB_CPU_PARTIAL is set
3. cpu_partial is just used whe
On 64bit arch, struct is 8-bytes aligned, so int will occupy a word if it
doesn't sits well.
This patch pack red_left_pad with reserved to save 8 bytes for struct
kmem_cache on a 64bit arch.
Signed-off-by: Wei Yang
---
include/linux/slub_def.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
kmem_cache->cpu_partial is just used when CONFIG_SLUB_CPU_PARTIAL is set,
so wrap it with config CONFIG_SLUB_CPU_PARTIAL will save some space
on 32bit arch.
This patch wrap kmem_cache->cpu_partial in config CONFIG_SLUB_CPU_PARTIAL
and wrap its sysfs too.
Signed-off-by: Wei Yang
---
include/linu
cpu_slab's field partial is used when CONFIG_SLUB_CPU_PARTIAL is set, which
means we can save a pointer's space on each cpu for every slub item.
This patch wrap cpu_slab->partial in CONFIG_SLUB_CPU_PARTIAL and wrap its
sysfs too.
Signed-off-by: Wei Yang
---
include/linux/slub_def.h | 2 ++
mm/
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
A single fix for a cputime accounting regression whihc got introduced in
the 4.11 cycle.
Thanks,
tglx
-->
Frederic W
Commit-ID: 88d879d29f9cc0de2d930b584285638cdada6625
Gitweb: http://git.kernel.org/tip/88d879d29f9cc0de2d930b584285638cdada6625
Author: Janakarajan Natarajan
AuthorDate: Tue, 25 Apr 2017 16:44:03 -0500
Committer: Thomas Gleixner
CommitDate: Sun, 30 Apr 2017 13:35:11 +0200
Prevent timer
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
The final fixes for 4.11:
- Prevent a triple fault with function graph tracing triggered via suspend
to ram.
- Prevent optimizing for size w
Hi Zhang,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.11-rc8 next-20170428]
[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/ying-zhang22455-nxp-com/arm64-ls1046a-dts-add
The seccomp/test_harness.h file contains useful helpers to build tests.
Moving it to the selftest directory should benefit to other test
components.
Signed-off-by: Mickaël Salaün
Cc: Andy Lutomirski
Cc: Kees Cook
Cc: Shuah Khan
Cc: Will Drewry
Link:
https://lkml.kernel.org/r/CAGXu5j+8CVz8vL5
On Thu, Apr 27, 2017 at 02:20:21PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function
> 'rtw_cfg80211_preinit_wiphy':
> drivers/staging
On Sat, Apr 29, 2017 at 01:32:09PM +0530, Laxman Dewangan wrote:
> On Saturday 29 April 2017 05:36 AM, Matthias Kaehlcke wrote:
> > -- regulator-settling-time-us: Settling time, in microseconds, for voltage
> > - change if regulator have the constant time for any level voltage change.
> > - This
Toshi noticed that the new support for a region-level badblocks missed
the case where errors are cleared due to BTT I/O.
An initial attempt to fix this ran into a "sleeping while atomic"
warning due to taking the nvdimm_bus_lock() in the BTT I/O path to
satisfy the locking requirements of __nvdimm
On Thu, Apr 27, 2017 at 10:42:49AM +0100, Sudeep Holla wrote:
> On 26/04/17 14:55, Mark Brown wrote:
> > As I'm getting fed up of saying: if the values you are setting are not
> > voltages and do not behave like voltages then the hardware should not be
> > represented as a voltage regulator since
On Sat, Apr 29, 2017 at 10:05 AM, Martin Kaiser wrote:
> Thus wrote Andy Shevchenko (andy.shevche...@gmail.com):
>> On Tue, Apr 18, 2017 at 12:11 PM, Martin Kaiser wrote:
>> Aren't 0 and 0444 different by meaning?
>
> my undestanding is that proc_create() calls proc_create_data(), where
>
>i
On Fri, Apr 28, 2017 at 12:56:21AM -0400, Javier Martinez Canillas wrote:
> The Samsung email address will stop working soon, so use my personal
> email address instead.
Acked-by: Mark Brown
signature.asc
Description: PGP signature
On Sat, Apr 29, 2017 at 9:52 AM, Ritesh Raj Sarraf wrote:
> Hello,
>
> On Fri, 2017-04-28 at 22:17 +0300, Andy Shevchenko wrote:
>> On Wed, Feb 22, 2017 at 12:24 PM, Ritesh Raj Sarraf wrote:
>>
>> > Any further comment on this patch ? Will this be accepted ?
>> > Please give a N/ACK.
>>
>> Sorry
The patch
ASoC: dwc: Disallow building designware_pcm as a module
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
ASoC: codec: wm8960: Relax bit clock computation when using PLL
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 ho
The patch
ASoC: codec: wm9860: avoid maybe-uninitialized warning
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
Sometimes we want to printk() multiple lines in a group without being
disturbed by concurrent printk() from interrupts and/or other threads.
For example, mixed printk() output of multiple thread's dump makes it
hard to interpret.
This patch introduces fixed-sized statically allocated buffers for
b
Hi Matthias,
2017-04-22 6:39 GMT+09:00 Matthias Kaehlcke :
> clang generates plenty of these warnings in different parts of the code,
> to an extent that the warnings are little more than noise. Disable the
> 'address-of-packed-member' warning.
>
> Signed-off-by: Matthias Kaehlcke
As far as I
Hi Matthias,
2017-04-22 6:39 GMT+09:00 Matthias Kaehlcke :
> clang generates plenty of these warnings in different parts of the code.
> They are mostly caused by container_of() and other macros which declare
> a "const *" variable for their internal use which triggers a
> "duplicate 'const' spec
On Fri, Apr 28, 2017 at 11:57:36AM -0700, Vineet Gupta wrote:
> Hi,
>
> Can we please backport upstream ecd43afdbe72017aefe48080631eb625e177ef4d
> ("ARCv2:
> save r30 on kernel entry as gcc uses it for code-gen") to 4.2 to 4.9 kernels.
>
> While the issue cites gcc, it is general deficiency of k
Hello,
I have noticed by execution of another script for the semantic patch language
(Coccinelle software) that the function “clkdev_add_clkout” does not contain
null pointer checks after calls of the function “kzalloc”.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/
Usage of device_lock() for dax_region attributes is unnecessary and
deadlock prone. It's unnecessary because the order of registration /
un-registration guarantees that drvdata is always valid. It's deadlock
prone because it sets up this situation:
ndctl D0 2170 2082 0x
We are always allocating extra 255Bytes of memory to handle ITE
physical address alignment requirement. The kmalloc() satisfies
the ITE alignment since the ITS driver is requesting a minimum
size of ITS_ITT_ALIGN bytes.
Let's try to allocate the exact amount of memory that is required
for ITEs to
Hi Robert,
2017-04-26 5:07 GMT+09:00 Robert Jarzmik :
> Masahiro Yamada writes:
>
>> Hi Robert,
>>> diff --git a/scripts/tags.sh b/scripts/tags.sh
>>> index a2ff3388e5ea..35cb64d5211c 100755
>>> --- a/scripts/tags.sh
>>> +++ b/scripts/tags.sh
>>> @@ -106,7 +106,8 @@ all_compiled_sources()
>>>
The current ITS driver is assuming every ITS hardware implementation
supports minimum of 16bit INTID. But this is not true, as per GICv3
specification, INTID field is IMPLEMENTATION DEFINED in the range of
14-24 bits. We might see an unpredictable system behavior on systems
where hardware support l
From: Markus Elfring
Date: Sun, 30 Apr 2017 17:45:19 +0200
* Multiplications for the size determination of memory allocations
indicated that array data structures should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle softw
On Sat, Apr 29, 2017 at 09:38:22PM -0700, Matthew Wilcox wrote:
> It sounds more like AT_NO_ESCAPE ... or AT_BELOW, or something.
I considered AT_ROACH_MOTEL at one point... Another interesting
question is whether EXDEV would've been better than ELOOP.
Opinions?
On Sun, 2017-04-30 at 22:54 +0900, Tetsuo Handa wrote:
> Sometimes we want to printk() multiple lines in a group without being
> disturbed by concurrent printk() from interrupts and/or other threads.
> For example, mixed printk() output of multiple thread's dump makes it
> hard to interpret.
>
> T
Evaluate LDFLAGS_BUILD_ID (which involves invoking the compiler) only
once instead of over and over.
This provides a ~20% reduction in null build time with x86 allnoconfig:
$ make allnoconfig && make -j8
$ perf stat -r5 -e sched:sched_process_exec make -j8
- 2 119 sched:sched_process_e
On 29/04/17 21:37, Stefan Bruens wrote:
> On Mittwoch, 26. April 2017 08:59:47 CEST Jonathan Cameron wrote:
>> On 26/04/17 07:19, Jonathan Cameron wrote:
>>> On 17/04/17 23:08, Stefan Bruens wrote:
On Freitag, 14. April 2017 17:12:03 CEST Jonathan Cameron wrote:
> [...]
>>>
4. Any user of
2017-04-29 17:24 GMT+03:00 Matwey V. Kornilov :
> 2017-04-29 11:16 GMT+03:00 Matwey V. Kornilov :
>> 2017-04-28 16:30 GMT+03:00 Bin Liu :
>>> On Fri, Apr 28, 2017 at 04:15:09PM +0300, Matwey V. Kornilov wrote:
2017-04-28 15:43 GMT+03:00 Bin Liu :
> On Fri, Apr 28, 2017 at 03:13:55PM +0300
On Mon, Apr 17, 2017 at 03:23:55PM +0300, Laurent Pinchart wrote:
> Hi Daniel,
>
> Thank you for the patch (and the investigation).
>
> On Monday 17 Apr 2017 18:52:39 Daniel Axtens wrote:
> > Currently, disconnecting a USB webcam while it is in use prints out a
> > number of warnings, such as:
>
On Sun, Apr 23, 2017 at 02:53:49PM +1000, Daniel Axtens wrote:
> Currently, disconnecting a USB webcam while it is in use prints out a
> number of warnings, such as:
>
> WARNING: CPU: 2 PID: 3118 at
> /build/linux-ezBi1T/linux-4.8.0/fs/sysfs/group.c:237
> sysfs_remove_group+0x8b/0x90
> sysfs gro
On Fri, 28 Apr 2017 12:02:58 +0200, Greg KH wrote:
> On Wed, Apr 26, 2017 at 06:15:40PM +0200, Karim Eshapa wrote:
>
>> Fixing sparse warnings incorrect type assignment.
>>
>> Signed-off-by: Karim Eshapa
>> ---
>> drivers/staging/wlan-ng/hfa384x_usb.c | 24 ++--
>> 1 file chan
On 28/04/17 17:17, Brian Masney wrote:
> On Fri, Apr 28, 2017 at 05:55:58PM +0200, Sebastian Reichel wrote:
>> isl29030 is basically the same chip. The only difference
>> is the chip's first pin. For isl29028 its named ADDR0 and
>> can be used to change the chip's i2c address. For isl29030
>> on th
On 27/04/17 16:30, Sebastian Reichel wrote:
> Drop legacy twl4030_get_madc_conversion() method. It has been
> used by drivers to get madc data before it conversion to IIO
> API. There are no users in the mainline kernel anymore.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Jonathan Cameron
> -
On 27/04/17 16:30, Sebastian Reichel wrote:
> All madc users have been converted to IIO API, so drop the
> legacy API. The function is still used inside of the driver.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Jonathan Cameron
> ---
> drivers/iio/adc/twl4030-madc.c | 5 +++--
> include/l
On 27/04/17 16:30, Sebastian Reichel wrote:
> This functionality is not used by the IIO subsystem. Due
> to removal of legacy API it can also be removed.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Jonathan Cameron
> ---
> drivers/iio/adc/twl4030-madc.c | 70
>
On 27/04/17 16:30, Sebastian Reichel wrote:
> twl4030-madc.h is no longer used by anything outside of
> the iio driver, so it can be merged into the driver.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Jonathan Cameron
> ---
> drivers/iio/adc/twl4030-madc.c | 113 +++
On 27/04/17 17:51, Guenter Roeck wrote:
> On Thu, Apr 27, 2017 at 05:30:06PM +0200, Sebastian Reichel wrote:
>> This driver is no longer needed:
>>
>> * It has no mainline users
>> * It has no DT support and OMAP is DT only
>> * iio-hwmon can be used for madc, which also works with DT
>>
>> Sign
Use time_before_eq time comparison defind kernel macro
that has safety check.
Signed-off-by: Karim Eshapa
---
drivers/video/fbdev/omap/lcd_mipid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/omap/lcd_mipid.c
b/drivers/video/fbdev/omap/lcd_mipid.c
inde
On Sun, Apr 16, 2017 at 02:11:31PM +0300, Laurent Pinchart wrote:
> Hi Greg,
>
> On Wednesday 21 Dec 2016 10:59:54 Greg KH wrote:
> > On Tue, Dec 20, 2016 at 11:19:23AM +, Dave Stevenson wrote:
> > > On 09/12/16 09:43, Greg KH wrote:
> > >> On Fri, Dec 09, 2016 at 11:14:41AM +0200, Laurent Pin
On Sun, Apr 30, 2017 at 06:19:59PM +0200, Greg KH wrote:
> On Sun, Apr 16, 2017 at 02:11:31PM +0300, Laurent Pinchart wrote:
> > Hi Greg,
> >
> > On Wednesday 21 Dec 2016 10:59:54 Greg KH wrote:
> > > On Tue, Dec 20, 2016 at 11:19:23AM +, Dave Stevenson wrote:
> > > > On 09/12/16 09:43, Greg K
On 28/04/17 05:11, Shrirang Bagul wrote:
> On Wed, 2017-04-26 at 06:37 +0100, Jonathan Cameron wrote:
>> On 19/04/17 15:05, Shrirang Bagul wrote:
>>> This patch fixes the sensor platform data initialisation for st_pressure
>>> and st_accel device drivers. Without this patch, the driver fails to
>>>
On 28/04/17 15:52, Fabrice Gasnier wrote:
> On 04/27/2017 07:49 AM, Jonathan Cameron wrote:
>> On 26/04/17 09:55, Benjamin Gaignard wrote:
>>> 2017-04-26 10:17 GMT+02:00 Fabrice Gasnier :
Add support for TRGO2 trigger that can be found on STM32F7.
Add additional master modes supported by
On Wed, Apr 26, 2017 at 01:44:43PM -0700, Ricardo Neri wrote:
> I regard that the role of this function is to obtain the the segment
> selector from either of the prefixes or inferred from the operands. It
> is the role of caller to determine if the segment selector should be
> ignored.
No, this i
Hi!
[...]
+* FixMe:
+* Device without no_thermal = true not register (err -22)
+* Len of platform device name "max17211-battery.X.auto"
+* more than 20 chars limit in THERMAL_NAME_LENGTH from
+* include/uapi/linux/thermal.h
+*/
IIRC we already h
>
> But I don't see any warning when I run it with --stdio. Could you
> show me the format file of sys_enter_mmap?
I found the problem. The kernel version I was testing on fails to
initialize some fields in the tracepoint structure, so my format
looked like:
# cat /sys/kernel/debug/tracing/event
>>
>> An appears to be correctly parsed by event_read_print in
>> tools/lib/tracevent/event-parse.c . Has anyone seen this before?
>
> What kernel are you running?
>
> I just built and booted v4.11-rc8 with a v4.11-rc8 perf:
I was running an internal version. I found the bug in an internal
commit.
On Sun, Apr 30, 2017 at 5:26 AM, Mickaël Salaün wrote:
> The seccomp/test_harness.h file contains useful helpers to build tests.
> Moving it to the selftest directory should benefit to other test
> components.
Unless Shuah thinks this should live in a new include/ directory, this
looks fine to me
On Sun, Apr 30, 2017 at 12:39 PM, Kees Cook wrote:
>
> On Sun, Apr 30, 2017 at 5:26 AM, Mickaël Salaün wrote:
> > The seccomp/test_harness.h file contains useful helpers to build tests.
> > Moving it to the selftest directory should benefit to other test
> > components.
>
> Unless Shuah thinks th
This passes the of_node from the bq27xxx i2c battery driver to the
common code, so that it can be registered and provide external supplies
linked with device-tree.
Signed-off-by: Paul Kocialkowski
---
drivers/power/supply/bq27xxx_battery.c | 5 -
drivers/power/supply/bq27xxx_battery_i2c.
The status reported directly by the battery controller is not always
reliable and should be corrected based on the current draw information.
This implements such a correction with a dedicated function, called
when retrieving the supply status.
Signed-off-by: Paul Kocialkowski
---
drivers/power/
This introduces a dedicated status change work to look for power
status change. It is triggered by external power change notifications
and periodically retries detecting a power status change for 5 seconds.
This is largely inspired by a similar mechanism from the sbs-battery
driver.
Signed-off-by
This uses the managed devices resources version of the
power_supply_register_no_ws function to register the power supply.
Signed-off-by: Paul Kocialkowski
---
drivers/power/supply/bq27xxx_battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/supply/bq27xxx_b
This renames the work structure member to poll_work, in anticipation
of the introduction of a status_work member used to detect status
changes.
Signed-off-by: Paul Kocialkowski
---
drivers/power/supply/bq27xxx_battery.c | 20 ++--
drivers/power/supply/bq27xxx_battery_i2c.c |
Fixes sparse warning "dubious: x & !y" in logical expression.
Signed-off-by: Guru Das Srinagesh
---
.../media/atomisp/pci/atomisp2/css2400/runtime/binary/src/binary.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/drivers/staging/media/atomisp/pci/atomisp2/css2400/runt
This moves the cros-ec-sbs dtsi to a new rk3288-veyron-chromebook-sbs
dtsi since it only concerns rk3288 veyron Chromebooks.
Other Chromebooks (such as the tegra124 nyans) also have sbs batteries
and don't use this dtsi, that only makes sense when used with
rk3288-veyron-chromebook anyway.
Signed
This lists the GPIO charger node as power supply for the battery, which
in turns allows receiving external power notifications and synchronizing
the charging state as soon as possible.
Signed-off-by: Paul Kocialkowski
---
arch/arm/boot/dts/rk3288-veyron-minnie.dts | 1 +
1 file changed, 1 insert
This lists the GPIO charger node as power supply for the battery, which
in turns allows receiving external power notifications and synchronizing
the charging state as soon as possible.
Signed-off-by: Paul Kocialkowski
---
arch/arm/boot/dts/rk3288-veyron-chromebook-sbs.dtsi | 1 +
arch/arm/boot/d
On 04/30/2017 09:41 AM, Jonathan Cameron wrote:
On 27/04/17 17:51, Guenter Roeck wrote:
On Thu, Apr 27, 2017 at 05:30:06PM +0200, Sebastian Reichel wrote:
This driver is no longer needed:
* It has no mainline users
* It has no DT support and OMAP is DT only
* iio-hwmon can be used for madc,
Hi,
On 23-04-17 19:37, Kenneth Hsu wrote:
This fixes a sparse warning regarding an undeclared symbol. Since the
function is private to rtw_recv.c, it should be declared as static.
Signed-off-by: Kenneth Hsu
Looks good to me:
Reviewed-by: Hans de Goede
Regards,
Hans
---
drivers/stagi
Add FPGA manager driver for loading Arria-V/Cyclone-V/Stratix-V
and Arria-10 FPGAs via CvP.
Signed-off-by: Anatolij Gustschin
---
Changes in v4:
- Update description about supported FPGA models in Kconfig
and commit log
- use writel() for iomem accesses
- factor out dummy write code
The MSB for the first byte of touch data transmission is always 1. Make
it a little more obvious we're testing this bit by using BIT(7).
Signed-off-by: Martin Kepplinger
---
I'd still use the definition :) but otherwise I'd write the following.
It really doesn't matter though.
thanks for the qu
Hi,
On Sun, Apr 30, 2017 at 05:27:07PM +0100, Jonathan Cameron wrote:
> On 28/04/17 17:17, Brian Masney wrote:
> > On Fri, Apr 28, 2017 at 05:55:58PM +0200, Sebastian Reichel wrote:
> >> isl29030 is basically the same chip. The only difference
> >> is the chip's first pin. For isl29028 its named A
Imagine you're completely new to Linux, just real quick, ok? What do you do?
Wouldn't having a look at README be under first if no *the* first thing?
Ah there it is: README. "Linux kernel". nice! So what's that?
"This file was moved to .. Please notice that there are several".
Wtf!? Why? Ca
Hi Paul,
Am Sonntag, 30. April 2017, 20:30:52 CEST schrieb Paul Kocialkowski:
> This moves the cros-ec-sbs dtsi to a new rk3288-veyron-chromebook-sbs
> dtsi since it only concerns rk3288 veyron Chromebooks.
>
> Other Chromebooks (such as the tegra124 nyans) also have sbs batteries
> and don't use
Hi,
On Sun, Apr 30, 2017 at 08:32:10PM +0300, Михайлов Алексей Анатольевич wrote:
> > IIRC we already had problems with small THERMAL_NAME_LENGTH before.
> > I suggest to add another patch, that increases THERMAL_NAME_LENGTH
> > (don't forget to Cc/To the thermal subsystem people).
> May be rename
From: Frank Rowand
An undeclared variable was used in a macro that evaluates to nothing
when CONFIG_DEBUG_LOCK_ALLOC is not defined. Change to use the correct
variable that does exist.
---
reported by kbuild test robot on on robh/for-next
https://lkml.org/lkml/2017/4/29/134
drivers/of/b
On 04/29/17 17:22, kbuild test robot wrote:
> Hi Frank,
>
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on v4.11-rc8 next-20170428]
> [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-
Hi,
On Sun, Apr 30, 2017 at 08:21:51AM +0300, Alex A. Mihaylov wrote:
> > > Slave device provide software layer for access to internal registers
> > > MAX17211/MAX17215 chip.
> > Please convert this to regmap.There is no generic w1 handler, but you can
> > provide custom
> > read/write functions.
Le dimanche 30 avril 2017 à 22:37 +0200, Heiko Stuebner a écrit :
> Hi Paul,
>
> Am Sonntag, 30. April 2017, 20:30:52 CEST schrieb Paul Kocialkowski:
> > This moves the cros-ec-sbs dtsi to a new rk3288-veyron-chromebook-sbs
> > dtsi since it only concerns rk3288 veyron Chromebooks.
> >
> > Other
On Sun, 30 Apr 2017, Wei Yang wrote:
> kmem_cache is a frequently used data in kernel. During the code reading, I
> found maybe we could save some space in some cases.
>
> 1. On 64bit arch, type int will occupy a word if it doesn't sit well.
> 2. cpu_slab->partial is just used when CONFIG_SLUB_CPU
On Wed, 26 Apr 2017, Vlastimil Babka wrote:
> > Such an application typically already has such logic and executes a
> > binding after discovering its numa node configuration on startup. It would
> > have to be modified to redo that action when it gets some sort of a signal
> > from the script tell
This patch adds the LED_BRIGHTNESS_FAST flag to allow the driver to
indicate that the brightness_set() callback is implemented on a fastpath
so that the LED core may choose to for example use a hrtimer to
implement the duration of a trigger for better timing accuracy.
Suggested-by: Jacek Anaszewsk
This is for readability as well as to avoid checkpatch warnings when
adding new bit flag information in the future.
Signed-off-by: David Lin
---
include/linux/leds.h | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/linux/leds.h b/include/linux/leds.h
index
Hi,
These patch series add the LED_BRIGHTNESS_FAST flag support for
ledtrig-transient to use hrtimer so that platforms with high-resolution timer
support can have better accuracy in the trigger duration timing. The need for
this support is driven by the fact that Android has removed the timed_oupu
1 - 100 of 165 matches
Mail list logo
