Commit-ID: f594bae08183fb6b57db55387794ece3e1edf6f6
Gitweb: http://git.kernel.org/tip/f594bae08183fb6b57db55387794ece3e1edf6f6
Author: Borislav Petkov
AuthorDate: Mon, 7 Mar 2016 16:44:44 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016 10:11:18
Commit-ID: a23f96ee4d51ebd50b83ce0dbb5d04898fb8e3cb
Gitweb: http://git.kernel.org/tip/a23f96ee4d51ebd50b83ce0dbb5d04898fb8e3cb
Author: Adrian Hunter
AuthorDate: Mon, 7 Mar 2016 16:44:42 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
Commit-ID: c3bc0c436899d01c3a09fddb308d487cc032fbd2
Gitweb: http://git.kernel.org/tip/c3bc0c436899d01c3a09fddb308d487cc032fbd2
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:45 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
Commit-ID: 4b633eba14627bcb1ef5c7a498e7dc308cd6a5d6
Gitweb: http://git.kernel.org/tip/4b633eba14627bcb1ef5c7a498e7dc308cd6a5d6
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:43 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
This patch adds the Makefile and Kconfig required to make the driver build.
Signed-off-by: John Crispin
---
drivers/net/ethernet/Kconfig |1 +
drivers/net/ethernet/Makefile |1 +
drivers/net/ethernet/mediatek/Kconfig | 17 +
On Mon, Mar 07, 2016 at 10:24:27PM -0600, Bjorn Helgaas wrote:
[...]
> > > Actually, I did find one problem report:
> > > http://forum.doozan.com/read.php?2,17868,22070,quote=1 from last May,
> > > but apparently it got lost in a forum and never found its way
> > > upstream.
> > >
> > > I
Hi Jon,
[auto build test WARNING on spi/for-next]
[also build test WARNING on next-20160308]
[cannot apply to v4.5-rc7]
[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/Jon-Hunter/spi-core-Fix
On 03/08/2016 02:59 AM, Thomas Gleixner wrote:
> On Tue, 23 Feb 2016, Prarit Bhargava wrote:
>
>> This patchset adds monotonic and real printk timestamps. The first patch
>> changes CONFIG_PRINT_TIME from a bool to an int to allow for the additional
>> timestamps that are added in patch 2.
>>
sg_alloc_table_from_buf() provides an easy solution to create an sg_table
from a virtual address pointer. This function takes care of dealing with
vmallocated buffers, buffer alignment, or DMA engine limitations (maximum
DMA transfer size).
Signed-off-by: Boris Brezillon
Allow for NULL cur_offs values when the caller does not know where the
NAND page register pointer point to.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/sunxi_nand.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
sunxi_nfc_hw_ecc_read_chunk() always retrieves the ECC and protected free
bytes, no matter if the user really asked for it or not. This can take a
non negligible amount of time, especially on NAND chips exposing large OOB
areas (> 1KB). Make it optional.
Signed-off-by: Boris Brezillon
On Mon, Mar 07, 2016 at 09:32:24AM +0800, Jianyu Zhan wrote:
> Commit e91467ecd1ef ("bug in futex unqueue_me") introduces a barrier()
> in unqueue_me(), to address below problem.
>
> The scenario is like this:
>
>
> original code:
>
> retry:
>lock_ptr = q->lock_ptr;
On Mon, Mar 07, 2016 at 03:41:15AM +0100, Rafael J. Wysocki wrote:
> If my understanding of the requency invariant utilization idea is correct,
> it is about re-scaling utilization so it is always relative to the capacity
> at the max frequency.
Right. So if a workload runs for 5ms at @1GHz and
On Tue, 8 Mar 2016, Sebastian Andrzej Siewior wrote:
> I sucked this in. It seems to work. What remains that free_irq() thingy:
> |WARNING: CPU: 0 PID: 0 at kernel/irq/manage.c:1541 __free_irq+0xb4/0x2e0()
> |Trying to free already-free IRQ 16
> |CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.4-rt10+
On Tue, Mar 08, 2016 at 10:42:12AM +, James Morse wrote:
> On 08/03/16 10:26, Peter Zijlstra wrote:
> > In any case, please try -rc6, which includes:
>
> Bother, I should have thought to test with the later rcs, I foolishly stopped
> with rc5.
>
> > a096309bc467 perf: Fix scaling vs.
I found this while testing the permission_fault patch with ept=0.
Paolo Bonzini (2):
KVM: MMU: fix ept=0/pte.u=0/pte.w=0/CR0.WP=0/CR4.SMEP=1/EFER.NX=0
combo
KVM: MMU: fix reserved bit check for
pte.u=0/pte.w=0/CR0.WP=0/CR4.SMEP=1/EFER.NX=0
Documentation/virtual/kvm/mmu.txt | 3 ++-
On Tue 08-03-16 12:12:20, Vlastimil Babka wrote:
> On 03/08/2016 11:10 AM, Michal Hocko wrote:
> > On Tue 08-03-16 10:52:15, Vlastimil Babka wrote:
> >> On 03/08/2016 10:46 AM, Michal Hocko wrote:
> > [...]
> > @@ -3294,6 +3289,18 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned
> > int
This driver parse the reboot commands like "reboot loader"
and "reboot recovery" to get a boot mode described in the
device tree , then call the corresponding write interfae
to store the boot mode in some place like special register
or ram , which can be read by the bootloader after system
On 03/08/2016 01:22 PM, Michal Hocko wrote:
>> Thanks.
>>
>>> A more important question is whether the criteria I have chosen are
>>> reasonable and reasonably independent on the particular implementation
>>> of the compaction. I still cannot convince myself about the convergence
>>> here. Is it
On Sat, Mar 05, 2016 at 11:18:48PM -0600, Chris Friesen wrote:
> The callers of steal_account_process_tick() expect it to return
> whether a jiffy should be considered stolen or not.
>
> Currently the return value of steal_account_process_tick() is in
> units of cputime, which vary between either
V7:
updated patches with "Reviewed-by" and "Acked-by" tags
V6:
as per comment, patch 15/15 in V5 was divided into 3 patches in V6
V5:
as per comment, patch 05/14 in V4, was divided into 2 patches in V5
V4:
fixed DOS EOL symbols in 2 new files
V3:
Due to comments in V2
Removed change 02/17 of
From: Sudip Mukherjee
We are getting build warning about:
sound/soc/codecs/rt5640.c:1892:11: warning: unused variable 'dai_sel'
The use of the variable was removed but the variable itself was not
removed.
Fixes: c467fc0e010b ("ASoC: rt5640: Set PLL src
On Sat, Feb 27, 2016 at 1:19 AM, Eric Anholt wrote:
> Since all of these pins were documented, we can use their names to
> explain what's going on.
>
> Signed-off-by: Eric Anholt
> + pinctrl-0 = <_gpio0
> +_gpio2
> +
On 08.03.16 10:31:33, Ganapatrao Kulkarni wrote:
> On Tue, Mar 8, 2016 at 1:17 AM, David Daney wrote:
> > On 03/07/2016 11:22 AM, Robert Richter wrote:
> >>
> >> On 03.03.16 15:55:35, David Daney wrote:
> >>>
> >>> From: Ganapatrao Kulkarni
On 2016/03/08 17:30, Paolo Bonzini wrote:
> On 08/03/2016 09:00, Takuya Yoshikawa wrote:
>>> KVM: MMU: introduce kvm_mmu_flush_or_zap
>>> KVM: MMU: move TLB flush out of __kvm_sync_page
>>> KVM: MMU: use kvm_sync_page in kvm_sync_pages
>>> KVM: MMU: cleanup __kvm_sync_page and its
On Tue, 8 Mar 2016 09:16:13 +0100, Jean Delvare wrote:
> On Thu, 3 Mar 2016 15:34:15 -0800, Greg KH wrote:
> > I'm announcing the release of the 4.4.4 kernel.
> >
> > All users of the 4.4 kernel series must upgrade.
> > (...)
> > Alex Deucher (13):
> > (...)
> > drm/radeon/pm: adjust
On Mon, Mar 7, 2016 at 11:46 PM, Masahiro Yamada
wrote:
> The compatible string "simple-bus" is well defined in ePAPR, while
> I see no documentation for the "arm,amba-bus" in ePAPR or under
> Documentation/devicetree/.
>
> DT is also used by other projects than
On Mon, Mar 07, 2016 at 11:27:26PM +, Luck, Tony wrote:
> >> + bytes = mbm_current->interval_bytes * MSEC_PER_SEC;
> >> + do_div(bytes, diff_time);
> >> + mbm_current->bandwidth = bytes;
> >> + mbm_current->interval_bytes = 0;
> >> +
From: Yuan Yao
The patch adds LS2085a to DSPI compatible.
The DSPI driver on LS2080A should use TCFQ mode.
It's different from on vf610.
Signed-off-by: Yuan Yao
---
arch/arm64/boot/dts/freescale/fsl-ls2080a.dtsi | 2 +-
1 file changed, 1 insertion(+), 1
On Mon, Feb 29, 2016 at 6:13 AM, Henry Paulissen wrote:
> While I was testing irq's on the cubietruck I found a couple of
> not working irq pins. Further diving into the problem it opened
> up a mess called "manual".
>
> This so called manual (A20 user manual v1.3 dated
On Tue, 8 Mar 2016, kbuild test robot wrote:
> Hi Thomas,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: e2857b8f11a289ed2b61d18d0665e05c1053c446
> commit: 3795de236d67a05994a1a12759db9d4dd9ffc42c
Commit 28c015a9daabe4e ("mtd: davinci-nand: disable subpage write for
keystone-nand") disables subpage write for Keystone SOCs due to hw
issues.
But subpage writes doesn't work even for DaVinci SOCs due to hw issues.
So set NAND_NO_SUBPAGE_WRITE option for all devices compatible to
this driver.
* Geert Uytterhoeven wrote:
> On Tue, Mar 8, 2016 at 9:38 AM, kbuild test robot
> wrote:
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > head:
On Mon, Mar 07, 2016 at 04:02:15PM -0800, Greg KH wrote:
> On Mon, Mar 07, 2016 at 06:55:43PM -0500, Gabriel Somlo wrote:
> > Allowing for the future possibility of implementing AML-based
> > (i.e., firmware-triggered) access to the QEMU fw_cfg device,
> > acquire the global ACPI lock when
On Tuesday 08 March 2016 16:22:15, Stephen Boyd wrote:
> Some systems are memory constrained but they need to load very
> large firmwares.
Out of curiousity, about which sizes of memory and firmware are you talking
about?
Regards,
Alexander
On Tue, Mar 08, 2016 at 11:43:36AM +0900, Chanho Min wrote:
> The use of phys_to_page is wrong in commit cb06ff102e2d ("ARM: PL011:
> Add support for Rx DMA buffer polling."), beacase DMA address is not
> physical address. Also, phys_to_page is not declared in some architecture.
> The use of
On Tue, Mar 08, 2016 at 09:48:42AM +, Zhang, Rui wrote:
> Punit and Javi,
>
> What do you think of this? I'd like to get your ACK before taking it.
Sorry, I didn't realize you were waiting for us. I'm quite happy for
this to go in:
Acked-by: Javi Merino
> >
Quoting Alexander Stein (2016-03-08 16:32:21)
> On Tuesday 08 March 2016 16:22:15, Stephen Boyd wrote:
> > Some systems are memory constrained but they need to load very
> > large firmwares.
>
> Out of curiousity, about which sizes of memory and firmware are you talking
> about?
>
Hm.. I've
On Thu, 3 Mar 2016 15:34:15 -0800, Greg KH wrote:
> I'm announcing the release of the 4.4.4 kernel.
>
> All users of the 4.4 kernel series must upgrade.
> (...)
> Alex Deucher (13):
> (...)
> drm/radeon/pm: adjust display configuration after powerstate
I am getting a regression from
On Sat, Feb 27, 2016 at 6:06 AM, Julien Grossholtz
wrote:
> The TS-4800 is an i.MX515 board. Its GPIO driver should only be compiled
> for this CPU or for test builds.
>
> Signed-off-by: Julien Grossholtz
Patch
On mån, 2016-03-07 at 20:59 -0800, Andy Lutomirski wrote:
> On Thu, May 28, 2015 at 12:42 PM, Eric W. Biederman
> wrote:
> > Andy Lutomirski writes:
> >
> Apparently alexl is encountering some annoyances related to the
> current workaround, and the
* Adrian Hunter wrote:
> On 07/03/16 21:44, Arnaldo Carvalho de Melo wrote:
> > From: Adrian Hunter
>
> Very sorry, but I just noticed that this and patch 5 (perf jit: Move clockid
> validation) have the wrong email address for the "From" and
On (03/08/16 10:08), Michal Hocko wrote:
> On Tue 08-03-16 12:51:04, Sergey Senozhatsky wrote:
> > Hello Michal,
> >
> > On (03/07/16 17:08), Michal Hocko wrote:
> > > On Mon 29-02-16 22:02:13, Michal Hocko wrote:
> > > > Andrew,
> > > > could you queue this one as well, please? This is more a
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can
From: Vikram Mulukutla
Some low memory systems with complex peripherals cannot afford to
have the relatively large firmware images taking up valuable
memory during suspend and resume. Change the internal
implementation of firmware_class to disallow caching based on a
From: Laura Abbott
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
Both the IOMMU and non-IOMMU allocations don't respect the
NO_KERNEL_MAPPING attribute, therefore drivers can't save virtual
address space and time spent mapping large buffers that are
intended only for userspace. Plumb this attribute into the code
for both types of DMA ops.
Cc: Robin Murphy
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can
> Le 8 mars 2016 à 09:54, Geert Uytterhoeven a écrit :
>
> On Mon, Mar 7, 2016 at 7:24 PM, Andreas Färber wrote:
>> Drop #address-cells and #size-cells, which are not required by the
>> gpio-keys binding documentation, as button sub-nodes are not
On Tue 08-03-16 10:24:56, Vlastimil Babka wrote:
[...]
> > @@ -2819,28 +2819,22 @@ static struct page *
> > __alloc_pages_direct_compact(gfp_t gfp_mask, unsigned int order,
> > int alloc_flags, const struct alloc_context *ac,
> > enum migrate_mode mode, int
On Tue, 8 Mar 2016 17:25:13 +0800
Jiancheng Xue wrote:
> Hi Brian,
>Thank you very much for your comments.
>
> On 2016/3/8 6:52, Brian Norris wrote:
> [...]
> >>
> >> diff --git a/Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt
> >>
On 03/08/2016 10:46 AM, Michal Hocko wrote:
> On Tue 08-03-16 10:24:56, Vlastimil Babka wrote:
> [...]
>>> @@ -2819,28 +2819,22 @@ static struct page *
>>> __alloc_pages_direct_compact(gfp_t gfp_mask, unsigned int order,
>>> int alloc_flags, const struct alloc_context *ac,
>>>
On Mon, 7 Mar 2016 12:54:13 -0500
Willem de Bruijn wrote:
> On Mon, Mar 7, 2016 at 10:36 AM, Jesper Dangaard Brouer
> wrote:
> > Hi Google,
> >
> > While playing with RPS, I needed to read stats from
> > /proc/net/softnet_stat and the tools I
On 07/03/16 19:00, Olof Johansson wrote:
On Mon, Mar 7, 2016 at 4:19 AM, Sudeep Holla wrote:
Hi Olof,
On 07/03/16 05:41, Olof Johansson wrote:
Hi Wim,
It's much easier for us if all DTS changes go in through the arm-soc
trees, to avoid these kind of conflicts. Is
Am 08.03.2016 um 09:54 schrieb Geert Uytterhoeven:
> On Mon, Mar 7, 2016 at 7:24 PM, Andreas Färber wrote:
>> Drop #address-cells and #size-cells, which are not required by the
>> gpio-keys binding documentation, as button sub-nodes are not devices.
>>
>> Reported-by: Julien
Hi Ingo,
On Tue, Mar 8, 2016 at 10:21 AM, Ingo Molnar wrote:
>> Same comment as before: thou shall not compile kernels for m68k without
>> selecting any platform support.
>
> That should be enforced at the Kconfig level.
I'm fully aware of that ;-)
Unfortunately it's not
On 2016/03/07 23:15, Paolo Bonzini wrote:
> Having committed the ubsan fixes, this are the cleanups that are left.
>
> Compared to v1, I have fixed the patch to coalesce page zapping after
> mmu_sync_children (as requested by Takuya and Guangrong), and I have
> rewritten is_last_gpte again in an
On 08/03/16 12:48, Ian Munsie wrote:
From: Ian Munsie
This adds an afu_driver_ops structure with event_pending and
deliver_event callbacks. An AFU driver such as cxlflash can fill these
out and associate it with a context to enable passing custom AFU
specific events to
On 08/03/16 12:48, Ian Munsie wrote:
From: Michael Neuling
This provides AFU drivers a means to associate private data with a cxl
context. This is particularly intended for make the new callbacks for
driver specific events easier for AFU drivers to use, as they can easily
On Tue, 23 Feb 2016, Prarit Bhargava wrote:
> This patchset adds monotonic and real printk timestamps. The first patch
> changes CONFIG_PRINT_TIME from a bool to an int to allow for the additional
> timestamps that are added in patch 2.
>
> Changes from v6: Petr Mladek pointed out that the
On 03/08/2016 12:45 AM, Yang Shi wrote:
> diff --git a/include/trace/events/hist.h b/include/trace/events/hist.h
> index 6122e42..37f6eb8 100644
> --- a/include/trace/events/hist.h
> +++ b/include/trace/events/hist.h
> @@ -9,6 +9,7 @@
>
> #if !defined(CONFIG_PREEMPT_OFF_HIST) &&
On 03/05/2016 02:54 PM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>> as we have this in Makefile:
>>
>> # enforce correct pointer usage
>> KBUILD_CFLAGS += $(call cc-option,-Werror=incompatible-pointer-types)
>
> Sorry, never mind - this is a recent commit that is not
On Mon, 7 Mar 2016, Bjorn Helgaas wrote:
> On Mon, Mar 07, 2016 at 11:55:43AM -0500, Sinan Kaya wrote:
> > It makes sense for SCI as it is Intel specific.
> >
> > Unfortunately, this cannot be done in an arch independent way. Of course,
> > ARM had to implement its own thing. While
Hi Tadeusz,
There is also a follow-up in the next paragraph:
"That pretty much sums up the new attack: the side-channel defenses that were
hoped to be sufficient were found not to be (again). So the answer, this time I
believe, is to make the processing rigorously constant-time."
The author
On Tue, Mar 8, 2016 at 9:38 AM, kbuild test robot
wrote:
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: e2857b8f11a289ed2b61d18d0665e05c1053c446
> commit:
The patch
regulator: pv88060: fix incorrect clear of event register
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On Sun, Feb 28, 2016 at 7:30 PM, Amitoj Kaur Chawla
wrote:
> Replace calls to devm_request_mem_region and devm_ioremap with a
> direct call to devm_ioremap_resource instead and modify error
> handling.
Patch applied, adding the timberdale: prefix.
Yours,
Linus Walleij
On Tue, Mar 8, 2016 at 9:49 AM, Rob Herring wrote:
>> diff --git a/arch/arm/boot/dts/axm55xx.dtsi b/arch/arm/boot/dts/axm55xx.dtsi
>> index ea288f0..8da4582 100644
>> --- a/arch/arm/boot/dts/axm55xx.dtsi
>> +++ b/arch/arm/boot/dts/axm55xx.dtsi
>> @@ -107,7 +107,7 @@
>>
On Tue 08-03-16 12:51:04, Sergey Senozhatsky wrote:
> Hello Michal,
>
> On (03/07/16 17:08), Michal Hocko wrote:
> > On Mon 29-02-16 22:02:13, Michal Hocko wrote:
> > > Andrew,
> > > could you queue this one as well, please? This is more a band aid than a
> > > real solution which I will be
* Thomas Gleixner wrote:
> On Tue, 8 Mar 2016, Daniel Wagner wrote:
>
> > From: Daniel Wagner
> >
> > With the introduction of the simple wait API we have two very
> > similar APIs in the kernel. For example wake_up() and swake_up()
> > is only
On (03/08/16 10:24), Vlastimil Babka wrote:
[..]
> > @@ -3294,6 +3289,18 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int
> > order,
> > did_some_progress > 0, no_progress_loops))
> > goto retry;
> >
> > + /*
> > +* !costly allocations are
Based on the Allwinner A64 user manual and on the previous sunxi
pinctrl drivers this introduces the pin multiplex assignments for
the ARMv8 Allwinner A64 SoC.
Port A is apparently used for the fixed function DRAM controller, so
the ports start at B here (the manual mentions "n from 1 to 7", so
Hi David,
Thanks for posting the final version. Very nice driver.
Applied whole series, after dropping leds-sn3218 with its
DT bindings. Stefan, thanks for testing the driver on the
Si-En hardware.
Thanks,
Jacek Anaszewski
On 03/08/2016 01:57 AM, David Rivshin (Allworx) wrote:
From: David
On Tue, Mar 08, 2016 at 08:51:31AM +0100, Maxime Ripard wrote:
> > > > > > + * struct sun4i_dma_chan_config - DMA channel config
> > > > > > + *
> > > > > > + * @para: contains information about block size and time before
> > > > > > checking
> > > > > > + * DRQ line. This is device specific
On Tue, Mar 08, 2016 at 09:42:31AM +0100, Hans de Goede wrote:
>
>
> I see 2 possible reasons why waiting till checking for drq can help:
>
> 1) A lot of devices have an internal fifo hooked up to a single mmio data
> register which gets read using the general purpose dma-engine, it allows
>
On Mon, 7 Mar 2016, Jacob Pan wrote:
> On Wed, 24 Feb 2016 13:31:34 -0800
> Jacob Pan wrote:
>
> > Changes since v5:
> > - Split changes into seprate patches. No code change.
> > Changes since V4:
> > - Deleted unnecessary cpumask_any_and() call, assign
On Mon, Mar 7, 2016 at 5:27 AM, Geert Uytterhoeven wrote:
> Hi Rob,
>
> On Fri, Mar 4, 2016 at 4:13 PM, Rob Herring wrote:
>> Sync to upstream dtc commit 53bf130b1cdd ("libfdt: simplify
>> fdt_node_check_compatible()"). This adds the following commits from
This baseboard can be used with all TX6 SoMs, but only a certain set
of combinations can be ordered by default. Add support for these
combinations in mainline, so that users can easily adopt their own
combination of SoM and baseboard themselves.
Signed-off-by: Lothar Waßmann
Add an empty line between properties and subnode in the clocks node.
Signed-off-by: Lothar Waßmann
---
arch/arm/boot/dts/imx6qdl-tx6.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/imx6qdl-tx6.dtsi
b/arch/arm/boot/dts/imx6qdl-tx6.dtsi
index
GPLv2-only devicetrees make reuse difficult for software components
licensed under a different license.
The consensus is that a GPL/X11 dual-license should allow all necessary
uses, so relicense the imx6*-tx6* files to this combination.
Signed-off-by: Lothar Waßmann
On 2/1/2016 11:54 PM, Wolfram Sang wrote:
device may be completed in separate kernel thread. PM core ensures
all power state transition dependency between devices. This patch
> I'd like an Ack on that from a PM maintainer, because I think chips like
> PMICs are special and might not be
The spidev driver doesn't like to be instantiated via a naked 'spidev'
compatible, though it is very convenient to invoke it this way without
a dedicated SPI device for basic functional testing.
Disable the spi node by default to silence the WARN_ON() from the
spidev driver, but leave the
From: Daniel Wagner
With the introduction of the simple wait API we have two very
similar APIs in the kernel. For example wake_up() and swake_up()
is only one character away. Although the compiler will warn
happily the wrong usage it keeps on going an even links the
Move clockid validation into jit_process() so it can later be
made conditional.
Signed-off-by: Adrian Hunter
---
Changes in V2:
Fixed "From" and "Signed-off-by" email addresses
tools/perf/builtin-inject.c | 24
Hi,
On 08-03-16 08:51, Maxime Ripard wrote:
On Tue, Mar 08, 2016 at 08:25:47AM +0530, Vinod Koul wrote:
On Mon, Mar 07, 2016 at 09:30:24PM +0100, Maxime Ripard wrote:
On Mon, Mar 07, 2016 at 04:08:57PM +0100, Boris Brezillon wrote:
Hi Vinod,
On Mon, 7 Mar 2016 20:24:29 +0530
Vinod Koul
Intel PT uses TSC as a timestamp, so add support for using TSC
instead of the monotonic clock. Use of TSC is selected by
an environment variable "JITDUMP_USE_ARCH_TIMESTAMP" and flagged
in the jitdump file with flag JITDUMP_FLAGS_ARCH_TIMESTAMP.
Signed-off-by: Adrian Hunter
For Intel PT / BTS, define the environment variable that selects
TSC timestamps in the jitdump file.
Signed-off-by: Adrian Hunter
---
Changes in V2:
Fixed "From" and "Signed-off-by" email addresses
tools/perf/arch/x86/util/intel-bts.c | 5 +
Intel PT uses the time members from the perf_event_mmap_page
to convert between TSC and perf time.
Due to a lack of foresight when Intel PT was implemented,
those time members were recorded in the (implementation
dependent) AUXTRACE_INFO event, the structure of which is
generally inaccessible
On 2016年03月04日 16:49, Paolo Bonzini wrote:
> On 04/03/2016 08:12, Lan Tianyu wrote:
/*
- * wmb: make sure everyone sees our modifications to the page tables
- * rmb: make sure we see changes to vcpu->mode
>>>
>>> You want to leave the comment explaining the memory barriers
For pcie nic, after setting link speed and thers is no link driver does not
need
to do phy reset untill link up.
For some pcie nics, to do this will also reset phy speed down counter and
prevent
phy from auto speed down.
This patch fix the issue reported in following link.
new compatible string: "fsl,ls2080a-dspi".
Signed-off-by: Yuan Yao
Acked-by: Rob Herring
---
Changed in v5:
Fix the subject and commit message.
Changed in v4:
No changes.
Changed in v3:
Add the modifier for new compatible string like:
"fsl,ls2080a-dspi"
Hi Brian,
Thank you very much for your comments.
On 2016/3/8 6:52, Brian Norris wrote:
[...]
>>
>> diff --git a/Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt
>> b/Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt
>> new file mode 100644
>> index 000..7407147
>> --- /dev/null
On 03/08/2016 10:48 AM, James Morris wrote:
On 03/08/2016 06:54 AM, Andy Lutomirski wrote:
This makes sense, but I still think the design is poor. If the hacker
gets code execution, then they can trivially brute force the ADI bits.
ADI in this scenario is intended to prevent the attacker
On Mon 2016-03-07 11:09:15, Philippe Loctaux wrote:
> Removed a * in the beginning of the block, and removed an unnecessary space.
>
> Signed-off-by: Philippe Loctaux
NAK.
Google kerneldoc, people actually like two spaces after ., and you
should not be changing
Adding Vignesh ...
On 08/03/16 09:49, Jon Hunter wrote:
> The function __spi_pump_messages() is called by spi_pump_messages() and
> __spi_sync(). The function __spi_sync() has an argument 'bus_locked'
> that indicates if it is called with the SPI bus mutex held or not. If
> 'bus_locked' is false
On (03/07/16 17:08), Michal Hocko wrote:
> On Mon 29-02-16 22:02:13, Michal Hocko wrote:
> > Andrew,
> > could you queue this one as well, please? This is more a band aid than a
> > real solution which I will be working on as soon as I am able to
> > reproduce the issue but the patch should help
On mån, 2016-03-07 at 21:15 -0800, Andy Lutomirski wrote:
> Hi all-
>
> I think there are three main types of concerns. First, there might
> be
> some as-yet-unknown semantic issues that would allow privilege
> escalation by users who create user namespaces and then confuse
> something else in
Hi Peter!
On 11/01/16 16:25, Peter Zijlstra wrote:
> Like enable_on_exec, perf_event_enable() event scheduling has problems
> respecting the context hierarchy when trying to schedule events (for
> example, it will try and add a pinned event without first removing
> existing flexible events).
>
>
Commit-ID: bc864af13f34d19c911f5691d87bdacc9ce109f5
Gitweb: http://git.kernel.org/tip/bc864af13f34d19c911f5691d87bdacc9ce109f5
Author: Chris Bainbridge
AuthorDate: Mon, 7 Mar 2016 11:10:00 +0100
Committer: Thomas Gleixner
CommitDate: Tue,
Hi Amitoj,
Thanks for the patches.
Applied only the 7/7 one. In the remaining ones, please remove
also all occurrences of platform_set_drvdata() in the probe()
and pdev_to_gpio() definition from leds-s3c24xx.cm as they will
be no longer required.
Best regards,
Jacek Anaszewski
On 03/07/2016
601 - 700 of 2412 matches
Mail list logo