On 03/21/2016 04:22 PM, Jeff Moyer wrote:
>> Just propagating some errors defintively seems odd.
>
> Not really. read, write, etc only expect a subset of errnos to be
> returned. The goal was not to leak kernel-internal or unexpected error
> numbers to userspace, and I didn't think I would be ab
On 04/21/2016 10:13 AM, Jiri Slaby wrote:
> On 04/21/2016, 03:54 PM, Sasha Levin wrote:
>> On 04/21/2016 08:39 AM, Greg KH wrote:
>>> On Thu, Apr 21, 2016 at 02:05:41PM +0200, Jiri Slaby wrote:
> On 04/21/2016, 01:59 PM, Jiri Slaby wrote:
> (CVE-2016-2085) 613317b EVM: Use crypto_memneq
On Thu, 21 Apr 2016 16:17:29 +0200
David Hildenbrand wrote:
> > Commit c896939f7cff ("KVM: use heuristic for fast VCPU lookup by id") added
> > a return path that prevents vcpu ids to exceed KVM_MAX_VCPUS. This is a
> > problem for powerpc where vcpu ids can grow up to 8*KVM_MAX_VCPUS.
> >
> > T
On Mon, Apr 18, 2016 at 01:26:11PM +0200, Enric Balletbo i Serra wrote:
> The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
> designed for portable devices.
>
> Signed-off-by: Enric Balletbo i Serra
> Cc: Rob Herring
> ---
> Changes since v3:
> - Model v10 as regulator (d
Hi Jose,
On Thu, 2016-04-21 at 14:10 +0100, Jose Abreu wrote:
> Hi Alexey,
>
>
> On 21-04-2016 13:18, Alexey Brodkin wrote:
> >
> > Hi Jose,
> >
> > On Thu, 2016-04-21 at 10:51 +0100, Jose Abreu wrote:
> > >
> > > Hi Alexey,
> > >
> > Ok reference clock will change.
> > But I may guess we'll
* Mugunthan V N [160421 04:19]:
> On Thursday 21 April 2016 03:43 PM, Grygorii Strashko wrote:
> > Add record for TI Ethernet Switch Driver CPSW/CPDMA/MDIO HW
> > (am33/am43/am57/dr7/davinci) to ensure that related patches
> > will go through dedicated linux-omap list.
> >
> > Also add Mugunthan
On Thu, Apr 21, 2016 at 10:27:46AM -0400, Sasha Levin wrote:
> This means that missing CVE fixes are quite common with stable trees?
Until someone reports they are missing :-)
Willy
On 21/04/2016 at 15:12:41 +0200, Wadim Egorov wrote :
> The RK808 and RK818 PMICs are using a similar register map.
> We can reuse the rtc driver for the RK818 PMIC. So let's add
> the RK818 in the Kconfig description.
>
> Signed-off-by: Wadim Egorov
Acked-by: Alexandre Belloni
> ---
> drivers
On Mon, Apr 18, 2016 at 05:23:49AM -0700, Amitkumar Karwar wrote:
> From: Xinming Hu
>
> Add device tree binding documentation for MARVELL's bluetooth sdio
> (sd8897 and sd8997) chip.
>
> Signed-off-by: Xinming Hu
> Signed-off-by: Amitkumar Karwar
> ---
> Listing changelist for both 1/2 and 2/
Hi,
On 21/04/16 03:02, J.D. Schroeder wrote:
> From: "Lodes, Jim"
>
> The DDC scl high and low times were set to the minimum values
> from the i2c specification, but the i2c specification takes into
> account the rise time and fall time to calculate the frequency.
> To pass HDMI certification DD
[adding Seung-Woo Kim to cc]
Hello Krzysztof,
On 03/28/2016 09:25 PM, Krzysztof Kozlowski wrote:
> On 29.03.2016 00:15, Javier Martinez Canillas wrote:
>> Tobias mentioned on IRC that the exynos4-is driver conflicts with the
>> Exynos DRM driver since both exynos_drm_fimc and exynos-fimc-is use
>
On Mon, Apr 18, 2016 at 10:00:42AM +0800, Wanpeng Li wrote:
> > H is for hierarchy. That counts the total of runnable tasks in the
> > entire child hierarchy. Nr_running is the number of se entities in
> > the current tree.
>
> So I think we should at least change cfs_rq->nr_running to
> cfs->h_n
Hi,
On 21/04/16 16:48, J.D. Schroeder wrote:
> From: "Lodes, Jim"
>
> The AVI infoframe R0-R3 in the 2nd data byte represents the
> Active Format Aspect Ratio. It is four bits long not two bits.
> This fixes that mask used to extract the bits before writing the
> bits to the hardware registers.
When pn533_recv_frame is called with skb = NULL and cmd->status = 0, set
cmd->status to an error code.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/pn533.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/nfc/pn533/pn533.c b/drivers/nfc/pn533/pn533.c
index ae13277..44bc5e0
Correctly call nfc_set_parent_dev before nfc_register_device. Otherwise the
driver will oops when being removed.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/i2c.c | 3 ++-
drivers/nfc/pn533/pn533.c | 4 +++-
drivers/nfc/pn533/pn533.h | 3 ++-
drivers/nfc/pn533/usb.c | 3 +--
4 fil
The requested irq needs to be freed when removing the driver, otherwise a
following driver load fails to request the irq.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/i2c.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/nfc/pn533/i2c.c b/drivers/nfc/pn533/i2c.c
index 967
When pn533_recv_frame is called from within abort_command context the current
dev->cmd is not guaranteed to be set.
Additionally on receiving an error status we can omit frame checking and
simply schedule the workquueue.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/pn533.c | 8 +++
Hello Samuel,
This patchset fixes some major bugs in the pn533 drivers (usb and i2c) and
improves performance of the PN532 chip by increasing its clock speed.
Best Regards
Michael
Michael Thalmeier (11):
NFC: pn533: i2c: free irq on driver remove
NFC: pn533: fix order of initialization
NFC
When multiple receive frames need to be put together in pn533_build_response
we need to use nfc_alloc_recv_skb instead of the normal alloc_skb. Otherwise
the nfc core causes an skb error when it tries to push the status byte in
front of the data.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/
When a command gets aborted the pn533 core does not need any RX frames that
may be received until a new frame is sent.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/i2c.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/nfc/pn533/i2c.c b/drive
Handle return codes for stopped polling operations better to reduce logging
activity.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/pn533.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/nfc/pn533/pn533.c b/drivers/nfc/pn533/pn533.c
index d1cc70a..c0
When a poll ist stopped we need to kill the out_urb request too before
starting a new request.
Additionally check if cmd is set in pn533_recv_ack befor accessing its struct
members.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/usb.c | 12 +---
1 file changed, 9 insertions(+),
We need to reset the poll modulation list before calling nfc_targets_found
because otherwise it is possible that the application is scheduled to run
before the modulation list is cleared and gets an error "Cannot activate
target while polling" upon calling activate_target.
Signed-off-by: Michael T
Default clock frequency of PN532 is 6.78 MHz. Increase the frequency to 27.12
MHz to increase throughput.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/pn533.c | 70 +++
drivers/nfc/pn533/pn533.h | 2 ++
2 files changed, 72 insertions(+)
dif
On Wed, Apr 20, 2016 at 01:55:42PM -0700, Kees Cook wrote:
...
> diff --git a/arch/x86/boot/header.S b/arch/x86/boot/header.S
> index 6236b9ec4b76..6b8f8728c1fa 100644
> --- a/arch/x86/boot/header.S
> +++ b/arch/x86/boot/header.S
> @@ -440,6 +440,93 @@ setup_data: .quad 0
Make sure cmd is set before a frame is passed to the transport layer for
sending. In addition pn533_send_async_complete checks if cmd is set before
accessing its members.
Signed-off-by: Michael Thalmeier
---
drivers/nfc/pn533/pn533.c | 54 +--
1 file c
On Thu, Apr 21, 2016 at 02:37:11PM +0200, Borislav Petkov wrote:
> On Thu, Apr 21, 2016 at 10:39:48AM +0200, Marc Haber wrote:
> > Currently, I cannot explain how this has happened, I must have flagged
> > an actually good kernel as bad from my understanding of git bisect.
> >
> > Can you give adv
On Thu, 2016-04-21 at 15:10 +0200, Peter Zijlstra wrote:
> On Wed, Apr 20, 2016 at 10:21:14PM +0200, Rafael J. Wysocki wrote:
> > You can send both and they both can go in via tip as far as I'm
> > concerned.
>
> OK, thanks!
>
> Srinivas I've munged the rapl patch to match the new style, so no
>
On Tue, Apr 19, 2016 at 1:11 AM, Al Stone wrote:
>
> When CPPC is being used by ACPI on arm64, user space tools such as
> cpupower report CPU frequency values from sysfs that are incorrect.
>
> What the driver was doing was reporting the values given by ACPI tables
> in whatever scale was used
Hi Linus,
Please pull these two fbdev fixes for 4.6.
Tomi
The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9:
Linux 4.6-rc4 (2016-04-17 19:13:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git
tags/fbd
On 04/21/2016, 03:53 PM, Sasha Levin wrote:
>> Pardom my ignorance, how can you actually be sure?
>
> I'm not, same way you can't be sure about your stable patch selection either.
I repeat I am not doing any selection.
Patches are not included iff they do not apply and I am not confident
enough
lockdep reports the following circular locking dependency.
==
INFO: possible circular locking dependency detected ]
4.6.0-rc3-00191-gfabf418 #162 Not tainted
---
systemd/1 is trying to acquire l
maxcpu=n sets the number of CPUs activated at boot time to a max of n,
but allowing the remaining CPUs to be brought up later if the user
decides to do so. However, on arm64 due to various reasons, we disallowed
hotplugging CPUs beyond n, by marking them not present. Now that
we have checks in plac
This series is an attempt at fixing the maxcpus=n behavior
on arm64. So far we have disabled hotplugging a CPU > n,
when maxcpus=n is in effect, due to following reasons.
1) Possible cpu feature incompatibilities with the new CPU
in heterogeneous systems.
2) New CPU requiring an errata work
On Thu, Apr 21, 2016 at 04:43:45PM +0300, Michael S. Tsirkin wrote:
> This adds a flag to enable/disable bypassing the IOMMU by
> virtio devices.
>
> This is on top of patch
> http://article.gmane.org/gmane.comp.emulators.qemu/403467
> virtio: convert to use DMA api
>
> Tested with patchset
> htt
Add scope parameter to the arm64_cpu_capabilities::matches(), so that
this can be reused for checking the capability on a given CPU vs the
system wide. The system uses the default scope associated with the
capability for initialising the CPU_HWCAPs and ELF_HWCAPs.
Cc: James Morse
Cc: Marc Zyngier
From: Marc Zyngier
Now that the capabilities are only available once all the CPUs
have booted, we're unable to check for a particular feature
in any subsystem that gets initialized before then.
In order to support this, introduce a local_cpu_has_cap() function
that tests for the presence of a gi
> Turns out the call to cancel_delayed_work_sync() in watchdog_release()
> is not necessary and can be dropped. If the worker is no longer necessary,
> the subsequent call to watchdog_update_worker() will cancel it. If it is
> already running, it won't do anything, since the worker function checks
From: Kan Liang
PERF_GLOBAL_CTL could be cleared after Package C7. This patch tries to
workaround this issue by re-enable PERF_GLOBAL_CTL in enable_box.
The workaround does not cover all cases. It helps for new events after
returning from C7.
There is no drawback in letting the thing enabled, so
From: Kan Liang
This patch addes full support for Intel SKL client uncore.
- Add support for SKL client cpu uncore, which is similar to BDW
client. There are some differences in CBOX number and uncore control
MSR.
- Add new CPU model 78 for SkyLake Mobile, include both cpu and pci
unco
Hi Appana,
Thanks for the review.
On Thu, 21 Apr 2016, Appana Durga Kedareswara Rao wrote:
>
>
> > -Original Message-
> > From: dmaengine-ow...@vger.kernel.org [mailto:dmaengine-
> > ow...@vger.kernel.org] On Behalf Of Peter Griffin
> > Sent: Thursday, April 21, 2016 4:34 PM
> > To: li
On Wed 2016-04-20 23:27:05, Michal Hocko wrote:
> On Wed 20-04-16 17:29:22, Tejun Heo wrote:
> > Hello, Michal.
> >
> > On Sun, Apr 17, 2016 at 08:07:48AM -0400, Michal Hocko wrote:
> [...]
> > > I liked your proposal when mem_cgroup_move_charge would be called from a
> > > context which doesn't h
On Mon, Apr 18, 2016 at 08:43:16PM +0200, H. Nikolaus Schaller wrote:
> This is a driver for the Integrated Silicon Solution Inc. LED driver
> chips IS31FL3196 and IS31FL3199. They can drive up to 6 or 9
> LEDs.
>
> Each LED is individually controllable in brightness (through pwm)
> in 256 steps s
Pan Xinhui was asking for a lock holder cpu argument in pv_wait()
to help the porting of pvqspinlock to PPC. The new argument will can
help hypervisor expediate the execution of the critical section by
the lock holder, if its vCPU isn't running, so that it can release
the lock sooner.
The pv_wait(
CPU Errata work arounds are detected and applied to the
kernel code at boot time and the data is then freed up.
If a new hotplugged CPU requires a work around which
was not applied at boot time, there is nothing we can
do but simply fail the booting.
Cc: Will Deacon
Cc: Mark Rutland
Cc: Andre Pr
Some users consider DMA optional, thus when driver is not compiled we shouldn't
prevent compilation of the users. Add stubs for dw_dma_probe() and
dw_dma_remove().
Signed-off-by: Andy Shevchenko
---
include/linux/dma/dw.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/linux/dma
Intel Quark UART uses DesignWare DMA IP. Though the DMA IP is connected in such
way that handshake interface uses inverted polarity. We have to provide a
possibility to set this in the DMA driver when configuring a channel.
Introduce a new member of custom slave configuration called 'polarity' and
It seems we need to extend custom slave configuration by one more member to
support Intel Quart UART. It becomes a burden to manage all members of struct
dw_dma_slave one-by-one.
Replace set of fields by embedding struct dw_dma_slave into struct dw_dma_chan.
Signed-off-by: Andy Shevchenko
---
d
There is at least one known device, i.e. UART on Intel Galileo, that works
unreliably in case of use of multi block transfer support in DMA mode.
Override autodetection by user provided data.
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw/core.c| 10 +++---
include/linux/
This patch series (v3: http://www.spinics.net/lists/kernel/msg2215303.html)
contains a number of mostly minor fixes and cleanups for the DW DMA driver. A
couple of them affect the DT binding so these may need to be updated to
maintain compatibility (old format is still supported though). The rest s
On Thu, 2016-04-21 at 18:03 +0300, Andy Shevchenko wrote:
> This patch series (v3: http://www.spinics.net/lists/kernel/msg2215303.
> html)
> contains a number of mostly minor fixes and cleanups for the DW DMA
> driver. A
> couple of them affect the DT binding so these may need to be updated
> to
>
From: Marc Zyngier
When introducing the whole CPU feature detection framework,
we lost the capability to detect a mismatched GIC configuration
(using the GICv2 MMIO interface, but having the system register
interface enabled).
In order to solve this, use the new this_cpu_has_cap() helper.
Also m
On Thu, Apr 21, 2016 at 01:36:14PM +0100, Richard Fitzgerald wrote:
> + ret = snprintf(buf, PAGE_SIZE,
> + "always_on: %u\nboot_on: %u\napply_uV: %u\nramp_disable: %u\n"
> + "soft_start: %u\npull_down: %u\nover_current_protection: %u\n",
> + !!c->always_on,
Used for Voltage Scaling using CPUFreq.
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407-family.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch/arm/boot/dts/stih407-family.dtsi
index af9233b..d0e639cd 10
On Tue, Apr 19, 2016 at 09:40:49AM +0200, Olliver Schinagl wrote:
> When leds are connected in a totem-pole configuration, they can be
> connected either in a active-high, or active-low manor. The driver
> currently always assumes active-high. This patch adds the
> 'nxp,inverted-out' boolean proper
Signed-off-by: Ludovic Barre
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407-family.dtsi | 40 +++
1 file changed, 40 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch/arm/boot/dts/stih407-family.dtsi
Doing so saves quite a bit of code in the driver.
For more information on the 'reserved-memory' bindings see:
Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
Suggested-by: Suman Anna
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407
This patch supplies the Mailbox Controller nodes. In order to
request channels, these nodes will be referenced by Mailbox
Client nodes.
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407-family.dtsi | 33 +
1 file changed, 33 i
This aligns with the internal configuration.
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407-family.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch/arm/boot/dts/stih407-family.dtsi
index
On Tue, Apr 19, 2016 at 04:59:12PM +0800, Peng Fan wrote:
> Add i.MX6UL support in documentation.
>
> Signed-off-by: Peng Fan
> Cc: Srinivas Kandagatla
> Cc: Maxime Ripard
> Cc: Rob Herring
> ---
> Documentation/devicetree/bindings/nvmem/imx-ocotp.txt | 5 +++--
> 1 file changed, 3 insertions
This is used for CPU Frequency Scaling.
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407-family.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch/arm/boot/dts/stih407-family.dtsi
index d0e639cd..eb2601f 10
Signed-off-by: Lee Jones
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stih407-family.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch/arm/boot/dts/stih407-family.dtsi
index 9fa1e58..af9233b 100644
--- a/arch/arm/boot/dts/stih407-f
We pass struct dw_dma_chip to the dw_dma_probe() anyway, thus we may use it to
pass platform data as well.
While here, constify the source of platform data.
Signed-off-by: Andy Shevchenko
---
drivers/ata/sata_dwc_460ex.c | 2 +-
drivers/dma/dw/core.c | 9 +
driv
Hi Ulf,
On Thursday 21 Apr 2016 15:52:06 Ulf Hansson wrote:
> On 21 April 2016 at 14:41, Laurent Pinchart wrote:
> > On Thursday 21 Apr 2016 11:10:19 Ulf Hansson wrote:
> >> On 21 April 2016 at 01:30, Laurent Pinchart wrote:
> >>> On Monday 07 Mar 2016 11:10:08 Ulf Hansson wrote:
> [...]
> >>
The nr_masters value equal to 0 is invalid since this DMA controller has to
have at least one master.
Check this before we proceed with the rest of properties.
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw/platform.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions
On Thu, Apr 21, 2016 at 6:30 AM, Boris Ostrovsky
wrote:
>
>
> On 04/15/2016 06:03 PM, Thomas Garnier wrote:
>>
>> +void __init kernel_randomize_memory(void)
>> +{
>> + size_t i;
>> + unsigned long addr = memory_rand_start;
>> + unsigned long padding, rand, mem_tb;
>> + stru
Keep the entire platform data in the struct dw_dma.
It makes the driver a bit cleaner.
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw/core.c| 30 +++---
drivers/dma/dw/platform.c| 4 ++--
drivers/dma/dw/regs.h| 5 ++---
inc
On Thu, Apr 21, 2016 at 03:56:53PM +0100, Stefan Hajnoczi wrote:
> On Thu, Apr 21, 2016 at 04:43:45PM +0300, Michael S. Tsirkin wrote:
> > This adds a flag to enable/disable bypassing the IOMMU by
> > virtio devices.
> >
> > This is on top of patch
> > http://article.gmane.org/gmane.comp.emulators
There are several changes are done here:
- Convert the property to be in bytes
Besides this is common practice for such property the use of a value in bytes
much more convenient than handling the encoded value.
- Rename data_width to data-width in the device tree bindings
- While here, replace
On Thu, Apr 21, 2016 at 01:18:27PM +0100, Matt Fleming wrote:
> ( Good Lord, I hate doing string manipulation in C )
(yep)
>
> On Wed, 20 Apr, at 03:25:32PM, Laszlo Ersek wrote:
> >
> > So, "len" does not include the room for the terminating NUL-byte here.
> > When "len" is passed to ucs2_as_ut
Am Donnerstag, 21. April 2016, 15:03:37 schrieb Nikos Mavrogiannopoulos:
Hi Nikos,
>
> [quote from pdf]
>
> > ... DRBG is “minimally” seeded with 112^6 bits of entropy.
> > This is commonly achieved even before user space is initiated.
>
> Unfortunately one of the issues of the /dev/urandom int
Em Thu, Apr 21, 2016 at 12:48:58PM +0200, Peter Zijlstra escreveu:
> On Wed, Apr 20, 2016 at 07:47:30PM -0300, Arnaldo Carvalho de Melo wrote:
> > The default remains 127, which is good for most cases, and not even hit
> > most of the time, but then for some cases, as reported by Brendan, 1024+
> >
You'll notice that the voltage cell is populated with 0's. Voltage
information is very platform specific, even depends on 'cut' and
'substrate' versions. Thus it is left blank for a generic (safe)
implementation. If other nodes/properties are provided by the
bootloader, the ST CPUFreq driver wil
This patch series (v3: http://www.spinics.net/lists/kernel/msg2215303.html)
contains a number of mostly minor fixes and cleanups for the DW DMA driver. A
couple of them affect the DT binding so these may need to be updated to
maintain compatibility (old format is still supported though). The rest s
On Tue, Apr 19, 2016 at 03:44:12PM +0200, Krzysztof Kozlowski wrote:
> Beside regular feed control interrupt, the driver requires also hash
> interrupt for older SoCs (samsung,s5pv210-secss). However after
> requesting it, the interrupt handler isn't doing anything with it, not
> even clearing the
On Thu, Apr 21, 2016 at 5:16 AM, Borislav Petkov wrote:
> On Wed, Apr 20, 2016 at 06:16:01PM -0700, Andy Lutomirski wrote:
>> Also, it's time for someone to do UMIP. I'll see if I can convince
>> someone in KVM land to emulate it to make it easier to test.
>
> That'll be fun - we can simply set t
On Thu, Apr 21, 2016 at 01:02:02PM +0100, Richard Fitzgerald wrote:
> If we don't have a GPIO for LDOENA it's impossible to turn
> the LDO1 regulator off so mark it as always-on.
If there is no enable control method for the regulator this should be
redundant. If that's not the case you should fix
Hi,
[auto build test WARNING on next-20160421]
[also build test WARNING on v4.6-rc4]
[cannot apply to robh/for-next asoc/for-next v4.6-rc4 v4.6-rc3 v4.6-rc2]
[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
2016-04-21 13:29+0200, Greg Kurz:
> On Wed, 20 Apr 2016 20:29:09 +0200
> Radim Krčmář wrote:
>> 2016-04-20 17:44+0200, Greg Kurz:
>> > Commit 338c7dbadd26 ("KVM: Improve create VCPU parameter (CVE-2013-4587)")
>> > introduced a check to prevent potential kernel memory corruption in case
>> > the v
The tty field was missing from AUDIT_LOGIN events.
Refactor code to create a new function audit_get_tty(), using it to
replace the call in audit_log_task_info() and to add it to
audit_log_set_loginuid(). Lock and bump the kref to protect it, adding
audit_put_tty() alias to decrement it.
Signed-o
On Tue, Apr 19, 2016 at 05:42:52PM +0200, H. Nikolaus Schaller wrote:
> Signed-off-by: H. Nikolaus Schaller
A more specific subject and commit message would be nice. It is a lot of
change to figure out it is just s/100mA/100uA/.
Acked-by: Rob Herring
> ---
> Documentation/devicetree/bindings
Hi Peter,
This is the second round of my filtering patchset. I've changed quite
many things since the previous one [1], notably
* split the pmu callback in two as we discussed,
* split the filter itself into 'core' and 'hw' parts,
* made only parent events eligible for configuring filters (chi
Newer versions of Intel PT support address ranges, which can be used to
define IP address range-based filters or TraceSTOP regions. Number of
ranges in enumerated via cpuid.
This patch implements pmu callbacks and related low-level code to allow
filter validation, configuration and programming int
For instruction trace filtering, namely, for communicating filter
definitions from userspace, I'd like to re-use the SET_FILTER code
that the tracepoints are using currently.
To that end, this patch moves the relevant code from behind EVENT_TRACING
macro.
Signed-off-by: Alexander Shishkin
---
k
New versions of Intel PT support address range-based filtering. These
are the registers, bit definitions and relevant CPUID bits.
Signed-off-by: Alexander Shishkin
---
arch/x86/events/intel/pt.c | 2 ++
arch/x86/events/intel/pt.h | 2 ++
arch/x86/include/asm/msr-index.h | 18 ++
On Tue, Apr 19, 2016 at 05:42:51PM +0200, H. Nikolaus Schaller wrote:
>
>
> H. Nikolaus Schaller (1):
> Documentation: bindings: fix palmas-rtc documentation
>
> Documentation/devicetree/bindings/rtc/rtc-palmas.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Don't send a co
Many instruction trace pmus out there support address range-based
filtering, which would, for example, generate trace data only for a
given range of instruction addresses, which is useful for tracing
individual functions, modules or libraries. Other pmus may also
utilize this functionality to allow
Trace filtering code needs an iterator that can go through all events in
a context, including inactive and filtered, to be able to update their
filters' address ranges based on mmap or exec events.
This patch changes perf_event_aux_ctx() to optionally do this.
Signed-off-by: Alexander Shishkin
-
On Wed, Apr 20, 2016 at 03:02:30PM +0530, Vinay Simha BN wrote:
> Japan Display Inc.
>
> Signed-off-by: Vinay Simha BN
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Rob Herring
On 20/04/16 16:21, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Apr 19, 2016 at 05:09:59PM +0100, Jon Hunter wrote:
>> On 19/04/16 16:40, Mark Brown wrote:
>
>>> This is *really* weird. Why would we need the list lock to do a
>>> device_register()?
>
>> So I did not think t
On 04/21/2016 09:43 AM, Tomi Valkeinen wrote:
>> Signed-off-by: Lodes, Jim
>
> Thanks, looks good. Can you fix the email here too, and resend?
Yes, I'll fix the sign off and make sure we have it correct going forward.
On Tue, Apr 05, 2016 at 06:18:18PM -0700, Jake Oshins wrote:
> Existing code just called release_mem_region(). Adding a
> wrapper around it allows the more complex range tracking
> that is introduced later in this patch series.
>
> Signed-off-by: Jake Oshins
With typo fix below,
Acked-by: Bjor
From: Gustavo Padovan
Change SYNC_IOC_FILE_INFO (former SYNC_IOC_FENCE_INFO) behaviour to avoid
future API breaks and optimize buffer allocation.
Now num_fences can be filled by the caller to inform how many fences it
wants to retrieve from the kernel. If the num_fences passed is greater
than ze
From: Gustavo Padovan
Hi,
Here we clean up the Sync ABI and then improve in to a more optimized version.
Also it is now less likely to need changes in the future. This is not
breaking any upstream user of the sync framework, as no driver wired support
for it, so far Android is the only user. A p
From: Gustavo Padovan
This function had copies in 3 different files. Unify them in kernel.h.
Cc: Joe Perches
Cc: Andrew Morton
Cc: David Airlie
Cc: Daniel Vetter
Cc: Rob Clark
Signed-off-by: Gustavo Padovan
---
v2: add typecheck() (comment from Maarten Lankhorst)
v3: make u64_to_user_ptr
> Am 21.04.2016 um 17:31 schrieb Rob Herring :
>
> On Tue, Apr 19, 2016 at 05:42:51PM +0200, H. Nikolaus Schaller wrote:
>>
>>
>> H. Nikolaus Schaller (1):
>> Documentation: bindings: fix palmas-rtc documentation
>>
>> Documentation/devicetree/bindings/rtc/rtc-palmas.txt | 6 +++---
>> 1 file
Em Thu, Apr 21, 2016 at 12:17:07PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Apr 21, 2016 at 12:48:58PM +0200, Peter Zijlstra escreveu:
> > On Wed, Apr 20, 2016 at 07:47:30PM -0300, Arnaldo Carvalho de Melo wrote:
> > > +++ b/kernel/events/callchain.c
>
> > > @@ -73,7 +81,7 @@ static int
On Mon, Mar 21, 2016 at 10:39:52AM +0100, Krzysztof Halasa wrote:
> I think this bug needs to be fixed, this way or another.
>
> The platform in question is Cavium CNS3xxx, ARMv6.
>
> A recent patch by Arnd Bergmann (498a92d42596 "ARM: cns3xxx: pci: avoid
> potential stack overflow") converted an
On 20/04/16 12:03, Jon Hunter wrote:
> Some IRQ chips, such as GPIO controllers or secondary level interrupt
> controllers, may require require additional runtime power management
> control to ensure they are accessible. For such IRQ chips, it makes sense
> to enable the IRQ chip when interrupts a
Unfortunately HPD isn't functional once we shut off all of the power
domains. Unfortunately we can end up shutting off all of the power
domains in any situation where we don't have any monitors connected,
essentially breaking hpd for the user unless they reboot with one of
their monitors connected.
401 - 500 of 873 matches
Mail list logo
