From: Laurent FERT
Fix offset for the second pass on the wrapped block when iterating over
memory in multi-block mode, otherwise wrong part of the block will get
copied.
Signed-off-by: Laurent FERT
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/msu.c | 2 +-
1 file changed,
STM framework should be able to handle multiple STM devices at a time,
each one with its own master allocation policy.
This patch changes dummy_stm driver to create multiple STM sinks to
help testing the framework.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/stm/dummy_stm.c | 57 +++
By convention, the name of the stm policy directory in configfs consists of
the device name to which it applies and the actual policy name, separated
by a dot. Now, some devices already have dots in their names that separate
name of the actual device from its instance identifier. Such devices will
It is possible to concurrently assign the same output (a character
device writer or an stm_source device) to different stm devices,
which sets off a strategically placed warning in stm_output_assign().
To avoid this, use a spinlock to serialize (un)assignments between
outputs and stm devices.
Sig
Em Sun, Feb 14, 2016 at 06:16:44PM -0800, Stephane Eranian escreveu:
> On Fri, Feb 12, 2016 at 12:43 PM, Arnaldo Carvalho de Melo
> wrote:
> >
> > Em Fri, Feb 12, 2016 at 12:32:53PM -0800, Stephane Eranian escreveu:
> > > On Thu, Feb 11, 2016 at 2:16 PM, Arnaldo Carvalho de Melo
> > > wrote:
> >
STM code takes references to the stm device and its module for the
duration of the character device's existence or the stm_source link.
Dropping these references is not well balanced everywhere, which may
lead to leaks.
This patch balances the acquisition and releasing of these two
references and
There is a window in stm_source_link_drop(), during which the source's
link may change before locks are acquired. When this happens, it throws
a warning, since this is not an expected scenario.
This patch handles the race in such a way that if the link appears to
have changed by the time we took t
STM device's link callback has the power to abort master/channel
assignment by returning a negative error code. Use this in dummy
stm device to optionally abort assigning certain channel IDs.
This is useful as fault injection into the stm class core, for
testing purposes.
Signed-off-by: Alexander
On 02/14/2016 03:22 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.97 release.
> There are 64 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
STM device's unlink callback is never actually called from anywhere in
the stm class code.
This patch adds calls to stm driver's unlink method after the unlinking
has succeeded.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/stm/core.c | 23 +++
include/linux/stm.h
According to the stm class interface, the packet callback should return
an error if it is asked to generate packets that it doesn't support.
When it succeeds, it should return number of bytes consumed from its
payload. Currently, for FLAG packet it mistakenly returns 1.
This patch addresses these
Most of the intel_th core supports multiple co-existing TH devices,
except for output device nodes, where intel_th device id is hardcoded
to be zero.
Fix this by fetching the actual intel_th device id from the parent
device's drvdata.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/inte
STM drivers provide a callback to generate/send individual STP packets;
it also tells the stm core how many bytes of payload it has consumed.
However, we would also need to use the negative space of this return
value to communicate errors that occur during the packet generation,
in which case the s
Heartbeat stm source may have multiple instances (for connecting to
different stm devices). Each instance will send a periodic test message
over its stm device when it is linked. This can be used for testing stm
class framework, stm device drivers or as a heartbeat over the stm link.
Signed-off-by
If an illegal attempt is made to unlink stm source device from an
stm device, the stm device's link spinlock mistakenly remains locked.
While this really shouldn't happen (there's a warning in place), the
locking should remain in order so that we can still recover from this
situation if it indeed d
Already during the subdevice initialization time, devices will need
to reference Intel TH controller descriptor structure.
This patch moves setting the drvdata from the pci glue to intel_th
core, before subdevices are populated.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/c
There's a commented-out function in the GTH driver that's a leftover
from previous versions of the driver, where we tried to inherit the
pre-existing configuration, which didn't prove to be a sound idea.
This patch removes the function. No functional changes.
Signed-off-by: Alexander Shishkin
--
Hi Greg,
These are the patches I have queued for the next merge window. Please
consider applying.
Alexander Shishkin (16):
intel_th: Depend on HAS_IOMEM
intel_th: gth: Remove commented-out code
intel_th: Update scratchpad bits according to enabled output activity
intel_th: sth: Sanitize p
This driver requires io memory to operate, so don't even consider it
for NO_IOMEM architectures.
Reported-by: Richard Weinberger
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwtracing/intel_t
Hello Greg,
On Mon, Feb 15, 2016 at 08:49:37AM -0800, Greg Kroah-Hartman wrote:
> On Mon, Feb 15, 2016 at 05:27:53PM +0100, Uwe Kleine-König wrote:
> > Greg, can you drop this patch, or do you need a proper changelog for a
> > revert? On top of that I'd then create a new patch which is more
> > co
On 02/15/2016 08:16 AM, Shuah Khan wrote:
> On 02/14/2016 03:20 PM, Greg Kroah-Hartman wrote:
>> -
>> NOTE: This is the last 4.3.y kernel to be released. After this one, it
>> is end-of-life, please move to 4.4.y at this point in time.
>> -
>>
>> Thi
From: Буди Романто, AreMa Inc
Signed-off-by: Буди Романто, AreMa Inc
---
drivers/media/pci/Kconfig | 2 +-
drivers/media/pci/Makefile | 2 +-
drivers/media/pci/ptx/Kconfig | 21 ++
drivers/media/pci/ptx/Makefile | 8 +
drivers/media/pci/ptx/pt3_pci.c| 509 ++
On Tue, 2016-02-16 at 00:25 +0800, kbuild test robot wrote:
> drivers/bluetooth/hci_mrvl.c:411:9-10: WARNING: return of 0/1 in
> function 'mrvl_fw_loaded' with return type bool
>
> Return statements in functions returning bool should use
> true/false instead of 1/0.
> Generated by: scripts/cocci
On 02/14/2016 03:20 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.2 release.
> There are 117 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On Mon, 15 Feb 2016, David Vrabel wrote:
> On 15/02/16 16:51, Stefano Stabellini wrote:
> > CC'ing a few others.
> >
> > On Fri, 12 Feb 2016, Arnd Bergmann wrote:
> >> The Xen framebuffer driver selects the xen keyboard driver, so the latter
> >> will be built-in if XEN_FBDEV_FRONTEND=y. However,
On Mon, Feb 15, 2016 at 06:04:15PM +0100, Dmitry Vyukov wrote:
> There is something wrong and I guess it is not actually working.
> Please post your config file so that I can double check. In
> particular, did you set "cover": false?
{
"http": "localhost:5",
"workdir": "root/g
On 02/14/2016 03:22 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.61 release.
> There are 76 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On Mon, Feb 15, 2016 at 03:17:55PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 15, 2016 at 02:36:43PM +0200, Joonas Lahtinen wrote:
> > Instead of implementing a custom locked reference counting, use lockref.
> >
> > Current implementation leads to a deadlock splat on Intel SKL platforms
> > when l
On 02/15/2016 08:08 PM, Bjørn Mork wrote:
> Ike Panhc writes:
>
>> There are complains on few ideapads that wireless is always hard
>> blocked but there is no physical radio switch. For now, we need
>> each user to report its dmi information and ignore hard blocks
>> on their ideapad. With more a
Rafael,
I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace
timers with utilization update callbacks' with next-20160215. An example
crash log and bisect results are attached below.
Please let me know if there is anything I can do to help tracking down
the proble
On 15/02/16 16:51, Stefano Stabellini wrote:
> CC'ing a few others.
>
> On Fri, 12 Feb 2016, Arnd Bergmann wrote:
>> The Xen framebuffer driver selects the xen keyboard driver, so the latter
>> will be built-in if XEN_FBDEV_FRONTEND=y. However, when CONFIG_INPUT
>> is a loadable module, this confi
On Mon, Feb 15, 2016 at 5:52 PM, Peter Zijlstra wrote:
> On Mon, Feb 15, 2016 at 05:38:36PM +0100, Dmitry Vyukov wrote:
>> Just to compensate the pain, here is what I've just got when
>> re-enabled perf in my config :)
>>
>> 2016/02/15 16:52:18 qemu-15: saving crash 'WARNING: CPU: 0 PID: 18465
>>
Hi Ganapathi,
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on v4.5-rc4 next-20160215]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Amitkumar-Karwar/Bluetooth
On Mon, Feb 15, 2016 at 05:54:51PM +0100, Dmitry Vyukov wrote:
> > OK, now I have syz-fuzzer at ~950% CPU time and a gazillion syz-executor
> > tasks running.
>
> If you want more or less, it is controlled by the "procs": 160 config
> parameter.
I've got 2*10 cores, each with SMT enabled for 40
On Mon, Feb 15, 2016 at 07:41:19AM -0800, Guenter Roeck wrote:
> On 02/15/2016 02:59 AM, Uwe Kleine-König wrote:
> >Hello Guenter,
> >
> >On Sun, Feb 14, 2016 at 08:50:10AM -0800, Guenter Roeck wrote:
> >>Uwe,
> >>
> >>Your patch 'driver-core: platform: probe of-devices only using list of
> >>compa
On Mon, Feb 15, 2016 at 5:41 PM, Peter Zijlstra wrote:
> On Mon, Feb 15, 2016 at 05:35:51PM +0100, Dmitry Vyukov wrote:
>> > root@ivb-ep:~/gopath/src/github.com/google/syzkaller# bin/syz-manager
>> > -config perf.cfg -v 1 -debug
>> > 2016/02/15 17:12:50 bad config syzkaller param: can't find bin/
On Mon, Feb 15, 2016 at 05:38:36PM +0100, Dmitry Vyukov wrote:
> Just to compensate the pain, here is what I've just got when
> re-enabled perf in my config :)
>
> 2016/02/15 16:52:18 qemu-15: saving crash 'WARNING: CPU: 0 PID: 18465
> at kernel/events/core.c:2743 ctx_sched_in+0x255/0x17f0()' to
>
CC'ing a few others.
On Fri, 12 Feb 2016, Arnd Bergmann wrote:
> The Xen framebuffer driver selects the xen keyboard driver, so the latter
> will be built-in if XEN_FBDEV_FRONTEND=y. However, when CONFIG_INPUT
> is a loadable module, this configuration cannot work. On mainline kernels,
> the symbo
On Mon, Feb 15, 2016 at 10:31:34AM -0600, Josh Poimboeuf wrote:
> On Fri, Feb 12, 2016 at 09:10:11PM +0100, Peter Zijlstra wrote:
> > On Fri, Feb 12, 2016 at 12:32:06PM -0600, Josh Poimboeuf wrote:
> > > What I actually see in the listing is:
> > >
> > > decl__percpu_prefix:__preempt_count
>
On Mon, Feb 15, 2016 at 05:27:53PM +0100, Uwe Kleine-König wrote:
> Hello Russell,
>
> On Mon, Feb 15, 2016 at 02:43:44PM +, Russell King - ARM Linux wrote:
> > On Mon, Feb 15, 2016 at 01:11:49PM +, Robin Murphy wrote:
> > > FWIW the PL180 on my Juno still works fine with this patch picked
On 15-02-16, 16:42, Jon Hunter wrote:
>
> On 15/02/16 16:26, Viresh Kumar wrote:
> > We are currently required to do two checks for regulator pointer:
> > IS_ERR() and IS_NULL().
> >
> > And multiple instances are reported, about both of these not being used
> > consistently and so resulting in c
On Mon, Feb 15, 2016 at 06:08:07PM +0200, Alexander Shishkin wrote:
> Hi Greg,
>
> These are patches I have queued for the next merge window. Please
> consider pulling.
>
> The following changes since commit 1b79dff672ca09a5461cc1d46ad81c62137841c5:
>
> Merge 4.5-rc4 into char-misc-next (2016-
On 15/02/16 16:26, Viresh Kumar wrote:
> We are currently required to do two checks for regulator pointer:
> IS_ERR() and IS_NULL().
>
> And multiple instances are reported, about both of these not being used
> consistently and so resulting in crashes.
>
> Fix that by initializing regulator poin
On Mon, Feb 15, 2016 at 05:35:51PM +0100, Dmitry Vyukov wrote:
> > root@ivb-ep:~/gopath/src/github.com/google/syzkaller# bin/syz-manager
> > -config perf.cfg -v 1 -debug
> > 2016/02/15 17:12:50 bad config syzkaller param: can't find bin/syz-execprog
> >
> > And its right, no such thing as bin/syz-
On Mon, Feb 15, 2016 at 04:36:55PM +, Daniel Stone wrote:
> Russell,
>
> On 12 February 2016 at 00:57, Akshay Bhat wrote:
> > Daniel Stone collabora.com> writes:
> >> Fixes: ffc30b74fd6d01588bd3fdebc3b1acc0857e6fc8
> >> Signed-off-by: Daniel Stone collabora.com>
> >
> > Tested-by: Akshay Bh
A crash has been observed when assigning penalty on x86 systems.
It looks like this problem happens on x86 platforms with IOAPIC and an SCI
interrupt override in the ACPI table with interrupt number greater than
16. (22 in this example)
The bug has been introduced by "ACPI, PCI, irq: remove inter
On Sat, 13 Feb 2016 01:15:10 +0200
"Kirill A. Shutemov" wrote:
>
> I'm trying to wrap my head around the issue and I don't think missing
> serialization with gup_fast is the cause -- we just don't need it
> anymore.
>
> Previously, __split_huge_page_splitting() required serialization against
>
On Mon, Feb 08, 2016 at 09:50:03AM +, Matt Fleming wrote:
> On Sun, 07 Feb, at 09:43:31PM, Greg KH wrote:
> > On Fri, Jan 29, 2016 at 12:39:54PM +0800, Kweh, Hock Leong wrote:
> > > From: "Kweh, Hock Leong"
> > >
> > > Introducing a kernel module to expose capsule loader interface
> > > (misc
On Mon, 15 Feb 2016, Kirill A. Shutemov wrote:
> > [ 59.851421] list_del corruption. next->prev should be 6e1eb000,
> > but was 0400
>
> This kinda interesting: 0x400 is TAIL_MAPPING.. Hm..
>
> Could you check if you see the problem on commit 1c290f642101 and its
> immediat
On Mon, Feb 15, 2016 at 5:35 PM, Dmitry Vyukov wrote:
> On Mon, Feb 15, 2016 at 5:29 PM, Peter Zijlstra wrote:
>> On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
>>> There is a way to run it without coverage on a local machine.
>>>
>>> First, you need to setup Go toolchain: downloa
Current implementation of __delay() function uses so-called
zero-delay loops. And the only condition to exit that loop is
LP_COUNT (loop count register) = 1 (but not 0 as it might be easily
imagined).
So if our calculation of "loops" gives 0 (and that is pretty possible
given result of multiplicat
Russell,
On 12 February 2016 at 00:57, Akshay Bhat wrote:
> Daniel Stone collabora.com> writes:
>> Fixes: ffc30b74fd6d01588bd3fdebc3b1acc0857e6fc8
>> Signed-off-by: Daniel Stone collabora.com>
>
> Tested-by: Akshay Bhat
>
> Tested on imx6 processor based board where re-probe was broken after a
Hi Archit,
On 11 February 2016 at 09:35, Archit Taneja wrote:
> component_master_add_with_match can fail if the master's bind op doesn't
> go through successfully. In such a scenario, all the components in the
> master's match array have their 'master' pointer set to the given master.
> These poi
On Mon, Feb 15, 2016 at 5:29 PM, Peter Zijlstra wrote:
> On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
>> There is a way to run it without coverage on a local machine.
>>
>> First, you need to setup Go toolchain: download latest Go distribution
>> from https://golang.org/dl:
>> ht
On Thu, Feb 11, 2016 at 10:23:18PM +0100, Robert Jarzmik wrote:
> @@ -1399,13 +1405,17 @@ static int pxad_probe(struct platform_device *op)
> return PTR_ERR(pdev->base);
>
> of_id = of_match_device(pxad_dt_ids, &op->dev);
> - if (of_id)
> + if (of_id) {
>
On Fri, Feb 12, 2016 at 09:10:11PM +0100, Peter Zijlstra wrote:
> On Fri, Feb 12, 2016 at 12:32:06PM -0600, Josh Poimboeuf wrote:
> > What I actually see in the listing is:
> >
> > decl__percpu_prefix:__preempt_count
> > je 1f:
> >
> > 1:
> > call___preempt_sched
On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
> There is a way to run it without coverage on a local machine.
>
> First, you need to setup Go toolchain: download latest Go distribution
> from https://golang.org/dl:
> https://storage.googleapis.com/golang/go1.5.3.linux-amd64.tar.gz
On 02/14/2016 10:09 PM, Balbir Singh wrote:
>> > For protection keys, we need to understand whether protections
>> > should be enforced in software or not. In general, we enforce
>> > protections when working on our own task, but not when on others.
>> > We call these "current" and "remote" operat
On Mon, Feb 15, 2016 at 5:17 PM, Peter Zijlstra wrote:
> On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
>> On Thu, Jan 14, 2016 at 10:35 AM, Peter Zijlstra
>> wrote:
>> > On Tue, Jan 12, 2016 at 12:26:27PM +0100, Dmitry Vyukov wrote:
>> >> What do you think if we work on making s
Hello Russell,
On Mon, Feb 15, 2016 at 02:43:44PM +, Russell King - ARM Linux wrote:
> On Mon, Feb 15, 2016 at 01:11:49PM +, Robin Murphy wrote:
> > FWIW the PL180 on my Juno still works fine with this patch picked on top of
> > -rc3, so the issue would seem to be something else - From a q
We are currently required to do two checks for regulator pointer:
IS_ERR() and IS_NULL().
And multiple instances are reported, about both of these not being used
consistently and so resulting in crashes.
Fix that by initializing regulator pointer with an error value and
checking it only against a
Hi Ganapathi,
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on v4.5-rc4 next-20160215]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Amitkumar-Karwar/Bluetooth
On Sun, 2016-02-14 at 16:39 -0800, Greg Kroah-Hartman wrote:
> On Fri, Feb 12, 2016 at 07:05:53PM +0100, Colin Vidal wrote:
> > Signed-off-by: Colin Vidal
> > ---
> > drivers/staging/rtl8188eu/core/rtw_iol.c | 10 +++---
> > 1 file changed, 3 insertions(+), 7 deletions(-)
> >
> > diff --git
drivers/bluetooth/hci_mrvl.c:411:9-10: WARNING: return of 0/1 in function
'mrvl_fw_loaded' with return type bool
Return statements in functions returning bool should use
true/false instead of 1/0.
Generated by: scripts/coccinelle/misc/boolreturn.cocci
CC: Ganapathi Bhat
Signed-off-by: Fenggua
On Mon, 15 Feb 2016 10:18:24 +
Juri Lelli wrote:
> > Signed-off-by: Steven Rostedt
> > ---
> > diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> > index cd64c979d0e1..1dd180cda574 100644
> > --- a/kernel/sched/deadline.c
> > +++ b/kernel/sched/deadline.c
> > @@ -735,7 +735,7
On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
> On Thu, Jan 14, 2016 at 10:35 AM, Peter Zijlstra wrote:
> > On Tue, Jan 12, 2016 at 12:26:27PM +0100, Dmitry Vyukov wrote:
> >> What do you think if we work on making syzkaller work for you locally?
> >
> > There's no easy way to do
On Monday 15 February 2016 09:19 PM, Nishanth Menon wrote:
On 02/14/2016 10:27 PM, Keerthy wrote:
On Saturday 13 February 2016 04:11 AM, Tony Lindgren wrote:
* Nishanth Menon [160212 14:32]:
On Fri, Feb 12, 2016 at 4:23 PM, Tony Lindgren wrote:
* Nishanth Menon [160209 14:17]:
On 02/0
On Monday 15 February 2016 14:51:13 Krzysztof Hałasa wrote:
> Arnd Bergmann writes:
>
> > I consider the use of __raw_* accessors a bug, I don't think we should
> > ever do that because it hides how the hardware actually works, it doesn't
> > work with spinlocks, and it can lead to the compiler s
On Mon, Feb 15, 2016 at 07:41:19AM -0800, Guenter Roeck wrote:
> On 02/15/2016 02:59 AM, Uwe Kleine-König wrote:
> >Hello Guenter,
> >
> >On Sun, Feb 14, 2016 at 08:50:10AM -0800, Guenter Roeck wrote:
> >>Uwe,
> >>
> >>Your patch 'driver-core: platform: probe of-devices only using list of
> >>compa
On Thu, Feb 11, 2016 at 06:39:46PM +, Marc Zyngier wrote:
> Add a new ARM64_HAS_VIRT_HOST_EXTN features to indicate that the
> CPU has the ARMv8.1 VHE capability.
>
> This will be used to trigger kernel patching in KVM.
>
> Acked-by: Christoffer Dall
> Acked-by: Catalin Marinas
> Signed-off
> -Original Message-
> From: Jiri Slaby [mailto:jsl...@suse.cz]
> Sent: Monday, February 15, 2016 17:20
> To: Shuah Khan ; sta...@vger.kernel.org
> Cc: li...@roeck-us.net; shuah...@samsung.com; linux-kernel@vger.kernel.org;
> Winkler, Tomas
> Subject: Re: [PATCH 3.12 00/64] 3.12.54-stabl
On Mon, 15 Feb 2016, Peter Zijlstra wrote:
> Not yet :/ I managed to reproduce a lot of fail with Vince's perf-fuzzer
> and some stress test scripts Ingo had.
I was glad to see the fixes go by, since a lot of the
syzkaller reports are very similar to open bugs I have with perf_fuzzer.
I have to
Hi Greg,
These are patches I have queued for the next merge window. Please
consider pulling.
The following changes since commit 1b79dff672ca09a5461cc1d46ad81c62137841c5:
Merge 4.5-rc4 into char-misc-next (2016-02-14 14:25:59 -0800)
are available in the git repository at:
https://github.com
On Mon, 15 Feb 2016 12:04:50 +0900
js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> CMA allocation should be guaranteed to succeed by definition, but,
> unfortunately, it would be failed sometimes. It is hard to track down
> the problem, because it is related to page reference manipulation and
>
On (02/15/16 09:43), kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux
> Sergey-Senozhatsky/printk-move-can_use_console-out-of-console_trylock_for_printk/20160213-024210
> commit af097cab1b878d5be746be8bcaa9a79986716c41 ("printk: set may_schedule
Use early console instead of earlyprintk which is supposed to use for
very early debugging (DEBUG_LL).
Signed-off-by: Michal Simek
---
arch/arm/boot/dts/zynq-parallella.dts | 2 +-
arch/arm/boot/dts/zynq-zc702.dts | 2 +-
arch/arm/boot/dts/zynq-zc706.dts | 2 +-
arch/arm/boot/dts/zynq
The patch
"ARM: 8432/1: move VMALLOC_END from 0xff00 to 0xff80"
(sha1: 6ff0966052c46efb53980b8a1add2e7b49c9f560)
has moved also start of VMALLOC area because size didn't change.
That's why origin location of vmalloc was
vmalloc : 0xf000 - 0xff00 ( 240 MB)
and now is
vmalloc
Support early console setup via DT for all listed compatible strings.
Signed-off-by: Michal Simek
---
drivers/tty/serial/xilinx_uartps.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/tty/serial/xilinx_uartps.c
b/drivers/tty/serial/xilinx_uartps.c
index 009e0dbc12d2..6f56577668
On Mon, Feb 15, 2016 at 04:46:31PM +0100, Arnd Bergmann wrote:
> -#if CONFIG_ARCH_NR_GPIO > 0
> -#define ARCH_NR_GPIOS CONFIG_ARCH_NR_GPIO
> -#endif
...
> diff --git a/include/asm-generic/gpio.h b/include/asm-generic/gpio.h
> index 40ec1433f05d..2d04b321db13 100644
> --- a/include/asm-generic/gpio.
13.02.2016 01:23, Ville Syrjälä wrote:
- Do you have another monitor to try?
- Do you have another cable to try?
More on this.
Computer DVI —— old DVI-HDMI cable —— old monitor HDMI == not working
Computer DVI —— another DVI-HDMI cable —— old monitor HDMI == not
working
Computer DVI —— DVI-D
On 02/15/2016 04:46 PM, Arnd Bergmann wrote:
> +static inline __deprecated int irq_to_gpio(unsigned int irq)
> +{
> + /* this has clearly not worked for a long time */
> + return -EINVAL;
> +}
> +
> #define IRQ_TO_BIT(irq) BIT(irq_to_gpio(irq) & 0x1f)
The issue seems to be a fallout from
On Mon, Feb 15, 2016 at 9:30 AM, Fabio Estevam wrote:
> [Sorry for the top post, can't reply properly from this Inbox]
>
> Could you please try applying this commit from linux-next?
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/base/regmap/regcache.c?id=3245d460
On 02/14/2016 10:27 PM, Keerthy wrote:
>
>
> On Saturday 13 February 2016 04:11 AM, Tony Lindgren wrote:
>> * Nishanth Menon [160212 14:32]:
>>> On Fri, Feb 12, 2016 at 4:23 PM, Tony Lindgren wrote:
* Nishanth Menon [160209 14:17]:
> On 02/09/2016 04:09 PM, Eduardo Valentin wrote:
>>>
On 02/14/2016 02:20 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.2 release.
There are 117 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On 02/14/2016 02:20 PM, Greg Kroah-Hartman wrote:
-
NOTE: This is the last 4.3.y kernel to be released. After this one, it
is end-of-life, please move to 4.4.y at this point in time.
-
This is the start of the stable review cycle for the 4.3.6 rel
The ep93xx goes through its own back-and-forth dance every time
it wants to know the gpio number for an irq line, when it really
just hardcodes a fixed offset in ep93xx_gpio_to_irq().
This removes the pointless macro and replaces the conversion inside
of the driver with simple add/subtract operati
On Mon, Feb 15, 2016 at 4:38 PM, Peter Zijlstra wrote:
> On Mon, Feb 15, 2016 at 04:04:36PM +0100, Dmitry Vyukov wrote:
>> Peter, I want to check status of these perf crashes. I see that you
>> landed a bunch of patches. But I still see perf-related crashes while
>> running syzkaller.
>
> Bugger :
I noticed that arch/arm/include/asm/gpio.h can almost be removed,
after we have already removed the file for most other architectures
now.
When I removed it, I ran into problems with irq_to_gpio(), which
we had already killed off in ARM, but it survived (barely) in the
global headers. this kills i
The ARM version of asm/gpio.h basically just contains the same definitions
as the gpiolib version, with the exception of ARCH_NR_GPIOS.
This adds the option for overriding the constant through Kconfig to
the architecture-independent header, and removes the ARM version at
the same time.
This patch
gpiolib has removed the irq_to_gpio() API several years ago,
but the global header still provided a non-working stub.
Apparently one new user has shown up in arch/mips, so this patch
moves the broken definition to where it is used, ensuring that
we get new users but not changing the current behavi
The ks8695 gpio driver has its own copy of the irq_to_gpio()
function. This is completely unused in the mainline kernel
after we converted all remaining users several years ago,
so we can remove the definition as well.
Signed-off-by: Arnd Bergmann
---
drivers/gpio/gpio-ks8695.c | 12
On 02/14/2016 02:22 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.61 release.
There are 76 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 02/14/2016 02:22 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.97 release.
There are 64 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
Octeon sets the default irq affinity to value 1 in the early arch init
code, so by default all irqs get registered with their affinity set to
core 0.
When setting one CPU ofline, octeon_irq_cpu_offline_ciu() calls
irq_set_affinity_locked(), but this function sets the IRQD_AFFINITY_SET bit
in the i
Julian Calaby writes:
> Hi Geliang,
>
> On Sun, Feb 7, 2016 at 2:30 PM, Geliang Tang wrote:
>> This patch cleans whitespaces and blank lines surrounding
>> list_for_each_entry*().
>
> It does a lot more than this, including:
> - Removing some unnecessary brackets
> - Whitespace changes well awa
On Mon, Feb 15, 2016 at 04:42:35PM +0200, Ville Syrjälä wrote:
> On Mon, Feb 15, 2016 at 10:55:33AM +0200, Oleksandr Natalenko wrote:
> > 13.02.2016 01:23, Ville Syrjälä wrote:
> > > - Do you have another monitor to try?
> > > - Do you have another cable to try?
> >
> > More on this.
> >
> > Comp
On Mon, Feb 15, 2016 at 04:04:36PM +0100, Dmitry Vyukov wrote:
> Peter, I want to check status of these perf crashes. I see that you
> landed a bunch of patches. But I still see perf-related crashes while
> running syzkaller.
Bugger :-)
> Are there any existing bugs left that you know
> about?
On 02/15/2016 02:59 AM, Uwe Kleine-König wrote:
Hello Guenter,
On Sun, Feb 14, 2016 at 08:50:10AM -0800, Guenter Roeck wrote:
Uwe,
Your patch 'driver-core: platform: probe of-devices only using list of
compatibles' causes the following qemu tests to crash in -next.
arm:vexpress-a9:vexpress_de
On Sat, Feb 13, 2016 at 12:58:31PM +0100, Sebastian Ott wrote:
>
> On Sat, 13 Feb 2016, Kirill A. Shutemov wrote:
> > Could you check if revert of fecffad25458 helps?
>
> I reverted fecffad25458 on top of 721675fcf277cf - it oopsed with:
>
> ¢ 1851.721062! Unable to handle kernel pointer derefer
On Mon, Feb 15, 2016 at 1:55 PM, Laurent Pinchart
wrote:
>> --- 0001/drivers/pinctrl/sh-pfc/Makefile
>> +++ work/drivers/pinctrl/sh-pfc/Makefile 2016-02-15 19:56:50.720513000
> +0900
>> @@ -1,11 +1,8 @@
>> sh-pfc-objs = core.o pinctrl.o
>> -ifeq ($(CONFIG_GPIO_SH_PFC),y)
>>
501 - 600 of 925 matches
Mail list logo
