On Mon 14-03-16 10:37:22, Alan Stern wrote:
> On Mon, 14 Mar 2016, Jan Kara wrote:
>
> > On Fri 11-03-16 12:56:10, Tejun Heo wrote:
> > > Hello, Jan.
> > >
> > > On Thu, Mar 03, 2016 at 10:33:10AM +0100, Jan Kara wrote:
> > > > > Ugh... that's nasty. I wonder whether the right thing to do is mak
On 2016年03月15日 03:23, Eduardo Valentin wrote:
> * PGP Signed by an unknown key
>
> On Fri, Mar 11, 2016 at 11:11:26AM +0800, Wei Ni wrote:
>> Add suspend/resume function in soctherm driver.
>> And enable it for Tegra124 and Tegra210.
>
> I would prefer you either improve the description of chan
On Mon, Mar 14, 2016 at 5:56 PM, Andrey Ryabinin wrote:
> 2016-03-14 13:43 GMT+03:00 Alexander Potapenko :
>
>> +
>> + rec = this_cpu_ptr(&depot_recursion);
>> + /* Don't store the stack if we've been called recursively. */
>> + if (unlikely(*rec))
>> + goto fast_ex
Hi Gustavo,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on next-20160315]
[cannot apply to v4.5]
[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/Gustavo
Following commit broke DW GMAC functionality on AXS10x boards:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e34d65696d2ef13dc32f2a162556c86c461ed763
That's what happens on eth0 up:
--->8
libphy: PHY stmmac-0: not
The patch
regulator: pwm: Prints error number along with detail
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 24 hou
The patch
regulator: mt6323: Fix trivial typo in module description
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 24
The patch
regulator: mt6323: Add support for MT6323 regulator
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 24 hours
On Tue, Mar 15, 2016 at 09:29:12AM +, Mark Brown wrote:
> The patch
>
>regulator: qcom-saw: Add support for SAW regulators
>
> has been applied to the regulator tree at
>
>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
Sorry, this is my scripts not coping with
The patch
regulator: Add document for MT6323 regulator
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 24 hours) and s
The patch
regulator: qcom-saw: Add support for SAW regulators
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 24 hours
* Linus Torvalds wrote:
> On Mon, Mar 14, 2016 at 5:32 AM, Ingo Molnar wrote:
> > +/**
> > + * fetch_or - perform *ptr |= mask and return old value of *ptr
> > + * @ptr: pointer to value
> > + * @mask: mask to OR on the value
> > + *
> > + * cmpxchg based fetch_or, macro so it works for differe
On Tue, Mar 15, 2016 at 09:29:10AM +, Mark Brown wrote:
> The patch
>
>regulator: mt6323: Add support for MT6323 regulator
>
> has been applied to the regulator tree at
>
>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
Sorry, this is my scripts not coping with
Felipe Ferreri Tonello wrote:
> On 11/03/16 23:07, Michal Nazarewicz wrote:
>> I’m also wondering whether it would be beneficial to get rid of buflen
>> all together and use wMaxPacketSie for in endpoints as well? Is that
>> feasible?
>
> Yes, we could just remove the buflen parameter.
>
> The onl
* Peter Zijlstra wrote:
> On Mon, Mar 14, 2016 at 07:44:14PM -0700, Linus Torvalds wrote:
> > On Mon, Mar 14, 2016 at 5:32 AM, Ingo Molnar wrote:
> > > +/**
> > > + * fetch_or - perform *ptr |= mask and return old value of *ptr
> > > + * @ptr: pointer to value
> > > + * @mask: mask to OR on the
On 15/03/2016 10:32, Mark Brown wrote:
> On Tue, Mar 15, 2016 at 09:29:10AM +, Mark Brown wrote:
>> The patch
>>
>>regulator: mt6323: Add support for MT6323 regulator
>>
>> has been applied to the regulator tree at
>>
>>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.g
Linus noticed that the new tick_dep_mask types introduced in:
d027d45d8a17 ("nohz: New tick dependency mask")
... are sloppily defined as 'unsigned long' - which is wasteful
to carry just 4 bits and which may also create suboptimal data
types on 64-bit systems with word alignment padding holes
> + if (!sync_print) {
> + if (printk_thread && !in_panic) {
> + /*
> + * This will wakeup the printing kthread and offload
> + * printing to a schedulable context.
> + */
> + __th
A recent change to the mbus driver added a warning printk that
prints a phys_addr_t using the %x format string, which fails in
case we build with 64-bit phys_addr_t:
drivers/bus/mvebu-mbus.c: In function 'mvebu_mbus_get_dram_win_info':
drivers/bus/mvebu-mbus.c:975:9: error: format '%x' expects arg
On Tue, 2016-03-15 at 11:03 +0100, Arnd Bergmann wrote:
> A recent change to the mbus driver added a warning printk that
> prints a phys_addr_t using the %x format string, which fails in
> case we build with 64-bit phys_addr_t:
Hey Arnd.
This is a bad patch subject, %pad is for a dma_addr_t.
The
Hi Christopher,
On 11/03/16 06:35, Christopher Covington wrote:
> Version 2 of the Server Base System Architecture (SBSAv2) describes the
> Generic UART registers as 32 bits wide. At least one implementation, found
> on the Qualcomm Technologies QDF2432, only supports 32 bit accesses.
> SBSAv3, wh
Implement the stack depot and provide CONFIG_STACKDEPOT.
Stack depot will allow KASAN store allocation/deallocation stack traces
for memory chunks. The stack traces are stored in a hash table and
referenced by handles which reside in the kasan_alloc_meta and
kasan_free_meta structures in the alloca
Signed-off-by: Alexander Potapenko
Acked-by: Andrey Ryabinin
---
lib/test_kasan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/test_kasan.c b/lib/test_kasan.c
index 90ad74f..82169fb 100644
--- a/lib/test_kasan.c
+++ b/lib/test_kasan.c
@@ -294,6 +294,8 @@ static noinline void __init
This patch set implements SLAB support for KASAN
Unlike SLUB, SLAB doesn't store allocation/deallocation stacks for heap
objects, therefore we reimplement this feature in mm/kasan/stackdepot.c.
The intention is to ultimately switch SLUB to use this implementation as
well, which will save a lot of
Rename kmalloc_large_oob_right() to kmalloc_pagealloc_oob_right(), as the
test only checks the page allocator functionality.
Also reimplement kmalloc_large_oob_right() so that the test allocates a
large enough chunk of memory that still does not trigger the page
allocator fallback.
Signed-off-by:
On 02/29/2016 09:48 PM, Paul Gortmaker wrote:
> Fixups here tend to be more all over the map vs. some of the other
> repeated/systematic ones we've seen elsewhere.
>
> We remove module.h from code that isn't doing anything modular at
> all; if they have __init sections, then replace it with init.
Add GFP flags to KASAN hooks for future patches to use.
This patch is based on the "mm: kasan: unified support for SLUB and
SLAB allocators" patch originally prepared by Dmitry Chernenkov.
Signed-off-by: Alexander Potapenko
---
v4: - fix kbuild compilation error (missing parameter for kasan_kmal
Quarantine isolates freed objects in a separate queue. The objects are
returned to the allocator later, which helps to detect use-after-free
errors.
Freed objects are first added to per-cpu quarantine queues.
When a cache is destroyed or memory shrinking is requested, the objects
are moved into th
Add KASAN hooks to SLAB allocator.
This patch is based on the "mm: kasan: unified support for SLUB and
SLAB allocators" patch originally prepared by Dmitry Chernenkov.
Signed-off-by: Alexander Potapenko
---
v3: - minor description changes
- store deallocation info in kasan_slab_free()
v4: -
* Vitaly Kuznetsov wrote:
> When booting Hyper-V Generation 2 guests KASAN reports the following
> out-of-bounds access:
>
> BUG: KASAN: slab-out-of-bounds in fb_is_primary_device+0x58/0x70 at addr
> 880079cf0eb0
> Read of size 8 by task swapper/0/1
> ...
> [] dump_stack+0x63/0x8b
> []
KASAN needs to know whether the allocation happens in an IRQ handler.
This lets us strip everything below the IRQ entry point to reduce the
number of unique stack traces needed to be stored.
Move the definition of __irq_entry to so that the
users don't need to pull in . Also introduce the
__softi
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
- Add the CPU id for the new z13s machine
- Add a s390 specific XOR template for RAID-5 checksumming based on the
XC instructio
Looks like the fimware 8.2 stall has the extra buttons spurious release
bug.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=114321
Cc: sta...@vger.kernel.org
Signed-off-by: Benjamin Tissoires
---
drivers/input/mouse/synaptics.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff
> -Original Message-
> From: Andrew Patterson [mailto:andrew.patter...@hpe.com]
> Sent: Tuesday, March 15, 2016 4:33 AM
> To: Ariel Elior
> Cc: linux-scsi ; linux-kernel ker...@vger.kernel.org>
> Subject: bnx2x: bnx2fc: FC-NPIV table with bad length
>
>
> I see the following error when
* Linus Torvalds wrote:
> On Mon, Mar 14, 2016 at 10:17 AM, Andy Lutomirski wrote:
> >
> > So yes, let's please warn. I'm okay with removing the panic_on_oops
> > thing though. (But if anyone suggests that we should stop OOPSing on
> > bad kernel page faults, I *will* fight back.)
>
> Bad ke
* Andy Lutomirski wrote:
> On Mon, Mar 14, 2016 at 11:40 AM, Linus Torvalds
> wrote:
> > On Mon, Mar 14, 2016 at 11:24 AM, Andy Lutomirski
> > wrote:
> >>
> >> The code in my queue is, literally:
> >>
> >> bool ex_handler_rdmsr_unsafe(const struct exception_table_entry *fixup,
> >>
The newly added synchronous openat support in AIO adds a ki_destruct_fn
function pointer to struct aio_kiocb inside of a CONFIG_AIO_THREAD check
but calls it unconditionally, leading to a build error:
fs/aio.c: In function 'kiocb_free':
fs/aio.c:1101:9: error: 'struct aio_kiocb' has no member name
On Wed, 9 Mar 2016, Balbir Singh wrote:
>
> The previous revision was nacked by Torsten, but compared to the alternatives
> at hand I think we should test this approach. Ideally we want all the
> complexity
> of live-patching in the live-patching code and not in the patch. The other
> option
>
Hello,
I was looking at the following code in the file
drivers/vfio/pci/vfio_pci_intrs.c:
ret = pci_enable_msix_range(pdev, vdev->msix, 1, nvec);
if (ret < nvec) {
if (ret > 0)
pci_disable_msix(pdev);
* Ingo Molnar wrote:
> * Andy Lutomirski wrote:
>
> > On Mon, Mar 14, 2016 at 11:40 AM, Linus Torvalds
> > wrote:
> > > On Mon, Mar 14, 2016 at 11:24 AM, Andy Lutomirski
> > > wrote:
> > >>
> > >> The code in my queue is, literally:
> > >>
> > >> bool ex_handler_rdmsr_unsafe(const struct ex
On Mon, Mar 14, 2016 at 05:03:34PM +, Dr. David Alan Gilbert wrote:
> * Li, Liang Z (liang.z...@intel.com) wrote:
> > >
> > > Hi,
> > > I'm just catching back up on this thread; so without reference to any
> > > particular previous mail in the thread.
> > >
> > > 1) How many of the free p
This reverts commit 85743f1eb34548ba4b056d2f184a3d107a3b8917.
Without this revert, POWER "pseries" KVM guests with a VF passed to a guest
using VFIO fail to bring the driver up:
mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
mlx4_core: Initializing :00:00.0
mlx4_core :00:00.0
On Tue, Mar 15, 2016 at 07:39:31AM +0700, Suravee Suthikulpanit wrote:
> What if I just merge the newly introduced arch/x86/include/perf/amd/iommu.h
> into the include/linux/amd-iommu.h? I do not see the point of having to
> separate things out into two files.
Except that this header has x86-speci
On Tue, Mar 15, 2016 at 12:19 PM, Alexey Kardashevskiy wrote:
> This reverts commit 85743f1eb34548ba4b056d2f184a3d107a3b8917.
>
> Without this revert, POWER "pseries" KVM guests with a VF passed to a guest
> using VFIO fail to bring the driver up:
>
> mlx4_core: Mellanox ConnectX core driver v2.2-
On 2016年03月15日 03:25, Eduardo Valentin wrote:
> * PGP Signed by an unknown key
>
> On Fri, Mar 11, 2016 at 11:11:34AM +0800, Wei Ni wrote:
>> Adds soctherm node for Tegra210, and add cpu,
>> gpu, mem, pllx as thermal-zones. Set critical
>> trip temp for cpu and gpu thermal zone.
>>
>> Signed-off
Commit-ID: 743146db071c4a828159211a295d12ff4f61752f
Gitweb: http://git.kernel.org/tip/743146db071c4a828159211a295d12ff4f61752f
Author: Vitaly Kuznetsov
AuthorDate: Tue, 15 Mar 2016 09:20:33 +0100
Committer: Ingo Molnar
CommitDate: Tue, 15 Mar 2016 11:08:26 +0100
x86/video: Don't assume
On 14/03/16 15:05, Jan Kiszka wrote:
> On 2016-03-14 15:39, Kieran Bingham wrote:
>> On 13/03/16 16:34, Jan Kiszka wrote:
>>> On 2016-03-03 12:41, Kieran Bingham wrote:
lx-mounts will identify current mount points based on the 'init_task'
namespace by default, as we do not yet have a kern
On Tue, Mar 15, 2016 at 10:32:45AM +0100, Ingo Molnar wrote:
> 2) its naming sucks. "fetch_or()" does not really signal that it's a
> fundamentally atomic operation, nor what API family it belongs to.
I disagree there, the fetch-$op naming is widely used for atomic
operations that return the
On Tue, Mar 15, 2016 at 11:40:17AM +0100, Borislav Petkov wrote:
> On Tue, Mar 15, 2016 at 07:39:31AM +0700, Suravee Suthikulpanit wrote:
> > What if I just merge the newly introduced arch/x86/include/perf/amd/iommu.h
> > into the include/linux/amd-iommu.h? I do not see the point of having to
> > s
On Mon, Mar 14, 2016 at 11:49:39AM +0100, Maxime Ripard wrote:
> On Sat, Mar 12, 2016 at 08:52:22AM +0100, Danny Milosavljevic wrote:
> > > The other direction (making two controls which both do the same and
> > > update
> > > each other's value) doesn't seem to be easily available.
> > > Shou
On Mon, Mar 14, 2016 at 03:37:23PM -0600, Toshi Kani wrote:
> Your patch is a simplified version of mine. So, yes, it fixes the Paul's
> issue, but it does not address other issues that my patchset also
> addressed. In specific, I think your patch has the following issues.
You couldnt've structu
On Mon, Mar 14, 2016 at 09:11:16PM -0600, Toshi Kani wrote:
> - pat = PAT(0, WB) | PAT(1, WT) | PAT(2, UC_MINUS) | PAT(3, UC) |
> - PAT(4, WB) | PAT(5, WT) | PAT(6, UC_MINUS) | PAT(7, UC);
> + if (cpu_has_pat) {
Please use on init paths boot_cpu_has(X86_FEATURE_PAT) and on fast p
David,
On 09/03/16 05:32, David Long wrote:
> From: "David A. Long"
>
> Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64.
>
> Signed-off-by: David A. Long
> ---
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/ptrace.h | 31 +++
> arch/arm64/kernel/ptrace.c
While building linux-next the test robot detected that the pci.h was including
two removed header files (pci-dma-compat.h and pci-bridge.h) causing the
process to fail:
http://lists.infradead.org/pipermail/linux-snps-arc/2016-March/000711.html
This patch has the goal to fix the build problem.
Sig
On Tue, Mar 15, 2016 at 10:32:45AM +0100, Ingo Molnar wrote:
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index 969e6704c3c9..851631899352 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -264,7 +264,7 @@ static void tick_nohz_dep_set_all(unsigne
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v4.6-1
For:
- Added support for some new video formats;
- mn88473 DVB frontend driver got promoted from staging;
- several improvements at the VSP1 driver;
- several cleanups and im
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Monday, March 14, 2016 8:00 PM
> To: martin.peter...@oracle.com; james.bottom...@hansenpartnership.com;
> Kashyap Desai; Sumit Saxena; Uday Lingala; James E.J. Bottomley
> Cc: linux-s...@vger.kernel.org; linux-kernel@
> On Mon, Mar 14, 2016 at 05:03:34PM +, Dr. David Alan Gilbert wrote:
> > * Li, Liang Z (liang.z...@intel.com) wrote:
> > > >
> > > > Hi,
> > > > I'm just catching back up on this thread; so without reference
> > > > to any particular previous mail in the thread.
> > > >
> > > > 1) How many
On Tuesday 15 March 2016 04:36 PM, Joao Pinto wrote:
> While building linux-next the test robot detected that the pci.h was including
> two removed header files (pci-dma-compat.h and pci-bridge.h) causing the
> process to fail:
> http://lists.infradead.org/pipermail/linux-snps-arc/2016-March/000711
Hi Bjorn, many thanks for coming back on this
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: 14 March 2016 19:17
> To: Gabriele Paoloni
> Cc: Lorenzo Pieralisi; 'Mark Rutland'; Guohanjun (Hanjun Guo); Wangzhou
> (B); liudongdong (C); Linuxarm; qiujiang; 'bhe
Commit 5f8fc43217a0 ("PCI: Include pci/pcie/Kconfig directly from
pci/Kconfig") in linux-next changed drivers/pci/Kconfig to include
drivers/pci/pcie/Kconfig itself, so that architectures do not need
to source both files themselves. ARC just recently gained PCI support
through commit 6b3fb77998dd (
Hi Marek,
On Fri, Feb 19, 2016 at 5:22 PM, Marek Szyprowski
wrote:
> This patch replaces ARM-specific IOMMU-based DMA-mapping implementation
> with generic IOMMU DMA-mapping code shared with ARM64 architecture. The
> side-effect of this change is a switch from bitmap-based IO address space
> mana
On Tue, 15 Mar 2016 12:22:18 +0300, Andrey Ryabinin said:
> 2016-03-15 12:11 GMT+03:00 Valdis Kletnieks :
> > This config breaks sparse:
> > 4AM is a bad time to figure out who's to blame here
>
> Update your sparse please. Make sure it has d917662d54ba ("lib.c: skip
> --param parameters").
A
This change cleans up style issues in drivers/pci/pcie/Kconfig, in
particular all indentation is now done using tabs, not spaces, and
the definition of PCIEASPM_DEBUG is now separated from the definition
of PCIEASPM with a newline.
Signed-off-by: Andreas Ziegler
---
drivers/pci/pcie/Kconfig | 7
The PM clocks framework requires clients to pass either a con-id or a
valid clk pointer in order to add a clock to a device. Add a new
function of_pm_clk_add_clks() to allows device clocks to be retrieved
from device-tree and populated for a given device. Note that it is
not necessary to make the c
On Tue, Mar 15, 2016 at 4:19 AM, wrote:
>
> Fedora only packaged 0.5.0, which doesn't include the last few
> dozen commits. And they probably won't update until a sparse maintainer
> sticks a v0.5.1 tag on it. I suspect that other distros are similar.
>
> Adding Christopher Li to the recipient
On Fri, 4 Mar 2016, Josh Poimboeuf wrote:
> On Fri, Mar 04, 2016 at 10:53:39AM +0100, Miroslav Benes wrote:
> > There is an #error in asm/livepatch.h for both x86 and s390 in
> > !CONFIG_LIVEPATCH cases. It does not make much sense as pointed out by
> > Michael Ellerman. One can happily include as
On Tuesday 15 March 2016 04:47 PM, Andreas Ziegler wrote:
> Commit 5f8fc43217a0 ("PCI: Include pci/pcie/Kconfig directly from
> pci/Kconfig") in linux-next changed drivers/pci/Kconfig to include
> drivers/pci/pcie/Kconfig itself, so that architectures do not need
> to source both files themselves.
Hi Magnus,
On 15/03/16 11:18, Magnus Damm wrote:
Hi Marek,
On Fri, Feb 19, 2016 at 5:22 PM, Marek Szyprowski
wrote:
This patch replaces ARM-specific IOMMU-based DMA-mapping implementation
with generic IOMMU DMA-mapping code shared with ARM64 architecture. The
side-effect of this change is a s
On 09/03/16 10:24, Neil Armstrong wrote:
> Under the OX810SE, this exact same interface is used as "Reference Peripheral
> Specification" Interrupt Controller, so add a new compatible string.
>
> Signed-off-by: Neil Armstrong
Acked-by: Marc Zyngier
M.
--
Jazz is not dead. It just smel
* Ingo Molnar wrote:
> Subject: [PATCH] atomic: Fix bugs in 'fetch_or()' and rename it to 'xchg_or()'
>
> Linus noticed a couple of problems with the fetch_or() implementation
> introduced
> by 5fd7a09cfb8c ("atomic: Export fetch_or()"):
>
> - Sloppy macro implementation: 'mask' and 'ptr' i
Hello,
On 2016-03-15 12:18, Magnus Damm wrote:
Hi Marek,
On Fri, Feb 19, 2016 at 5:22 PM, Marek Szyprowski
wrote:
This patch replaces ARM-specific IOMMU-based DMA-mapping implementation
with generic IOMMU DMA-mapping code shared with ARM64 architecture. The
side-effect of this change is a swi
PCI-SIG has defined Interface FEh for Base Class 0Ch,
Sub-Class 03h as "USB Device (not host controller)". It is
already being used in various USB device controller drivers
for matching, so converting those to use the definition.
Signed-off-by: Heikki Krogerus
---
drivers/pci/quirks.c
On 3/15/2016 11:38 AM, Vineet Gupta wrote:
> On Tuesday 15 March 2016 04:47 PM, Andreas Ziegler wrote:
>> Commit 5f8fc43217a0 ("PCI: Include pci/pcie/Kconfig directly from
>> pci/Kconfig") in linux-next changed drivers/pci/Kconfig to include
>> drivers/pci/pcie/Kconfig itself, so that architectures
* Peter Zijlstra wrote:
> On Tue, Mar 15, 2016 at 10:32:45AM +0100, Ingo Molnar wrote:
> > 2) its naming sucks. "fetch_or()" does not really signal that it's a
> > fundamentally atomic operation, nor what API family it belongs to.
>
> I disagree there, the fetch-$op naming is widely used f
On Tue, Mar 15, 2016 at 7:10 AM, Viresh Kumar wrote:
> On 12-03-16, 03:05, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> cpufreq_resume() attempts to resync the current frequency with
>> policy->cur for the first online CPU, but first it does that after
>> restarting governors for all
On Tue, Mar 15, 2016 at 12:33 PM, Jon Hunter wrote:
> The PM clocks framework requires clients to pass either a con-id or a
> valid clk pointer in order to add a clock to a device. Add a new
> function of_pm_clk_add_clks() to allows device clocks to be retrieved
> from device-tree and populated fo
* Ingo Molnar wrote:
>
> Linus noticed that the new tick_dep_mask types introduced in:
>
> d027d45d8a17 ("nohz: New tick dependency mask")
>
> ... are sloppily defined as 'unsigned long' - which is wasteful
> to carry just 4 bits and which may also create suboptimal data
> types on 64-bit s
Hi Netanel,
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.5 next-20160315]
[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/Netanel-Belgazal/net-ena-Add-a-driver-for
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
for you to fetch changes up to efbec
On Tue, Mar 15, 2016 at 12:40:06PM +0200, Or Gerlitz wrote:
> "[..] Regarding backward compatibility in SR-IOV, if hypervisor has
> this new code, the virtual OS must be updated. [...]"
Which is broken, we can't break user or guest VM ABIs ever.
On Tue, Mar 15, 2016 at 10:32:45AM +0100, Ingo Molnar wrote:
> +#ifndef xchg_or
> +# define xchg_or(ptr, mask) \
> +({ \
> + typeof(ptr) __ptr = (ptr);
Linus noticed a couple of problems with the fetch_or() implementation introduced
by 5fd7a09cfb8c ("atomic: Export fetch_or()"):
- Sloppy macro implementation: 'mask' and 'ptr' is evaluated multiple times,
which will break if arguments have side effects. Also, it uses
double-underscore temp
2016-03-15 12:27 GMT+03:00 Alexander Potapenko :
> On Mon, Mar 14, 2016 at 5:56 PM, Andrey Ryabinin
> wrote:
>> 2016-03-14 13:43 GMT+03:00 Alexander Potapenko :
>>
>>> +
>>> + rec = this_cpu_ptr(&depot_recursion);
>>> + /* Don't store the stack if we've been called recursively. */
>>>
On Thu, 10 Mar 2016, Jiri Kosina wrote:
> On Wed, 9 Mar 2016, Petr Mladek wrote:
>
> > LivePatch framework deserves some documentation, definitely.
> > This is an attempt to provide some basic info. I hope that
> > it will be useful for both LivePatch producers and also
> > potential developers o
Hi Eduardo,
On Thursday 10 March 2016 03:05 AM, Eduardo Valentin wrote:
This changes the driver to use the devm_ version
of thermal_zone_of_sensor_register and cleans
up the local points and unregister calls.
Boot tested on dra7xx-evm, dra72x-evm, pandaboard-es.
Also checked the thermal sysf
* Ingo Molnar wrote:
> But IMHO this really highlights a fundamental weakness of all this macro
> magic,
> it's all way too fragile.
>
> Why don't we introduce a boring family of APIs:
>
> cmpxchg_8()
> cmpxchg_16()
> cmpxchg_32()
> cmpxchg_64()
>
> xchg_or_32(
Hi Marek, Arnd,
On 19/02/16 10:30, Arnd Bergmann wrote:
On Friday 19 February 2016 09:22:44 Marek Szyprowski wrote:
This patch replaces ARM-specific IOMMU-based DMA-mapping implementation
with generic IOMMU DMA-mapping code shared with ARM64 architecture. The
side-effect of this change is a swi
010) attached,
this results in the following splat at boot time:
BUG: unable to handle kernel NULL pointer dereference at 0014
IP: [] usb_audio_probe+0x2cc/0x9a0 [snd_usb_audio]
Oops: [#1] SMP
[...]
CPU: 2 PID: 696 Comm: systemd-udevd Not tainted 4.5.0-next-20160315 #13
* Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> > But IMHO this really highlights a fundamental weakness of all this macro
> > magic,
> > it's all way too fragile.
> >
> > Why don't we introduce a boring family of APIs:
> >
> > cmpxchg_8()
> > cmpxchg_16()
> > cmpxchg_32()
>
Hello Tomeu
On 3/15/2016 8:23 AM, Tomeu Vizoso wrote:
Thanks.
Btw, I have rebased on top of 4.5 this morning and I have noticed that
88f8b1bb41c6 ("stmmac: Fix 'eth0: No PHY found' regression") got in
there, so I guess we have now a bunch of boards with broken network on
that release:(
This
Hi Christoffer,
On 09/03/16 05:39, Christoffer Dall wrote:
On Tue, Mar 08, 2016 at 11:29:29AM +, Julien Grall wrote:
Even though all the variables aren't marked with __initdata, they are
only used during initialization. So the structure is marked with
__initdata.
Not sure I understand thi
obe+0x2cc/0x9a0 [snd_usb_audio]
> Oops: [#1] SMP
> [...]
> CPU: 2 PID: 696 Comm: systemd-udevd Not tainted 4.5.0-next-20160315 #13
> Hardware name: Dell Inc. Latitude E6540/0725FP, BIOS A10 06/26/2014
> task: 88021c88d7c0 ti: 88003d5b task.ti: 88003d5b
>
On Tue, Mar 15, 2016 at 01:08:35PM +0100, Ingo Molnar wrote:
> * Peter Zijlstra wrote:
>
> > On Tue, Mar 15, 2016 at 10:32:45AM +0100, Ingo Molnar wrote:
> > > 2) its naming sucks. "fetch_or()" does not really signal that it's a
> > > fundamentally atomic operation, nor what API family it be
Hi Linus,
The following changes since commit 18558cae0272f8fd9647e69d3fec1565a7949865:
Linux 4.5-rc4 (2016-02-14 13:05:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git tags/fbdev-4.6
for you to fetch changes up to 13aa38e291bdd
On 03/14/2016 07:25 PM, Paolo Bonzini wrote:
On 14/03/2016 08:41, Suravee Suthikulpanit wrote:
Any particular reason why you do not recommend the use of bit field?
1) The current coding style is generally not using bitfields
2) Having to review patches that change working code unrelated t
在 2016/3/11 4:27, Andy Shevchenko 写道:
> On Thu, Mar 10, 2016 at 9:09 PM, Alan Tull wrote:
>> On Fri, Mar 4, 2016 at 1:44 AM, qiujiang wrote:
>>> This patch converts device node to fwnode in
>>> dwapb_port_property for designware gpio driver,
>>> so as to provide a unified data structure for DT
>>
On Tue, 15 Mar 2016, Jiri Kosina wrote:
> cleaner_kthread() is not marked freezable, and therefore calling
> try_to_freeze() in its context is a pointless no-op.
>
> In addition to that, as has been clearly demonstrated by 80ad623edd2d
> ("Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()")
Some versions of GCC, reportedly before 4.8, fail with
arch/powerpc/mm/8xx_mmu.c:139:2: error: memory input 1 is not directly
addressable
Change the one-element array into a simple variable to avoid this.
Signed-off-by: Christophe Leroy
Cc: Scott Wood
---
Verified with GCC 4.4.4 and GCC 4.8.3
Hello,
I am not sure whether there is some to fix or not, since it can be
triggered only by root. But still if I run the following program
several times in a row, whole machine becomes unusable for several
minutes (ssh, ps and pretty much everything hangs):
// autogenerated by syzkaller (http://
101 - 200 of 732 matches
Mail list logo
