On Friday 20 January 2017 07:16 PM, Sekhar Nori wrote:
> On Friday 13 January 2017 03:30 PM, Bartosz Golaszewski wrote:
>> The aemif driver can now access struct of_dev_auxdata (using platform
>> data).
>>
>> Add the device id to the clock lookup table for the nand clock and
>> create a separate lo
Eduardo,
On Friday 06 January 2017 11:31 AM, Keerthy wrote:
Technical Reference Manual [1] mandates that software should
not be configuring the thermal shutdown thresholds. Hence
removing TSHUT_CONFIG.
Any comments on this?
- Keerthy
[1] http://www.ti.com/lit/ug/sprui30b/sprui30b.pdf
Keert
On Mon, Jan 23, 2017 at 01:18:41PM +0100, Arnd Bergmann wrote:
> One line was apparently pasted incorrectly during a new feature patch:
>
> drivers/net/phy/marvell.c:2090:15: error: initialized field overwritten
> [-Werror=override-init]
>.features = PHY_GBIT_FEATURES,
>
> I'm removing the e
On 01/20/2017 12:09 AM, Thomas Gleixner wrote:
On Thu, 19 Jan 2017, Denys Vlasenko wrote:
A lot of asm-optimized routines in arch/x86/crypto/ keep its
constants in .data. This is wrong, they should be on .rodata.
Mnay of these constants are the same in different modules.
For example, 128-bit s
On Jan 23 2017 or thereabouts, Bastien Nocera wrote:
> On Tue, 2017-01-17 at 15:35 +0100, Benjamin Tissoires wrote:
> > Hey guys,
> >
> > I tried to revive the in-kernel battery support for HID++ devices.
> > I was thinking of doing just a few patches, but in the end I had to
> > do
> > cleanups a
From: Markus Elfring
Date: Mon, 23 Jan 2017 14:54:26 +0100
Remove a condition check which is unnecessary at the end
because this source code place should usually only be reached
with a non-zero pointer.
Signed-off-by: Markus Elfring
---
tools/perf/util/probe-event.c | 6 ++
1 file changed,
From: Geliang Tang
Use nilfs_btree_node_size() instead of open-coding.
Signed-off-by: Geliang Tang
Signed-off-by: Ryusuke Konishi
---
fs/nilfs2/btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nilfs2/btree.c b/fs/nilfs2/btree.c
index 2e315f9..9c7ea17 100644
--- a
On Mon, 23 Jan 2017 15:14:51 +
Matthew Wilcox wrote:
> > I maintain my own stack of "linuxdoc" with a python version
> > of the kernel-doc script (hosted on github). It uses the same
> > regexes as the perl version (using a python rewrite here has some
> > other benefits, one you will see bel
Hi Andrew,
Please queue the following changes for the next merge window:
Geliang Tang (2):
nilfs2: use nilfs_btree_node_size()
nilfs2: use i_blocksize()
where "nilfs2: use i_blocksize()" requires the patch "fs: add
i_blocksize()" which resides in -mm tree.
Meanwhile "nilfs2: use nil
From: Geliang Tang
Since i_blocksize() helper has been defined in fs.h, use it instead
of open-coding.
Signed-off-by: Geliang Tang
Signed-off-by: Ryusuke Konishi
---
fs/nilfs2/alloc.c | 2 +-
fs/nilfs2/btree.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/nilfs2/al
> .install
> linux/genwqe/.install
> linux/genwqe/..install.cmd
...
If these aren't just a mistake in your list the patches need to be
fixed not to install this build system internal file.
And I'm pretty sure I already pointed this out last time.
From: Markus Elfring
Date: Mon, 23 Jan 2017 15:10:19 +0100
Remove an error code assignment which is redundant in an if branch for
the handling of a memory allocation failure because the same value was set
for the local variable "err" before.
Signed-off-by: Markus Elfring
---
tools/perf/util/pr
From: Markus Elfring
Date: Mon, 23 Jan 2017 15:43:13 +0100
A local variable was set to an error code before a concrete error situation
was detected. Thus move the corresponding assignment into an if branch
to indicate a software failure there.
This issue was detected by using the Coccinelle soft
On Fri, Jan 20, 2017 at 12:05:13PM -0500, Nayna Jain wrote:
> The current TPM 2.0 device driver extends only the SHA1 PCR bank
> but the TCG Specification[1] recommends extending all active PCR
> banks, to prevent malicious users from setting unused PCR banks with
> fake measurements and quoting th
From: Markus Elfring
Date: Mon, 23 Jan 2017 15:56:31 +0100
A local variable was set to an error code before a concrete error situation
was detected. Thus move the corresponding assignment into an if branch
to indicate a software failure there.
This issue was detected by using the Coccinelle soft
From: Markus Elfring
Date: Mon, 23 Jan 2017 16:08:21 +0100
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Delete an unnecessary check in try_to_find_absolute_address()
Delete an unnecessary assignment in try_to_find_absolute_address()
On 01/23/2017 07:06 AM, Alexander Potapenko wrote:
> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
> uninitialized memory in cfq_init_cfqq():
>
> ==
> BUG: KMSAN: use of unitialized memory
> ...
> Call Trace
2017-01-23 16:17 GMT+01:00 Sekhar Nori :
> On Friday 20 January 2017 07:16 PM, Sekhar Nori wrote:
>> On Friday 13 January 2017 03:30 PM, Bartosz Golaszewski wrote:
>>> The aemif driver can now access struct of_dev_auxdata (using platform
>>> data).
>>>
>>> Add the device id to the clock lookup tabl
Allow the user to communicate with the tasklet through the atomic state
field by assigning a bit for their use. This can be used, for example,
to differentiate between a tasklet called following an irq or from
process context, where some hardware state may only be valid after the
irq.
Signed-off-b
On 01/23/2017 12:28 AM, tip-bot for Kevin Hao wrote:
> x86/fpu: Set the xcomp_bv when we fake up a XSAVES area
>
> I got the following calltrace on a Apollo Lake SoC with 32-bit kernel:
...
> --- a/arch/x86/kernel/fpu/xstate.c
> +++ b/arch/x86/kernel/fpu/xstate.c
> @@ -1070,6 +1070,7 @@ int copyi
buffered_rmqueue removes a page from a given zone and uses the per-cpu
list for order-0. This is fine but a hypothetical caller that wanted
multiple order-0 pages has to disable/reenable interrupts multiple
times. This patch structures buffere_rmqueue such that it's relatively
easy to build a bulk
alloc_pages_nodemask does a number of preperation steps that determine
what zones can be used for the allocation depending on a variety of
factors. This is fine but a hypothetical caller that wanted multiple
order-0 pages has to do the preparation steps multiple times. This patch
structures __alloc
Many workloads that allocate pages are not handling an interrupt at a
time. As allocation requests may be from IRQ context, it's necessary to
disable/enable IRQs for every page allocation. This cost is the bulk
of the free path but also a significant percentage of the allocation
path.
This patch a
This is rebased on top of mmotm to handle collisions with Vlastimil's
series on cpusets and premature OOMs.
Changelog since v4
o Protect drain with get_online_cpus
o Micro-optimisation of stat updates
o Avoid double preparing a page free
Changelog since v3
o Debugging check in allocation path
o M
On Thu, Jan 19, 2017 at 04:12:27PM -0800, Joshua Clayton wrote:
> Describe a cyclone-ps-spi devicetree entry, required features
>
> Signed-off-by: Joshua Clayton
> ---
> .../bindings/fpga/altera-passive-serial.txt| 25
> ++
> 1 file changed, 25 insertions(+)
> creat
The per-cpu page allocator can be drained immediately via drain_all_pages()
which sends IPIs to every CPU. In the next patch, the per-cpu allocator
will only be used for interrupt-safe allocations which prevents draining
it from IPI context. This patch uses workqueues to drain the per-cpu
lists ins
On Tue, Nov 29, 2016 at 07:14:45PM +0300, Alexander Kochetkov wrote:
> Property set to '"rockchip,rk3228-timer", "rockchip,rk3288-timer"'
> to match devicetree bindings.
>
> Signed-off-by: Alexander Kochetkov
> ---
> arch/arm/boot/dts/rk3228-evb.dts |4
> 1 file changed, 4 insertions(+)
On 01/23/2017 08:33 AM, Chris Wilson wrote:
> Allow the user to communicate with the tasklet through the atomic state
> field by assigning a bit for their use. This can be used, for example,
> to differentiate between a tasklet called following an irq or from
> process context, where some hardware
Guess I forget to add one of the platform/chrome maintainers, as only
his ack is pending for this series, cc'ing Benson Leung
Thanks,
Enric
2017-01-23 13:14 GMT+01:00 Lee Jones :
> On Thu, 19 Jan 2017, Enric Balletbo i Serra wrote:
>
>> From: Stephen Barber
>>
>> If the EC supports RTC host co
From: Steffen Klassert
Date: Mon, 23 Jan 2017 10:35:17 +0100
> So this creates new incompatibilities what is another argument against
> this approach. If you really need this, try to implement a full compat
> layer. I think this is the only sane solution for this.
A full compat layer is the only
On Mon, Jan 23, 2017 at 4:30 PM, Jens Axboe wrote:
> On 01/23/2017 07:06 AM, Alexander Potapenko wrote:
>> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
>> uninitialized memory in cfq_init_cfqq():
>>
>> ==
>
On Fri, Jan 20, 2017 at 07:02:08PM +0530, Sekhar Nori wrote:
> Hi Rob,
>
> On Friday 20 January 2017 04:51 PM, Bartosz Golaszewski wrote:
> > Add DT bindings for the TI DA850 AHCI SATA controller.
> >
> > Signed-off-by: Bartosz Golaszewski
>
> Could you ack this binding?
First I'm seeing it th
On 01/23/2017 08:49 AM, Alexander Potapenko wrote:
> On Mon, Jan 23, 2017 at 4:30 PM, Jens Axboe wrote:
>> On 01/23/2017 07:06 AM, Alexander Potapenko wrote:
>>> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
>>> uninitialized memory in cfq_init_cfqq():
>>>
>>> ==
Mark when we run the execlist tasklet following the interrupt, so we
don't probe a potentially uninitialised register when submitting the
contexts multiple times before the hardware responds.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i915_irq.c | 7 +--
drivers/gpu/drm/i91
On Mon, Jan 23, 2017 at 06:37:18AM +, Matthew Wilcox wrote:
> Wow, DAX devices look painful and awful. I certainly don't want to be
> exposing the memory fronted by my network filesystem to userspace to
> access. That just seems like a world of pain and bad experiences.
So what is your inter
On Mon, 23 Jan 2017, Jens Axboe wrote:
> On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > Allow the user to communicate with the tasklet through the atomic state
> > field by assigning a bit for their use. This can be used, for example,
> > to differentiate between a tasklet called following an irq
On Monday 23 January 2017 09:02 PM, Bartosz Golaszewski wrote:
> 2017-01-23 16:17 GMT+01:00 Sekhar Nori :
>> On Friday 20 January 2017 07:16 PM, Sekhar Nori wrote:
>>> On Friday 13 January 2017 03:30 PM, Bartosz Golaszewski wrote:
The aemif driver can now access struct of_dev_auxdata (using pl
On Sun, Jan 22, 2017 at 11:10:04PM -0800, Dan Williams wrote:
> How about we solve the copy_from_user() abuse first before we hijack
> this thread for some future feature that afaics has no patches posted
> yet.
Solving copy_from_user abuse first sounds perfectly fine to me. But
please do so with
On Sun, Jan 22, 2017 at 09:30:23AM -0800, Dan Williams wrote:
> So are you saying we need a way to go from a block_device inode to a
> dax_device inode and then look up the dax_operations from there?
>
> A filesystem, if it so chooses, could mount on top of the dax_device
> inode directly?
Senten
On Mon, Jan 23, 2017 at 1:55 PM, Vlastimil Babka wrote:
> On 01/23/2017 01:16 PM, Arnd Bergmann wrote:
>> To be honest, I can't figure that out either, maybe it is or
>> maybe not,
>
>
> Seems the report is correct and not false positive, in scenario when we goto
> nopage before the assignment, a
Le 23/01/2017 à 16:25, Christoph Hellwig a écrit :
>> .install
>
>> linux/genwqe/.install
>> linux/genwqe/..install.cmd
>
> ...
>
> If these aren't just a mistake in your list the patches need to be
> fixed not to install this build system internal file.
>
> And I'm pretty sure I already pointe
2017-01-23 17:06 GMT+03:00 Alexander Potapenko :
> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
> uninitialized memory in cfq_init_cfqq():
>
> ==
> BUG: KMSAN: use of unitialized memory
> ...
> Call Trace:
>
For a GICv2 (which happens to be virtualization capable), the
architecture mandates the following regions:
GICD: 4kB
GICC: 8kB
GICH: 8kB
GICV: 8kB
Unfortunately, I made a mistake in one of the examples contained in
the DT binding document, and e
Since everybody copied my own mistake from the DT binding example,
let's address all the offenders in one swift go.
Most of them got the CPU interface size wrong (4kB, while it should
be 8kB), except for both keystone platforms which got the control
interface wrong (4kB instead of 8kB).
In a few
The joys of copy/paste: the example of a virtualization capable GIC
in the DT binding was wrong, and propagated to dozens of platforms.
By having a GICC region that is only 4kB (instead of 8kB), we
end-up not being able to access the GICC_DIR register which is on
the second page.
Oh well. Let's fi
Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov:
> On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote:
>> Hello,
>>
>> The following program triggers WARNING in kvm_apic_accept_events:
>> https://gist.githubusercontent.com/dvyukov/95b845a2e637485568ea1ef181a72370/raw/d90717dd67128b21715c5e794568a16
On 01/23, Pavel Tikhomirov wrote:
>
> >IOW. Currently CRIU can't restore the process tree with the same
> >has_child_subreaper bits if some process forks before
> >prctl(PR_SET_CHILD_SUBREAPER). It restores the tree as if prctl()
> >was called before the 1st fork.
> >
> >So you change the semantics
Hi,
I could use some help verifying an use-after-free bug that I am seeing
after the new direct I/O work went in.
When issuing a direct write io using libaio, a bio is referenced in the
blkdev_direct_IO path, and then put again in the blkdev_bio_end_io path.
However, there is a case where the bio
Add a test case for cancelling the sync fallback mechanism.
Signed-off-by: Luis R. Rodriguez
---
tools/testing/selftests/firmware/fw_fallback.sh | 32 +
1 file changed, 32 insertions(+)
diff --git a/tools/testing/selftests/firmware/fw_fallback.sh
b/tools/testing/selftes
This simplifies init and exit.
Signed-off-by: Luis R. Rodriguez
---
lib/test_firmware.c | 35 +++
1 file changed, 11 insertions(+), 24 deletions(-)
diff --git a/lib/test_firmware.c b/lib/test_firmware.c
index 1cb9bf9eb41f..38cc188c4d3c 100644
--- a/lib/test_firmw
We have no custom fallback mechanism test interface. Provide one.
This tests both the custom fallback mechanism and cancelling the
it.
Signed-off-by: Luis R. Rodriguez
---
lib/test_firmware.c | 45
tools/testing/selftests/firmware/fw_fallback.sh | 68
Since commit 5d47ec02c37ea632398cb251c884e3a488dff794
("firmware: Correct handling of fw_state_wait() return value")
fw_load_abort(fw_priv) could be called twice and lead us to a
kernel crash. This happens only when the firmware fallback mechanism
(regular or custom) is used. The fallback mechanism
Calling it user mode helper only creates confusion.
Signed-off-by: Luis R. Rodriguez
---
tools/testing/selftests/firmware/Makefile| 2 +-
.../testing/selftests/firmware/{fw_userhelper.sh => fw_fallback.sh} | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
Am Montag, 23. Januar 2017, 16:40:46 CET schrieb Daniel Lezcano:
> On Tue, Nov 29, 2016 at 07:14:45PM +0300, Alexander Kochetkov wrote:
> > Property set to '"rockchip,rk3228-timer", "rockchip,rk3288-timer"'
> > to match devicetree bindings.
> >
> > Signed-off-by: Alexander Kochetkov
> > ---
> >
Hello Daniel!
:
> +
> +&timer {
> + compatible = "rockchip,rk3228-timer", "rockchip,rk3288-timer";
> +};
> 23 янв. 2017 г., в 18:40, Daniel Lezcano
> написал(а):
>
> I'm not sure this is correct, to which timer &timer will refer ?
>
>timer {
>compatible = "arm,armv
On Mon, Jan 23, 2017 at 04:59:32PM +0100, Thomas Gleixner wrote:
> On Mon, 23 Jan 2017, Jens Axboe wrote:
>
> > On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > > Allow the user to communicate with the tasklet through the atomic state
> > > field by assigning a bit for their use. This can be used,
Am Dienstag, 29. November 2016, 19:14:48 CET schrieb Alexander Kochetkov:
> arm-global-timer can provide clockevents, clocksource and shed_clock. But
> on rk3188 platform it provide only clocksource and shed_clock. clockevents
> from arm-global-timer is not used by kernel because there is another
On Mon, Dec 26, 2016 at 11:21:36PM +0100, Lukasz Majewski wrote:
> The commit a55944ca82d2
> ("backlight: update bd state & fb_blank properties when necessary")
> has posed some extra restrictions on blanking and unblanking frame buffer
> device.
>
> Unfortunately, pwm_bl driver's probe did not i
On Mon, 2017-01-23 at 16:09 +0200, Jarkko Sakkinen wrote:
> On Sun, Jan 22, 2017 at 01:36:28PM -0800, James Bottomley wrote:
> > On Sun, 2017-01-22 at 23:04 +0200, Jarkko Sakkinen wrote:
> > > On Sun, Jan 22, 2017 at 11:01:07PM +0200, Jarkko Sakkinen wrote:
> > > > On Sun, Jan 22, 2017 at 10:30:55P
On Monday, January 23, 2017 10:08:53 AM CET Jens Wiklander wrote:
> On Fri, Jan 20, 2017 at 05:57:51PM +0100, Arnd Bergmann wrote:
> > On Thursday, January 19, 2017 3:56:23 PM CET Jens Wiklander wrote:
> > > On Wed, Jan 18, 2017 at 05:28:17PM +0100, Arnd Bergmann wrote:
> > > Does the platform dev
On Mon, Jan 23, 2017 at 5:03 PM, Andrey Ryabinin wrote:
> 2017-01-23 17:06 GMT+03:00 Alexander Potapenko :
>> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
>> uninitialized memory in cfq_init_cfqq():
>>
>> =
This will make further changes easier to review.
Signed-off-by: Luis R. Rodriguez
---
lib/test_firmware.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/lib/test_firmware.c b/lib/test_firmware.c
index a3e8ec3fb1c5..1cb9bf9eb41f 100644
--- a/lib/test_firmware.c
+
Some distributions (Debian, OpenSUSE) have a udev rule in place to cancel
all fallback mechanism uevents immediately. This would obviously
make it hard to test against the fallback mechanism test interface,
so we need to check for this.
Signed-off-by: Luis R. Rodriguez
---
tools/testing/selftest
A kernel crash has been reported by a few folks on cancelling the
firmware fallback mechanism introduced by some new code changes in
v4.10. Testing this is not easy as most distributions disable
the option to always use the fallback mechanism by default
(CONFIG_FW_LOADER_USER_HELPER_FALLBACK), and
On Monday, January 23, 2017 4:19:41 PM CET Andrew Lunn wrote:
> On Mon, Jan 23, 2017 at 01:18:41PM +0100, Arnd Bergmann wrote:
> > One line was apparently pasted incorrectly during a new feature patch:
> >
> > drivers/net/phy/marvell.c:2090:15: error: initialized field overwritten
> > [-Werror=ov
On Mon, Jan 23, 2017 at 11:04:22AM +0100, Marc Dietrich wrote:
> Hello Dmitry,
>
> Am Sonntag, 22. Januar 2017, 23:43:47 CET schrieb Dmitry Torokhov:
> > To have expected effect the __initdata attribute should go after variable
> > name and before initializer.`
> >
> > Signed-off-by: Dmitry Torok
On Tue, Nov 29, 2016 at 07:14:49PM +0300, Alexander Kochetkov wrote:
> The patch move ce field out of struct bc_timer into struct
> rk_clock_event_device and rename struct bc_timer to struct rk_timer.
Why ?
>
> Use CXGB3_... instead of CXBG3_...
>
> Signed-off-by: Nicolas Iooss
Acked-by: Steve Wise
On Fri, Jan 20, 2017 at 08:46:40PM +, Jayachandran C wrote:
> Add documentation for Cavium ThunderX2 CN99XX ARM64 processor family.
> The processor core will use cavium,thunder2 as ID and the SoC will use
> cavium,thunder-99xx
>
> Signed-off-by: Jayachandran C
> ---
> Documentation/devicetre
> Great question! I have sent out patches for a couple of actual bugs that
> came from this warning in the past few months.
>
> I still have a couple of patches that I have not sent out so far,
> I think they are all false-positives, and I have not found a good
> workaround for most of them other
On Fri 2017-01-20 15:26:06, Mel Gorman wrote:
> On Fri, Jan 20, 2017 at 03:26:05PM +0100, Vlastimil Babka wrote:
> > > @@ -2392,8 +2404,24 @@ void drain_all_pages(struct zone *zone)
> > > else
> > > cpumask_clear_cpu(cpu, &cpus_with_pcps);
> > > }
> > > - on_each_cpu_m
On 23/01/2017 17:03, David Hildenbrand wrote:
> Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov:
>> On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> The following program triggers WARNING in kvm_apic_accept_events:
>>> https://gist.githubusercontent.com/dvyukov/95b845a2e6374
Hi,
* Tony Lindgren [170105 16:45]:
> Many Motorola phones like droid 4 are using a custom PMIC called CPCAP
> or 6556002. We can support it's core features quite easily with regmap_spi
> and regmap_irq.
>
> The children of cpcap, such as regulators, ADC and USB, can be just regular
> device dri
On Mon, Jan 23, 2017 at 11:05:49AM +0100, Andrzej Hajda wrote:
> Ultra HD modes requires clock ticking at increased rate.
>
> Signed-off-by: Andrzej Hajda
> ---
> v2: long lines wrapped
> v3: moved assigned clocks to cmu_disp node in tm2-common
> ---
> arch/arm64/boot/dts/exynos/exynos5433-tm2-c
available in the git repository at:
git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20170123
for you to fetch changes up to c659af78eb7b7d7be40f23d9d97bde58eb1368ac:
tpm: Check size of response before accessing data (2017-01-23 18:28:18 +0200
Radim Krcmar writes:
> 2017-01-19 15:16+0100, Vitaly Kuznetsov:
>> With TimeSync version 4 protocol support we started updating system time
>> continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
>> there is a time sample from the host which triggers do_settimeofday[64]().
>
On 01/23/2017 08:49 PM, Jarkko Sakkinen wrote:
On Fri, Jan 20, 2017 at 12:05:13PM -0500, Nayna Jain wrote:
The current TPM 2.0 device driver extends only the SHA1 PCR bank
but the TCG Specification[1] recommends extending all active PCR
banks, to prevent malicious users from setting unused PCR
On Sun, Jan 22, 2017 at 04:16:48PM +0800, Baoyou Xie wrote:
> This patch adds watchdog controller driver for ZTE's zx2967 family.
>
> Signed-off-by: Baoyou Xie
Hello Baoyou,
Please see comments below.
Thanks,
Mathieu
> ---
> drivers/watchdog/Kconfig | 10 ++
> drivers/watchdog/Makefile
Daniel, thanks for reviewing patches!
> 23 янв. 2017 г., в 19:26, Daniel Lezcano
> написал(а):
>
> On Tue, Nov 29, 2016 at 07:14:49PM +0300, Alexander Kochetkov wrote:
>> The patch move ce field out of struct bc_timer into struct
>> rk_clock_event_device and rename struct bc_timer to struct rk_
(Re-submitting this patch set originally created by Leonard Crestez,
possibly abandoned by Leonard due to a change in employment)
When using devicetree, stuff like i2c_client.name or spi_device.modalias
is initialized to the first DT compatible id with the vendor prefix
stripped. Since some driver
From: Crestez Dan Leonard
When using devicetree i2c_board_info.type is set to the compatible
string with the vendor prefix removed. For I2C devices described via
ACPI the i2c_board_info.type string is set to the ACPI device name. When
using ACPI and DT ids this string ends up something like "PRP0
From: Crestez Dan Leonard
When using devicetree stuff like i2c_client.name or spi_device.modalias
is initialized to the first DT compatible id with the vendor prefix
stripped. Since some drivers rely on this try to replicate it when using
ACPI with DT ids.
Signed-off-by: Crestez Dan Leonard
Sig
From: Crestez Dan Leonard
When using devicetree spi_device.modalias is set to the compatible
string with the vendor prefix removed. For SPI devices described via
ACPI the spi_device.modalias string is initialized by acpi_device_hid.
When using ACPI and DT ids this string ends up something like "P
From: Kevin Cernekee
> Sent: 21 January 2017 00:05
> Several of the xfrm netlink and setsockopt() interfaces are not usable
> from a 32-bit binary running on a 64-bit kernel due to struct padding
> differences. This has been the case for many, many years[0]. This
> patch series deprecates the bro
On Mon, Jan 23, 2017 at 01:44:32AM +0200, Jarkko Sakkinen wrote:
> From: James Bottomley
>
> Signed-off-by: James Bottomley
>
I really think we should not use the ugly read/write interface for any
new things.
Still unconvinced we should add a new cdev at this point.. But seeing
seesion support
Since version 3.0.0 of the SMBIOS specification, there can be
multiple entry points in memory, pointing to one or two DMI tables.
If both a 32-bit ("_SM_") entry point and a 64-bit ("_SM3_") entry
point are present, the specification requires that the latter points
to a table which is a super-set o
On Fri, Jan 20, 2017 at 11:21:01PM +0100, Andreas Färber wrote:
> Enforce groupment by SoCs and order alphabetically within the group
> (with some exceptions). This should facilitate adding new boards.
>
> Signed-off-by: Andreas Färber
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt |
On Fri, Jan 20, 2017 at 11:21:04PM +0100, Andreas Färber wrote:
> bcrmf -> brcmf
>
> Fixes: ab3943fe57a2 ("ARM64: dts: meson-gxbb: Add P20x Wifi SDIO support")
> Cc: Neil Armstrong
> Signed-off-by: Andreas Färber
> ---
> arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi | 2 +-
> 1 file changed,
On Mon, Jan 23, 2017 at 05:29:20PM +0100, Petr Mladek wrote:
> On Fri 2017-01-20 15:26:06, Mel Gorman wrote:
> > On Fri, Jan 20, 2017 at 03:26:05PM +0100, Vlastimil Babka wrote:
> > > > @@ -2392,8 +2404,24 @@ void drain_all_pages(struct zone *zone)
> > > > else
> > > >
On Fri, Jan 20, 2017 at 11:21:10PM +0100, Andreas Färber wrote:
> Sort nodes referenced by label alphabetically.
Seems to be pointless churn.
>
> Signed-off-by: Andreas Färber
> ---
> arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 76
> ++---
> 1 file changed, 38 insert
gcc cannot track the combined state of the 'mask' variable across the
barrier in pgdat_resize_unlock() at compile time, so it warns that we
can run into undefined behavior:
mm/sparse.c: In function 'section_deactivate':
mm/sparse.c:802:7: error: 'early_section' may be used uninitialized in this
f
And this discussion reminds me again that I do not understand how setns()
and PR_SET_CHILD_SUBREAPER should play together... Add cc's.
Suppose we have a process P in the root namespace and another namespace X.
P does setns() and enters the X namespace.
P forks a child C.
C forks a grandchild G.
On Mon, Jan 23, 2017 at 03:58:37PM +0100, Nicolas Dichtel wrote:
> This header file is exported, thus move it to uapi.
Why? Why is this damn thing exported in the first place?
The moment we decide to change an MSR name or even remove it from that
file, we break userspace. And what for, because us
Am 23.01.2017 um 17:52 schrieb Rob Herring:
> On Fri, Jan 20, 2017 at 11:21:10PM +0100, Andreas Färber wrote:
>> Sort nodes referenced by label alphabetically.
>
> Seems to be pointless churn.
We are constantly adding new nodes, so this avoids duplicates, mismerges
and uncertainties of where thin
Am 23.01.2017 um 17:50 schrieb Rob Herring:
> On Fri, Jan 20, 2017 at 11:21:04PM +0100, Andreas Färber wrote:
>> bcrmf -> brcmf
>>
>> Fixes: ab3943fe57a2 ("ARM64: dts: meson-gxbb: Add P20x Wifi SDIO support")
>> Cc: Neil Armstrong
>> Signed-off-by: Andreas Färber
>> ---
>> arch/arm64/boot/dts/am
From: David Laight
Date: Mon, 23 Jan 2017 16:45:39 +
> Provided you've got the length of the user's buffer the compat code
> ought to be trivial (if tedious).
Wireless guys had to deal with a similar problem with nl80211.
You don't know who is going to get the message when you build it,
bec
On Mon, Jan 23, 2017 at 04:09:42PM +0200, Jarkko Sakkinen wrote:
> On Sun, Jan 22, 2017 at 01:36:28PM -0800, James Bottomley wrote:
> > On Sun, 2017-01-22 at 23:04 +0200, Jarkko Sakkinen wrote:
> > > On Sun, Jan 22, 2017 at 11:01:07PM +0200, Jarkko Sakkinen wrote:
> > > > On Sun, Jan 22, 2017 at 10
On Mon, Jan 23, 2017 at 07:36:20AM -0800, Dave Hansen wrote:
> The kernel xsave buffer should *ALWAYS* have the
> XCOMP_BV_COMPACTED_FORMAT bit set. It should have been set before the
> copyin and it should be set when it's finished.
>
> The best fix here would be not to paper over the issue in t
On Mon, 2017-01-23 at 01:44 +0200, Jarkko Sakkinen wrote:
> This patch set adds support for TPM spaces that provide a context
> for isolating and swapping transient objects. The content does
> not yet include support for policy and HMAC sessions.
>
> There's a test script for trying out TPM spaces
Hello,
On Fri, Jan 20, 2017 at 03:26:06PM +, Mel Gorman wrote:
> > This translates to queue_work_on(), which has the comment of "We queue
> > the work to a specific CPU, the caller must ensure it can't go away.",
> > so is this safe? lru_add_drain_all() uses get_online_cpus() around this.
> >
601 - 700 of 823 matches
Mail list logo
