Only decrement *iff* we're possitive. Warn if we've hit
a situation where the counter is already 0 after we're done
with a modprobe call, this would tell us we have an unaccounted
counter access -- this in theory should not be possible as
only one routine controls the counter, however preemption is
Running out of our modprobe limit is not a memory limit but
a system specific established limitation set to avoid a possible
recursive issue with modprobe. This gives userspace a better idea
of what happened if we can't load a module, it could use this to
wait and try again.
Signed-off-by: Luis R.
This adds helpers for getting access to the kmod count and limit from
userspace. While at it, this also lets userspace fine tune the kmod
limit after boot, it uses the shiny new proc_douintvec_minmax().
These knobs should help userspace more gracefully and deterministically
handle module loading.
Just use the simplified rate limit printk when the max modprobe
limit is reached, while at it throw out a bone should the error
be triggered.
Signed-off-by: Luis R. Rodriguez
---
kernel/kmod.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/kernel/kmod.c b/kernel/k
Commit e7d316a02f6838 ("sysctl: handle error writing UINT_MAX to u32 fields")
added proc_douintvec() to start help adding support for unsigned int,
this however was only half the work needed, all these issues are present
with the current implementation:
o Printing the values shows a negative val
kmod has an optimization in place whereby if a some kernel code
uses request_module() on a module already loaded we never bother
userspace as the module already is loaded. This is not true for
get_fs_type() though as it uses aliases.
Additionally kmod <= v19 was broken -- it returns 0 to modprobe
diff --git a/Makefile b/Makefile
index 7b0c92f53169..b38abe9adef8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 8
-SUBLEVEL = 12
+SUBLEVEL = 13
EXTRAVERSION =
NAME = Psychotic Stoned Sheep
diff --git a/arch/arc/include/asm/delay.h b/arch/arc/include/asm/delay.h
I'm announcing the release of the 4.4.37 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.8.13 kernel.
All users of the 4.8 kernel series must upgrade.
The updated 4.8.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.8.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 705eb9e38fce..b57ec79b4941 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 36
+SUBLEVEL = 37
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/arc/include/asm/delay.h b/arch/arc/include/asm/delay.h
index
On Thu, Dec 08, 2016 at 07:21:37PM +0300, Kirill A. Shutemov wrote:
> 5-level paging support is required from hardware when compiled with
> CONFIG_X86_5LEVEL=y. We may implement runtime switch support later.
>
> Signed-off-by: Kirill A. Shutemov
...
> diff --git a/arch/x86/boot/cpuflags.c b/arc
On 12/08/2016 08:39 AM, Jerome Glisse wrote:
>> On 12/08/2016 08:39 AM, Jérôme Glisse wrote:
>>> > > Architecture that wish to support un-addressable device memory should
>>> > > make
>>> > > sure to never populate the kernel linar mapping for the physical range.
>> >
>> > Does the platform someh
On Thu, Dec 8, 2016 at 12:05 PM, Borislav Petkov wrote:
>
> The cpuid() in cpuflags.c doesn't zero ecx which, if we have to be
> pedantic, it should do. It calls CPUID now with the ptr value of its 4th
> on 64-bit and 3rd arg on 32-bit, respectively, IINM.
In fact, just do a single cpuid_count(),
As a followup to this posting from yesterday:
https://marc.info/?l=linux-block&m=148115232806065&w=2
this is version 2. I wanted to post a new one fairly quickly, as there
ended up being a number of potential crashes in v1. This one should be
solid, I've run mq-deadline on both NVMe and regular r
Signed-off-by: Jens Axboe
---
block/Kconfig.iosched | 43 +--
block/blk-mq-sched.c| 19 +++
block/blk-mq-sched.h| 1 +
block/blk-mq.c | 3 +++
block/elevator.c| 5 -
drivers/nvme/host/pci.c | 1 +
include/l
Currently we pass in to run the queue async, but don't flag the
queue to be run. We don't need to run it async here, but we should
run it. So fixup the parameters.
Signed-off-by: Jens Axboe
---
block/blk-flush.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/blk-flush.
Hi everyone,
I am testing the timeslice of vCPU thread in QEMU/KVM. In principle,
the timeslice should be stable under following workload but it is
unstable after I do experiments with following workload. I appreciate
it if you can give me some suggestions. Thanks in advance.
Workload settings:
I
Signed-off-by: Jens Axboe
---
block/Kconfig.iosched | 6 +
block/Makefile| 1 +
block/mq-deadline.c | 647 ++
3 files changed, 654 insertions(+)
create mode 100644 block/mq-deadline.c
diff --git a/block/Kconfig.iosched b/block/Kconfi
Takes a list of requests, and dispatches it. Moves any residual
requests to the dispatch list.
Signed-off-by: Jens Axboe
---
block/blk-mq.c | 85 --
block/blk-mq.h | 1 +
2 files changed, 48 insertions(+), 38 deletions(-)
diff --git a/blo
We have a variant for all hardware queues, but not one for a single
hardware queue.
Signed-off-by: Jens Axboe
---
block/blk-mq.c | 18 +++---
include/linux/blk-mq.h | 1 +
2 files changed, 12 insertions(+), 7 deletions(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 9
Signed-off-by: Jens Axboe
---
block/Makefile | 2 +-
block/blk-core.c | 9 +-
block/blk-exec.c | 3 +-
block/blk-flush.c| 7 +-
block/blk-merge.c| 3 +
block/blk-mq-sched.c | 246 +++
block/blk-mq-
Signed-off-by: Jens Axboe
---
block/elevator.c | 8
include/linux/elevator.h | 5 +
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/block/elevator.c b/block/elevator.c
index a18a5db274e4..40f0c04e5ad3 100644
--- a/block/elevator.c
+++ b/block/elevator.c
@@ -248
Update driver drv260x to use generic device properties
Remove platform data
Signed-off-by: Jingkui Wang
---
drivers/input/misc/drv260x.c | 43 ---
1 file changed, 8 insertions(+), 35 deletions(-)
diff --git a/drivers/input/misc/drv260x.c b/drivers/input/m
On Thu, Dec 08, 2016 at 12:08:53PM -0800, Linus Torvalds wrote:
> Especially since that's some of the ugliest inline asm ever due to the
> nasty BX handling.
Yeah, about that: why doesn't gcc handle that for us like it would
handle a clobbered register? I mean, it *should* know that BX is live
whe
On 12/08/2016 02:17 PM, Jingkui Wang wrote:
> Update driver drv260x to use generic device properties
> Remove platform data
>
> Signed-off-by: Jingkui Wang
> ---
> drivers/input/misc/drv260x.c | 43 ---
> 1 file changed, 8 insertions(+), 35 deletions(-)
>
>
On Thu, Dec 8, 2016 at 10:47 AM, Luis R. Rodriguez wrote:
> This adds a new stress test driver for kmod: the kernel module loader.
> The new stress test driver, test_kmod, is only enabled as a module right
> now. It should be possible to load this as built-in and load tests early
> (refer to the f
On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
> We currently statically limit the number of modprobe threads which
> we allow to run concurrently to 50. As per Keith Owens, this was a
> completely arbitrary value, and it was set in the 2.3.38 days [0]
> over 16 years ago in year 2000.
On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
> kmod_concurrent is used as an atomic counter for enabling
> the allowed limit of modprobe calls, provide wrappers for it
> to enable this to be expanded on more easily. This will be done
> later.
>
> Signed-off-by: Luis R. Rodriguez
> --
On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
> While looking for early possible module loading failures I was
> able to reproduce a memory leak possible with kmemleak. There
> are a few rare ways to trigger a failure:
>
> o we've run into a failure while processing kernel parameters
Hi,
On 08.12.2016 00:15, Francois Romieu wrote:
> Lino Sanfilippo :
>> The driver uses a private lock for synchronization between the xmit
>> function and the xmit completion handler, but since the NETIF_F_LLTX flag
>> is not set, the xmit function is also called with the xmit_lock held.
>>
>> O
> On 12/08/2016 08:39 AM, Jerome Glisse wrote:
> >> On 12/08/2016 08:39 AM, Jérôme Glisse wrote:
> >>> > > Architecture that wish to support un-addressable device memory should
> >>> > > make
> >>> > > sure to never populate the kernel linar mapping for the physical
> >>> > > range.
> >> >
> >> >
A recent clean-up declared och_flags as a int rather than fmode_t. This
lead to the following sparse warning:
drivers/staging/lustre/lustre/llite/file.c:106:30: warning: restricted
fmode_t degrades to integer
This patch fixes this issue.
Fixes: 0a1200991234f7 ("staging: lustre: cleanup lustre_li
Fix the following build errors on X86_32 !GPIOLIB
sound/soc/samsung/tm2_wm5110.c:220:3: error: implicit declaration
of function 'gpiod_set_value_cansleep' [-Werror=implicit-function-declaration]
sound/soc/samsung/tm2_wm5110.c:438:24: error: implicit declaration
of function 'devm_gpiod_get' [-Werro
Both SND_SOC_SMARTQ and SND_SOC_SAMSUNG_TM2_WM5110
use gpio/consumer.h
This patch adds GPIOLIB || COMPILE_TEST to Kconfig entries
to avoid any build errors.
See commit 638f958baeaf
("extcon: Allow compile test of GPIO consumers if !GPIOLIB")
for similar problem and explanations.
Reported-by: Krz
On Thu, Nov 17, 2016 at 02:25:01PM -0800, David Daney wrote:
> From: David Daney
>
> Some (defective) PCIe devices are not able to reliably do link
> retraining.
>
> Check to see if ASPM is possible between link partners before
> configuring common clocking, and doing the resulting link retraini
On Thu, Dec 08, 2016 at 09:43:01PM +0100, Fabian Frederick wrote:
> Fix the following build errors on X86_32 !GPIOLIB
>
> sound/soc/samsung/tm2_wm5110.c:220:3: error: implicit declaration
> of function 'gpiod_set_value_cansleep' [-Werror=implicit-function-declaration]
> sound/soc/samsung/tm2_wm511
On Thu, Dec 08, 2016 at 09:43:19PM +0100, Fabian Frederick wrote:
> Both SND_SOC_SMARTQ and SND_SOC_SAMSUNG_TM2_WM5110
> use gpio/consumer.h
> This patch adds GPIOLIB || COMPILE_TEST to Kconfig entries
> to avoid any build errors.
I think that is not entirely correct. There won't be build errors h
The clocksource delta to nanoseconds conversion is using signed math, but
the delta is unsigned. This makes the conversion space smaller than
necessary and in case of a multiplication overflow the conversion can
become negative. The conversion is done with scaled math:
s64 nsec_delta = ((s64)c
If the timekeeping CPU is scheduled out long enough by a hypervisor the
clocksource delta multiplication can overflow and as a result time can go
backwards. That's insane to begin with, but people already triggered a
signed multiplication overflow, so a unsigned overflow is not necessarily
impossib
Kill the ever confusing typedef and use u64.
NOT FOR INCLUSION - Must be regenerated at some point via coccinelle
Not-Signed-off-by: Thomas Gleixner
---
arch/alpha/kernel/time.c|4 -
arch/arc/kernel/time.c | 12 ++--
arch/arm/mach-d
cycles_t is defined as u64, so casting it to u64 is a pointless and
confusing exercise. cycles_t should simply go away and be replaced with a
plain u64 to avoid further confusion.
Signed-off-by: Thomas Gleixner
---
kernel/time/timekeeping.c |5 ++---
1 file changed, 2 insertions(+), 3 deleti
Propagating a unsigned value through signed variables and functions makes
absolutely no sense and is just prone to (re)introduce subtle signed
vs. unsigned issues as happened recently.
Clean it up.
Signed-off-by: Thomas Gleixner
---
kernel/time/timekeeping.c | 26 +-
1
This series addresses the recently reintroduced signed vs. unsigned
wreckage by cleaning up the whole call chain instead of just making a
simple s64 -> u64 'fix' at one point and keeping the rest signed, which
eventually led to the unintended signed conversion and brought back an
issue that was fix
The resume code must deal with a clocksource delta which is potentially big
enough to overflow the 64bit mult.
Replace the open coded handling with the proper function.
Signed-off-by: Thomas Gleixner
---
kernel/time/timekeeping.c | 26 +-
1 file changed, 5 insertions(+
On 2016-12-07 18:37, Marek Vasut wrote:
> On 12/08/2016 02:26 AM, Stefan Agner wrote:
>> On 2016-12-07 16:59, Stefan Agner wrote:
>>> On 2016-12-07 16:49, Marek Vasut wrote:
On 12/08/2016 01:27 AM, Stefan Agner wrote:
> The DRM subsystem specifies the pixel clock polarity from a
> cont
Hi all,
This patch series introduces async requests for read and write
operations. If the read, or the write, is an async operation to begin
with (aio), we can avoid waiting for the server response.
This is my first contribution to 9p, so feedback and suggestions are
welcome!
Stefano Stabellini
If the write is an async operation, send a 9p request and return
EIOCBQUEUED. Do not wait for completion.
Complete the write operation from a callback instead.
Signed-off-by: Stefano Stabellini
---
net/9p/client.c | 80 -
1 file changed, 7
Introduce a simple helper function to only prepare a p9 client request,
without any waiting involved.
Currently not utilized, but it will be used by a later patch.
Signed-off-by: Stefano Stabellini
---
net/9p/client.c | 12
1 file changed, 12 insertions(+)
diff --git a/net/9p/clie
The parameter can be NULL.
Currently not utilized, but it will be used in later patches.
Signed-off-by: Stefano Stabellini
---
fs/9p/vfs_addr.c| 8
fs/9p/vfs_dir.c | 2 +-
fs/9p/vfs_file.c| 4 ++--
fs/9p/xattr.c | 4 ++--
include/net/9p/client.h | 7 +++
If the read is an async operation, send a 9p request and return
EIOCBQUEUED. Do not wait for completion.
Complete the read operation from a callback instead.
Signed-off-by: Stefano Stabellini
---
net/9p/client.c | 88 +++--
1 file changed, 86
Add a few fields to struct p9_req_t. Callback is the function which will
be called upon requestion completion. offset, rsize, pagevec and kiocb
store important information regarding the read or write request,
essential to complete the request.
Currently not utilized, but they will be used in a lat
On Thu, Dec 08, 2016 at 12:28:07PM -0800, Kees Cook wrote:
> On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
> > diff --git a/kernel/kmod.c b/kernel/kmod.c
> > index 0277d1216f80..cb6f7ca7b8a5 100644
> > --- a/kernel/kmod.c
> > +++ b/kernel/kmod.c
> > @@ -44,6 +44,9 @@
> > @@ -186,6 +174
On Thu, Dec 08, 2016 at 12:29:42PM -0800, Kees Cook wrote:
> On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
> > kmod_concurrent is used as an atomic counter for enabling
> > the allowed limit of modprobe calls, provide wrappers for it
> > to enable this to be expanded on more easily. Th
On Fri, 2016-12-09 at 01:33 +0800, fu@linaro.org wrote:
> From: Fu Wei
>
> This patch defines pr_fmt(fmt) for all pr_* functions,
> then the pr_* doesn't need to add "arch_timer:" everytime.
trivia:
> diff --git a/drivers/clocksource/arm_arch_timer.c
> b/drivers/clocksource/arm_arch_timer.
On Thu, Dec 8, 2016 at 2:30 PM, Kees Cook wrote:
> On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
>> While looking for early possible module loading failures I was
>> able to reproduce a memory leak possible with kmemleak. There
>> are a few rare ways to trigger a failure:
>>
>> o we
From: Murali Karicheri
Fix the pa clock to point to the clkpa which has clock rate of 1/3 of PA
PLL clock and add clock names.
Signed-off-by: Murali Karicheri
Signed-off-by: Grygorii Strashko
---
arch/arm/boot/dts/keystone-k2e-netcp.dtsi | 3 ++-
arch/arm/boot/dts/keystone-k2hk-netcp.dtsi |
On Thu, Dec 8, 2016 at 1:10 PM, Luis R. Rodriguez wrote:
> On Thu, Dec 8, 2016 at 2:30 PM, Kees Cook wrote:
>> On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote:
>>> While looking for early possible module loading failures I was
>>> able to reproduce a memory leak possible with kmemleak.
On Thu, Dec 08, 2016 at 11:29:30AM +0800, Jia He wrote:
> Fixes: a4b349540a ("powerpc/mm: Cleanup LPCR defines")
> Signed-off-by: Jia He
Acked-by: Paul Mackerras
On Thu, 2016-12-08 at 10:01 +0200, Tomi Valkeinen wrote:
>
> > DRM drivers don't strike me as suitable for small/slow cores with dumb
> > framebuffers or simple 2D only accel, such as the one found in the ASpeed
> > BMCs.
>
> Then the DRM framework should be improved to be suitable.
Dave ? :-)
From: Kan Liang
On x86, NMI handler is the most important part which brings overhead
for sampling. Adding a pmu specific overhead type
PERF_PMU_SAMPLE_OVERHEAD for it.
For other architectures which may don't have NMI, the overhead type can
be reused.
Signed-off-by: Kan Liang
---
arch/x86/even
From: Kan Liang
Iterating all events which need to receive side-band events also bring
some overhead.
The side-band events overhead PERF_CORE_SB_OVERHEAD is a common overhead
type.
Signed-off-by: Kan Liang
---
include/uapi/linux/perf_event.h | 1 +
kernel/events/core.c| 17 ++
From: Kan Liang
This series only include the kernel related patches.
Profiling brings additional overhead. High overhead may impacts the
behavior of the profiling object, impacts the accuracy of the
profiling result, and even hang the system.
Currently, perf has dynamic interrupt throttle mechan
From: Kan Liang
A new perf record is introduced to export perf overhead information to
userspace. So the user can measure the overhead of sampling directly.
If the user doesn't want to use this feature, it can be switched off by
configuring the user space tool.
Perf overhead is actually the sum
From: Kan Liang
In STAT_START, resets overhead counter for each possible cpuctx of event
pmu.
In STAT_DONE, generate overhead information for each possible cpuctx and
reset the overhead counteris.
Signed-off-by: Kan Liang
---
arch/x86/events/core.c | 37 +
1
From: Kan Liang
It only needs to generate the overhead statistics once when perf is
done. But there is no good place in the kernel for that.
A new ioctl PERF_EVENT_IOC_STAT is introduced to notify the kernel when
the tool 'start' and 'done'.
In 'start', the kernel resets the overhead numbers.
In
From: Kan Liang
Multiplexing overhead is one of the key overhead when the number of
events is more than available counters.
The multiplexing overhead PERF_CORE_MUX_OVERHEAD is a common overhead
type.
Signed-off-by: Kan Liang
---
include/uapi/linux/perf_event.h | 1 +
kernel/events/core.c
On Thu, 2016-12-08 at 16:21 +0100, Daniel Vetter wrote:
> Yeah, small drivers like these we have piles now, things exploded a lot
> after atomic landed two years ago. And they seem to shrink with every
> release a bit more (since lots more drivers gives you lots more insight
> into what other refac
On Fri, 2016-12-09 at 08:23 +1100, Benjamin Herrenschmidt wrote:
> > From memory, David claimed you cannot directly work on the fb with a
> > "proper"
>
> DRM driver. Maybe I misunderstood but then the DRM shines by its complete
> absence of useful documentation
That sentence should have been i
From: Jean-Jacques Hiblot
From: Jean-Jacques Hiblot
The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace
operation to specify if registers need to saved/restored by the ftrace handler.
This is needed by kgraft and possibly other ftrace-based tools, and the ARM
architecture
Hi Florian,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.9-rc8]
[cannot apply to arm-soc/for-next next-20161208]
[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/Florian
On Thu 2016-12-08 21:32:12, Lino Sanfilippo wrote:
> Hi,
>
> On 08.12.2016 00:15, Francois Romieu wrote:
> > Lino Sanfilippo :
> >> The driver uses a private lock for synchronization between the xmit
> >> function and the xmit completion handler, but since the NETIF_F_LLTX flag
> >> is not set, t
On 32-bit ARM with 64-bit dma_addr_t I get this warning about an
incorrect format string:
In file included from
/git/arm-soc/drivers/net/ethernet/mellanox/mlx5/core/alloc.c:42:0:
drivers/net/ethernet/mellanox/mlx5/core/alloc.c: In function
‘mlx5_frag_buf_alloc_node’:
drivers/net/ethernet/mellano
On Thu 2016-12-08 13:58:47, Jie Deng wrote:
>
>
> On 2016/12/7 17:48, Pavel Machek wrote:
> > Hi!
> >
> >> This patch provides the initial driver for 25/40/50/100 GbE
> >> devices using Synopsys DWC Enterprise Ethernet (XLGMAC)
> >>
> >> Signed-off-by: Jie Deng
> > I trust this is different hard
On Fri, 2016-12-09 at 08:34 +1100, Benjamin Herrenschmidt wrote:
> As I mentioned earlier, probably 1 or 2 years ago, Dave made the
> argument that shadowing through memory was necessary and precluded 2D
> accel, though I don't fully remember the root of the argument. If that
> is indeed not the ca
The array for initializing the cle is set up on the stack with
almost entirely constant data and then passed to a function that
converts it into HW specific bit patterns. With the latest
addition, the size of this array has grown to the point that
we get a warning about potential stack overflow in
> "Finn" == Finn Thain writes:
Finn> This patch series is based on the one submitted recently by Ondrej
Finn> Zary. This version has a different irq probing fix for HP C2502
Finn> boards and a more comprehensive patch to change the default irq
Finn> parameter.
Applied to 4.10/scsi-queue.
-
Hi Linus,
Please pull three important fixes for the parisc architecture for v4.9 from
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.9-5
Dave provided two patches: One which purges the TLB before setting a PTE entry
and a second one which drops unnecessary TLB f
In some configurations, gcc cannot trace the state of variables
across a spin_unlock() barrier, leading to a warning about
correct code:
xgene_enet_main.c: In function 'xgene_enet_start_xmit':
../../../phy/mdio-xgene.h:112:14: error: 'mss_index' may be used uninitialized
in this function [-Werror
On Wednesday 23 November 2016 09:12 AM, Tomi Valkeinen wrote:
On 23/11/16 10:52, Greg Kroah-Hartman wrote:
On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
Hi,
Since the fbdev framework is in maintenance mode and all new display drivers
should be made with the DRM framework, rem
Usage llist_del_first needs lock protection, however the table in the
comments of llist.h show a '-'. Correct this, and also add better
comments on top.
Cc: Huang Ying
Cc: Ingo Molnar
Cc: Will Deacon
Cc: Paul McKenney
Signed-off-by: Joel Fernandes
---
include/linux/llist.h | 19 ++---
On Thu 2016-12-08 10:18:13, Thomas Gleixner wrote:
> On Wed, 7 Dec 2016, Pavel Machek wrote:
> > On Wed 2016-12-07 12:46:12, Thomas Gleixner wrote:
> > > On Tue, 6 Dec 2016, Pavel Machek wrote:
> > > > > From: Len Brown
> > > > >
> > > > > Upon removal of the i7300_idle driver, the idle_notifer i
On Thu, Dec 8, 2016 at 10:10 AM, Mauro Carvalho Chehab
wrote:
> Em Wed, 7 Dec 2016 12:39:24 -0700
> Jonathan Corbet escreveu:
>
>> On Wed, 7 Dec 2016 16:42:58 +0100
>> Daniel Vetter wrote:
>>
>> > We already had a super-short blurb, but worth extending it I think:
>> > We're still pretty far aw
On 12/05, Kuninori Morimoto wrote:
>
> Hi Stephen
>
> This is v5 of "clkdev: add devm_of_clk_get()", but new series.
> I hope my understanding was correct with your idea.
Yes this looks good. Given that we're so close to the merge
window, perhaps I should just merge the first patch into clk-next
On 12/05, Kuninori Morimoto wrote:
> diff --git a/sound/soc/generic/simple-card-utils.c
> b/sound/soc/generic/simple-card-utils.c
> index cf02625..4924575 100644
> --- a/sound/soc/generic/simple-card-utils.c
> +++ b/sound/soc/generic/simple-card-utils.c
> @@ -98,7 +98,8 @@ int asoc_simple_card_par
On 12/05, Kuninori Morimoto wrote:
> From: Kuninori Morimoto
>
> Current simple-card is supporting this style for clocks
>
> sound {
> ...
> simple-audio-card,cpu {
> sound-dai = <&xxx>;
> clocks = <&cpu_clock>;
>
Hi,
On 08.12.2016 22:54, Pavel Machek wrote:
> On Thu 2016-12-08 21:32:12, Lino Sanfilippo wrote:
>> Hi,
>>
>> On 08.12.2016 00:15, Francois Romieu wrote:
>> > Lino Sanfilippo :
>> >> The driver uses a private lock for synchronization between the xmit
>> >> function and the xmit completion handl
On 12/8/2016 1:11 PM, Grygorii Strashko wrote:
From: Murali Karicheri
Fix the pa clock to point to the clkpa which has clock rate of 1/3 of PA
PLL clock and add clock names.
Signed-off-by: Murali Karicheri
Signed-off-by: Grygorii Strashko
---
Acked-by: Santosh Shilimkar
Hi Arnd,
Can you
On Tuesday 06 December 2016 10:51 AM, Greg Kroah-Hartman wrote:
On Fri, Dec 02, 2016 at 04:23:55PM +, Colin King wrote:
From: Colin Ian King
A previous fix of a memory leak now prints the string 'name'
that was previously free'd. Fix this by free'ing the string
at the end of the function
On 12/06/2016 07:57 PM, Jie Deng wrote:
> This patch adds phy-mode support for Synopsys XLGMAC
The functional changes look good, but I would like to see some
description of what the XL part stands for here.
While you are modifying this, do you also mind submitting a Device Tree
specification chan
On Thu 2016-12-08 23:12:10, Lino Sanfilippo wrote:
> Hi,
>
> On 08.12.2016 22:54, Pavel Machek wrote:
> > On Thu 2016-12-08 21:32:12, Lino Sanfilippo wrote:
> >> Hi,
> >>
> >> On 08.12.2016 00:15, Francois Romieu wrote:
> >> > Lino Sanfilippo :
> >> >> The driver uses a private lock for synchron
Hi David,
On Thu, Dec 8, 2016 at 1:37 AM, David Miller wrote:
> You really have to land the IP header on a proper 4 byte boundary.
>
> I would suggest pushing 3 dummy garbage bytes of padding at the front
> or the end of your header.
Are you sure 3 bytes to get 4 byte alignment is really the bes
On Saturday 26 November 2016 11:02 AM, Greg Kroah-Hartman wrote:
On Sat, Nov 26, 2016 at 09:07:42AM +, Sudip Mukherjee wrote:
The driver was actually released with BSD license. It also gained GPL
when it was submitted to be included in the kernel.
Cc: Teddy Wang
Cc: gzhou1
Signed-off-by:
From: WingMan Kwok
This patch adds support of the cpts device found in the
gbe and 10gbe ethernet switches on the keystone 2 SoCs
(66AK2E/L/Hx, 66AK2Gx).
Cc: Richard Cochran
Signed-off-by: WingMan Kwok
Signed-off-by: Grygorii Strashko
---
changes in v2:
- dropped bindings changes
link on v1
On Thu, 8 Dec 2016, Ondrej Zary wrote:
> On Monday 05 December 2016 07:07:19 Finn Thain wrote:
> > This patch series is based on the one submitted recently by Ondrej
> > Zary.
> >
> > This version has a different irq probing fix for HP C2502 boards and a
> > more comprehensive patch to change t
Add support for sixteen-channel 12-bit resolution ADC and its functions,
which include general-purpose ADC readings, battery voltage measurement,
and die temperature measurement.
Signed-off-by: Ksenija Stanojevic
Reviewed-by: Jonathan Cameron
---
Changes in v11:
- use dev_get_drvdata instead de
Add 4-wire/5-wire touchscreen controller.
Signed-off-by: Ksenija Stanojevic
---
Changes in v11:
- use dev_get_drvdata instead dev_get_platdata
- use writel instead mxs_lradc_reg_* functions
Changes in v10:
- none
Changes in v9:
- none
Changes in v8:
- rebase onto 4.9-rc1
Changes in v7:
Add core files for low resolution analog-to-digital converter (mxs-lradc)
MFD driver.
Signed-off-by: Ksenija Stanojevic
---
Changes in v11:
- create static struct mfd_cells
- don't set platform data in mfd cells, set driver data instead
- remove mxs_lradc_reg_* functions, use writel function i
Since the driver has been split into mfd there is no reason for it to
stay, so remove it.
Signed-off-by: Ksenija Stanojevic
Acked-by: Jonathan Cameron
---
Changes in v11:
- none
Changes in v10:
- none
Changes in v9:
- none
Changes in v8:
- rebase onto 4.9-rc1
Changes in v7:
- none
Chan
The bindings, which are now used in MFD, need also to be
documented in the MFD binding document.
Signed-off-by: Ksenija Stanojevic
---
Changes in v11:
- none
Changes in v10:
- none
Changes in v9:
- format patch using -M option
Changes in v8:
- rebase onto 4.9-rc1
Changes in v7:
- add to
Split existing driver mxs-lradc into MFD with touchscreen and
IIO part.
Tested on I.MX28
Ksenija Stanojevic (5):
mfd: mxs-lradc: Add support for mxs-lradc MFD
iio: adc: mxs-lradc: Add support for adc driver
input: touchscreen: mxs-lradc: Add support for touchscreen
iio: adc: mxs-lradc: Re
501 - 600 of 857 matches
Mail list logo
