On Sun, Apr 23, 2017 at 04:17:33PM +0800, Ryder Lee wrote:
> Add documentation for PCIe PHY available in MT7623 series SoCs.
>
> Signed-off-by: Ryder Lee
> ---
> .../devicetree/bindings/phy/phy-mt7623-pcie.txt| 67
> ++
> 1 file changed, 67 insertions(+)
> create mode 1
Hi Joerg,
[auto build test ERROR on s390/features]
[also build test ERROR on v4.11-rc8 next-20170428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-s390-Fix-iommu-groups-and
Hello, Vincent.
On Thu, Apr 27, 2017 at 10:59:12AM +0200, Vincent Guittot wrote:
> > But the only difference there is that we lose accuracy in calculation;
> > otherwise, the end results are the same, no?
>
> Yes the end result is the same, it was mainly to point out the range
> difference and ex
On Sat, Apr 22, 2017 at 10:35:17AM -0700, Bjorn Andersson wrote:
> This adds the binding for describing shared memory buffers for
> implementing the remote filesystem protocol.
>
> Signed-off-by: Bjorn Andersson
> ---
>
> My initial attempt was to mimic the ramoops of just adding the compatible
On Fri, Apr 28, 2017 at 10:34 AM, Jerome Glisse wrote:
>> Kirill points out that the calls to {get,put}_dev_pagemap() can be
>> removed from the mm fast path if we take a single get_dev_pagemap()
>> reference to signify that the page is alive and use the final put of the
>> page to drop that refer
On mainline, there is no functional difference, just less code, and
symmetric lock/unlock paths.
On PREEMPT_RT builds, this fixes the following warning, seen by
Alexander GQ Gerasiov, due to the sleeping nature of spinlocks.
BUG: sleeping function called from invalid context at
kernel/locking
On Fri, Apr 28, 2017 at 1:38 AM, Wu Hao wrote:
> On Thu, Apr 20, 2017 at 09:10:01AM -0500, Alan Tull wrote:
>> Create of-fpga-region.c
>>
>> Move the following functions without modification from
>> fpga-region.c to of-fpga-region.c:
>>
>> * of_fpga_region_find
>> * of_fpga_region_get_mgr
>> * of_
On Thu, 27 Apr 2017 10:44:01 +0200
Johan Hovold wrote:
> On Wed, Apr 26, 2017 at 07:26:40PM +0200, Andreas Kemnade wrote:
> > If the netdev is accessed before the urbs are initialized,
> > there will be NULL pointer dereferences. That is avoided by
> > registering it when it is fully initialized.
> Kirill points out that the calls to {get,put}_dev_pagemap() can be
> removed from the mm fast path if we take a single get_dev_pagemap()
> reference to signify that the page is alive and use the final put of the
> page to drop that reference.
>
> This does require some care to make sure that any
On Thu, Apr 27, 2017 at 8:09 PM, Diego Viola wrote:
> On Thu, Apr 27, 2017 at 7:56 PM, Diego Viola wrote:
>> Hello,
>>
>> For some reason 4.11-rc8 makes my Dell Inspiron 5558 crash. The
>> problem is very random and I don't know how to reproduce it.
>>
>> That said, this only started happening wi
On 28/04/17 17:52, Will Deacon wrote:
> On Fri, Apr 28, 2017 at 06:16:46PM +0200, Geert Uytterhoeven wrote:
>> On Fri, Apr 28, 2017 at 4:57 PM, Will Deacon wrote:
>>> On Thu, Apr 27, 2017 at 02:33:05PM +0200, Geert Uytterhoeven wrote:
On arm32, the machine model specified in the device tree
Similar to the SDIO driver, we should implement this so that we will
automatically reset the device whenever there's a command timeout or
similar.
Signed-off-by: Brian Norris
---
I still haven't found the reset sequence to work 100% reliably, but it's
definitely better than nothing.
drivers/net
Kirill points out that the calls to {get,put}_dev_pagemap() can be
removed from the mm fast path if we take a single get_dev_pagemap()
reference to signify that the page is alive and use the final put of the
page to drop that reference.
This does require some care to make sure that any waits for t
On Fri, Apr 28, 2017 at 02:28:55PM +0200, Sebastian Reichel wrote:
> Cleanup driver slightly by using input_set_capability() instead
> of manually setting the required bits.
>
> Signed-off-by: Sebastian Reichel
Applied, thank you.
> ---
> drivers/input/misc/twl4030-pwrbutton.c | 3 +--
> 1 fil
On Fri, Apr 28, 2017 at 02:28:54PM +0200, Sebastian Reichel wrote:
> The interrupt should be requested for the platform device
> and not for the input device.
>
> Fixes: 7f9ce649d267 ("Input: twl4030-pwrbutton - simplify driver using
> devm_*")
> Signed-off-by: Sebastian Reichel
Applied, thank
On Fri, Apr 28, 2017 at 10:23:47AM +0530, Ganapatrao Kulkarni wrote:
> This is not a full event list, but a short list of useful events.
>
> Signed-off-by: Ganapatrao Kulkarni
> ---
> tools/perf/pmu-events/arch/arm64/mapfile.csv | 14 +
> .../arm64/thunderx2/implementation-defined.json
On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote:
> currently running v4.11-rc8-75-gf83246089ca0
>
> sunrpc bit is for the other unrelated problem I'm chasing.
>
> note also, I saw the backtrace without the fs/splice.c changes.
Interesting... Could you add this and see if that
On Sat, 2017-04-22 at 09:32 +0800, Geliang Tang wrote:
> Use setup_timer() instead of init_timer() to simplify the code.
>
> Signed-off-by: Geliang Tang
Thanks, series applied.
--
Doug Ledford
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57
On 26/04/17 17:03, Suzuki K Poulose wrote:
On 25/04/17 19:49, Radim Krčmář wrote:
2017-04-24 11:10+0100, Suzuki K Poulose:
The KVM uses mmu_notifier (wherever available) to keep track
of the changes to the mm of the guest. The guest shadow page
tables are released when the VM exits via mmu_noti
On Fri Apr 28 17, Jarkko Sakkinen wrote:
On Wed, Apr 26, 2017 at 03:39:54PM -0700, Jerry Snitselaar wrote:
For easier decoding, output the error code returned
from the tpm device in hex when the device is TPM2.0.
Cc: Jarkko Sakkinen
Cc: Peter Huewe
Cc: Marcel Selhorst
Cc: Jason Gunthorpe
Re
On 28/04/17 18:08, Doug Ledford wrote:
> On Mon, 2017-04-24 at 10:44 -0700, Joe Perches wrote:
>> On Mon, 2017-04-24 at 10:26 +0100, Colin King wrote:
>>>
>>> trivial fix to typo in pr_err message
>> []
>>>
>>> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c
>>> b/drivers/infiniband/sw/rxe/rxe_v
On Fri, Apr 21, 2017 at 06:23:36PM -0700, Stefan Agner wrote:
> The clock requirements are completely missing, add the clocks
> currently required by the driver.
>
> Signed-off-by: Stefan Agner
> ---
> Documentation/devicetree/bindings/mtd/gpmi-nand.txt | 14 +-
> 1 file changed, 13
On Fri, Apr 21, 2017 at 09:22:02PM +0200, Jens Rottmann wrote:
> The iMX-TLV320AIC23 driver isn't from Freescale, but from a company named
> Eukrea Electromatique, originally for their own boards. From the code I get
> the impression it is a bit older, its DT options use a differing naming
> scheme
On Sun, 2017-04-23 at 17:09 +0800, Pan Bian wrote:
> Function alloc_skb() will return a NULL pointer when there is no
> enough
> memory. However, the return value of alloc_skb() is directly used
> without validation in function send_fw_pass_open_req(). This patches
> checks the return value of allo
On 28/04/17 16:52, Morten Rasmussen wrote:
> Hi Vincent,
[...]
> As mentioned above, waiting time, i.e. !running && weight, is not
> scaled, which causes trouble for load.
I ran some rt-app-based tests on a system with frequency and cpu invariance.
(1) Two periodic 20% tasks with 12ms period on
On Mon, 2017-04-24 at 10:44 -0700, Joe Perches wrote:
> On Mon, 2017-04-24 at 10:26 +0100, Colin King wrote:
> >
> > trivial fix to typo in pr_err message
> []
> >
> > diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c
> > b/drivers/infiniband/sw/rxe/rxe_verbs.c
> []
> >
> > @@ -1324,7 +1324,7 @
On Thu, Apr 27, 2017 at 02:22:36PM +0200, Martin Kepplinger wrote:
> We now have a few of this device's definitions. Let's avoid magic numbers
> and use them.
>
> Signed-off-by: Martin Kepplinger
> ---
> drivers/input/touchscreen/ar1021_i2c.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(
* Cleaned up the formatting of ablkcipher_get arguments so it complies
with kernel style
* The offset in ablkcipher_get sould be added to the source, not the
destination. We rename it to soffset for clarity.
* dst++ should be dst=sg_next(dst)
* We call kunmap_atomic earlier so we only have to d
On Thu, Apr 27, 2017 at 02:22:35PM +0200, Martin Kepplinger wrote:
> The device could as well be in command mode, in which this driver cannot
> handle the device. When opening the device, let's make sure the device
> will be in the mode we expect it to be for this driver.
>
> Signed-off-by: Martin
On 28/04/17 12:30 AM, Herbert Xu wrote:
> You are right. Indeed the existing code looks buggy as they
> don't take sg->offset into account when doing the kmap. Could
> you send me some patches that fix these problems first so that
> they can be easily backported?
Ok, I think the only buggy one
On Fri, Apr 28, 2017 at 06:16:46PM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 28, 2017 at 4:57 PM, Will Deacon wrote:
> > On Thu, Apr 27, 2017 at 02:33:05PM +0200, Geert Uytterhoeven wrote:
> >> On arm32, the machine model specified in the device tree is printed
> >> during boot-up, courtesy o
On Tue, Mar 21, 2017 at 02:14:05PM +0200, Kalle Valo wrote:
> What I could do is to wait for the patches 1-3 trickle down to w-d-next
> and then apply this patch. It usually takes few weeks, but with bad luck
> it might happen only after the merge window. Would that work?
Is this going to get pick
On Fri, Apr 28, 2017 at 05:43:13PM +0100, Al Viro wrote:
> On Fri, Apr 28, 2017 at 11:29:55AM -0400, Dave Jones wrote:
> > On Fri, Apr 21, 2017 at 06:54:30PM +0100, Al Viro wrote:
> > > On Wed, Apr 12, 2017 at 03:03:18PM -0400, Dave Jones wrote:
> > >
> > > > Well it's been running an hour
On Fri, Apr 21, 2017 at 05:50:32PM +0200, Enric Balletbo i Serra wrote:
> Allow the possibility to configure the charge and the current voltage of
> the charger and also the NTC type for battery temperature measurement.
>
> Signed-off-by: Enric Balletbo i Serra
> ---
> Changes since v1:
> - Requ
On Fri, 2017-04-28 at 09:13 +0200, Steffen Klassert wrote:
> encap type espinudp sport 4500 dport 4500 addr 0.0.0.0
>
> Ok, this is espinudp. This information was important.
> This is not a GRO issue as I thought, the TX side is already broken.
>
> Could you please try the patch below?
On Friday, April 28, 2017, Andy Shevchenko wrote:
> > We were using "input-enable" to signal when the pin function that we set
> also needs to be forcible set to input by the software (once again,
> because the HW is not smart enough to do it on its own), but is different
> than the bi-directional
On Fri, 2017-04-28 at 17:26 +0300, Dan Carpenter wrote:
> On Fri, Apr 28, 2017 at 04:19:28PM +0200, Ilia Sergachev wrote:
> > Checkpatch emits WARNING: Avoid line continuations in quoted strings.
> >
> > Remove line continuations - split strings using quotes.
> >
> > Signed-off-by: Ilia Sergachev
On 04/28/17 00:11, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170427:
>
on i386:
when CONFIG_OF_OVERLAY is not enabled:
drivers/built-in.o: In function `unflatten_device_tree':
(.init.text+0x1209f): undefined reference to `unittest_unflatten_overlay_base'
--
~Randy
On Fri, Apr 28, 2017 at 11:29:55AM -0400, Dave Jones wrote:
> On Fri, Apr 21, 2017 at 06:54:30PM +0100, Al Viro wrote:
> > On Wed, Apr 12, 2017 at 03:03:18PM -0400, Dave Jones wrote:
> >
> > > Well it's been running an hour without incident, which looks promising.
> > > I'll leave it run, but
On Tue, Apr 11, 2017 at 9:53 AM, Leno Hou wrote:
> This patch optimized the code by previously getpos function call.
> Therefore, It's takes the convenience to understand logic of code.
Besides what Christoph told you (I agree with him, writing test suites
/ modules is quite good exercise for new
Hi guys,
On Fri, Apr 28, 2017 at 01:46:24PM +, Jayachandran C wrote:
> On Thu, Apr 27, 2017 at 06:37:59PM +0100, Will Deacon wrote:
> > > If my understanding is correct, the sysfs suggestion above is going to
> > > add API complexity without solving the issue. Ignoring the exclude_hv if
> > >
On 04/28/2017 01:11 AM, Jon Masters wrote:
> On 04/27/2017 08:54 PM, Khuong Dinh wrote:
>> From: Khuong Dinh
>>
>> This patch makes pci-xgene-msi driver ACPI-aware and provides
>> MSI capability for X-Gene v1 PCIe controllers in ACPI boot mode.
>>
>> Signed-off-by: Khuong Dinh
>> Signed-off-by: D
On Fri, 2017-04-28 at 18:08 +0200, Sebastien Buisson wrote:
> 2017-04-28 17:50 GMT+02:00 Stephen Smalley :
> > You seem to be conflating kernel policy with userspace policy.
> > security_load_policy() is provided with the kernel policy image,
> > which
> > is the result of linking the kernel-releva
Hi Masahiro,
Sorry for the delay, I was busy with non-NAND/MTD stuff lately.
On Wed, 19 Apr 2017 16:06:57 +0900
Masahiro Yamada wrote:
> Each driver has been responsible for:
> - Check if ECC setting specified (mostly by DT) is valid
> - Meet the chip's required ECC strength
> - Maximize
On Fri, Apr 28, 2017 at 8:50 AM, Greg Kroah-Hartman
wrote:
> On Fri, Apr 28, 2017 at 06:14:44AM -0700, Guenter Roeck wrote:
>> On 04/28/2017 12:28 AM, Greg Kroah-Hartman wrote:
>> > On Thu, Apr 27, 2017 at 02:09:56PM -0700, Guenter Roeck wrote:
>> > > --- /dev/null
>> > > +++ b/drivers/staging/typ
On Fri, Apr 28, 2017 at 12:11 PM, Cong Wang wrote:
> On Fri, Apr 28, 2017 at 8:30 AM, Paul Moore wrote:
>> On Thu, Apr 27, 2017 at 8:47 PM, Paul Moore wrote:
>>> In that case please send a proper inline patch to the audit mailing list
>>> and we'll review it.
>>>
>>> Thanks.
>>
>> Now that I'm b
On Fri, Apr 28, 2017 at 11:16 AM, Linus Walleij
wrote:
> On Thu, Apr 27, 2017 at 10:19 AM, Jacopo Mondi
> wrote:
> But why.
>
> I have these two static inlines just below your new macros:
+1.
> We generally prefer static inlines over macros because they are easier
> to read.
Not only. It adds
2017-04-25, 20:47:30 +0200, Jason A. Donenfeld wrote:
> This is a defense-in-depth measure in response to bugs like
> 4d6fa57b4dab ("macsec: avoid heap overflow in skb_to_sgvec"). While
> we're at it, we also limit the amount of recursion this function is
> allowed to do. Not actually providing a b
On Fri, Apr 28, 2017 at 05:55:58PM +0200, Sebastian Reichel wrote:
> isl29030 is basically the same chip. The only difference
> is the chip's first pin. For isl29028 its named ADDR0 and
> can be used to change the chip's i2c address. For isl29030
> on the other hand that pin is named Ials and is an
Hi Will,
On Fri, Apr 28, 2017 at 4:57 PM, Will Deacon wrote:
> On Thu, Apr 27, 2017 at 02:33:05PM +0200, Geert Uytterhoeven wrote:
>> On arm32, the machine model specified in the device tree is printed
>> during boot-up, courtesy of of_flat_dt_match_machine().
>>
>> On arm64, of_flat_dt_match_mac
This is the first step to make the aesni AES-GCM implementation
generic. The current code was written for rfc4106, so it handles only
some specific sizes of associated data.
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_asm.S | 169 +-
1 file
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_asm.S | 62 ++-
1 file changed, 48 insertions(+), 14 deletions(-)
diff --git a/arch/x86/crypto/aesni-intel_asm.S
b/arch/x86/crypto/aesni-intel_asm.S
index 605726aaf0a2..16627fec80b2 100644
--- a/a
Hello, Vincent.
On Thu, Apr 27, 2017 at 10:28:01AM +0200, Vincent Guittot wrote:
> On 27 April 2017 at 02:30, Tejun Heo wrote:
> > Hello, Vincent.
> >
> > On Wed, Apr 26, 2017 at 12:21:52PM +0200, Vincent Guittot wrote:
> >> > This is from the follow-up patch. I was confused. Because we don't
>
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_avx-x86_64.S | 31 ---
1 file changed, 24 insertions(+), 7 deletions(-)
diff --git a/arch/x86/crypto/aesni-intel_avx-x86_64.S
b/arch/x86/crypto/aesni-intel_avx-x86_64.S
index 7230808a7cef..faecb1518bf8 10
Hi
After sending this mail i just found out how i could reset the i2c-1 controller
manually with
devmem 0xffd05014 32 0x2000
devmem 0xffd05014 32 0
So i took a look into the device tree file socfpga.dtsi and found that the
reset lines
where not defined (although available in the corresponding
On Tue, Apr 25, 2017 at 07:25:49PM +0100, Catalin Marinas wrote:
> On Tue, Apr 25, 2017 at 07:22:23PM +0100, Catalin Marinas wrote:
> > The dma_common_pages_remap() function allocates a vm_struct object and
> > initialises the pages pointer to value passed as argument. However, when
> > this functi
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_avx-x86_64.S | 31 ---
1 file changed, 24 insertions(+), 7 deletions(-)
diff --git a/arch/x86/crypto/aesni-intel_avx-x86_64.S
b/arch/x86/crypto/aesni-intel_avx-x86_64.S
index a73117c84904..ee6283120f83 10
On Thu, Apr 27, 2017 at 02:33:05PM +0200, Geert Uytterhoeven wrote:
> On arm32, the machine model specified in the device tree is printed
> during boot-up, courtesy of of_flat_dt_match_machine().
>
> On arm64, of_flat_dt_match_machine() is not called, and the machine
> model information is not ava
Hi Frank,
On Fri, Apr 28, 2017 at 5:24 PM, Frank Rowand wrote:
> On 04/28/17 04:25, Geert Uytterhoeven wrote:
>> On Wed, Apr 26, 2017 at 2:09 AM, wrote:
>>> create mode 100644 drivers/of/unittest-data/overlay.dts
>>> create mode 100644 drivers/of/unittest-data/overlay_bad_phandle.dts
>>> cre
Now that the asm side of things can support all the valid lengths of ICV
and all lengths of associated data, provide the glue code to expose a
generic gcm(aes) crypto algorithm.
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_glue.c | 208 -
1 f
This is the first step to make the aesni AES-GCM implementation
generic. The current code was written for rfc4106, so it handles only
some specific sizes of associated data.
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_avx-x86_64.S | 85 ++--
1 file
This is the first step to make the aesni AES-GCM implementation
generic. The current code was written for rfc4106, so it handles
only some specific sizes of associated data.
Signed-off-by: Sabrina Dubroca
---
arch/x86/crypto/aesni-intel_avx-x86_64.S | 122 ++-
1 file
The current aesni AES-GCM implementation only offers support for
rfc4106(gcm(aes)). This makes some things a little bit simpler
(handling of associated data and authentication tag), but it means
that non-IPsec users of gcm(aes) have to rely on
gcm_base(ctr-aes-aesni,ghash-clmulni), which is much s
On Fri, Apr 28, 2017 at 8:30 AM, Paul Moore wrote:
> On Thu, Apr 27, 2017 at 8:47 PM, Paul Moore wrote:
>> In that case please send a proper inline patch to the audit mailing list
>> and we'll review it.
>>
>> Thanks.
>
> Now that I'm back in front of a proper screen/keyboard I've been
> looking
> >> Hi,
> >>
> >> [adding Dave Miller, netdev, lkml]
> >
> > thanks
> >
> >>> On QEMU the next-20170428 hangs on boot for me due to kernel panic in
> >>> rtnetlink_init():
> >>>
> >>> void __init rt
From: Jan Kiszka
Date: Mon, 24 Apr 2017 21:27:15 +0200
> The IOT2000 is industrial controller platform, derived from the Intel
> Galileo Gen2 board. The variant IOT2020 comes with one LAN port, the
> IOT2040 has two of them. They can be told apart based on the board asset
> tag in the DMI table.
2017-04-28 17:50 GMT+02:00 Stephen Smalley :
> You seem to be conflating kernel policy with userspace policy.
> security_load_policy() is provided with the kernel policy image, which
> is the result of linking the kernel-relevant portions of all policy
> modules together. A hash of that image will
From: Niklas Cassel
Date: Fri, 28 Apr 2017 17:08:17 +0200
> Hello
>
>
> Since next-20170428
> the ARTPEC-6 SoC (MACH_ARTPEC6) does no longer boot.
>
> It works fine with next-20170427.
>
>
> I've bisected it to the following commit:
>
> 6d684e54690c
From: Mark Rutland
Date: Fri, 28 Apr 2017 15:52:34 +0100
> On Fri, Apr 28, 2017 at 04:24:29PM +0300, Yury Norov wrote:
>> Hi all,
>
> Hi,
>
> [adding Dave Miller, netdev, lkml]
>
>> On QEMU the next-20170428 hangs on boot for me due to kernel panic in
>>
isl29030 is basically the same chip. The only difference
is the chip's first pin. For isl29028 its named ADDR0 and
can be used to change the chip's i2c address. For isl29030
on the other hand that pin is named Ials and is an analog
current output proportional to ALS/IR. This change is
irrelevant fo
On Fri, Apr 28, 2017 at 11:43:26PM +0900, Michael Mera wrote:
> Fix checkpatch messages:
> ERROR: code indent should use tabs where possible
> WARNING: Block comments should align the * on each line
>
> Changes:
> - replace unnecessary multiline comment by a single line comment
> - change "bit
Hi Vincent,
Sorry for crashing the party this late. As you know, it takes a long
period of uninterrupted review time to properly review PELT stuff.
Disclaimer: I haven't read the rest of the thread yet.
On Mon, Apr 10, 2017 at 11:18:29AM +0200, Vincent Guittot wrote:
> The current implementation
On Fri, Apr 28, 2017 at 06:14:44AM -0700, Guenter Roeck wrote:
> On 04/28/2017 12:28 AM, Greg Kroah-Hartman wrote:
> > On Thu, Apr 27, 2017 at 02:09:56PM -0700, Guenter Roeck wrote:
> > > --- /dev/null
> > > +++ b/drivers/staging/typec/pd.h
> > > @@ -0,0 +1,281 @@
> > > +/*
> > > + * Copyright 2015
Mehmet Kayaalp wrote:
> >> + /* TODO: update CRC */
> >
> > Is this bit missing?
>
> I didn't add it, since I wasn't sure it was still used with secure boot.
I'm not sure why secure boot would skip it if normal boot does it. You'll
have to trawl the boot wrapper and kernel arch setup code to
On 04/28/17 02:44, Arnd Bergmann wrote:
> gcc warns that an empty device tree would cause undefined behavior:
>
> drivers/of/unittest.c: In function 'of_unittest':
> drivers/of/unittest.c:2199:25: warning: 'last_sibling' may be used
> uninitialized in this function [-Wmaybe-uninitialized]
>
> Th
On Fri, 2017-04-28 at 17:16 +0200, Sebastien Buisson wrote:
> 2017-04-27 20:47 GMT+02:00 Stephen Smalley :
> > > I just checked, with the method of computing the checksum on a
> > > (data,
> > > len) pair on entry to security_load_policy() the checksum does
> > > not
> > > change after using setseb
On Wed, Apr 26, 2017 at 03:39:47PM +0300, Yury Norov wrote:
> On Thu, Apr 20, 2017 at 09:05:30PM +0200, Peter Zijlstra wrote:
> > On Thu, Apr 20, 2017 at 09:23:18PM +0300, Yury Norov wrote:
> > > Is there some test to reproduce the locking failure for the case.
> >
> > Possibly sysvsem stress befo
Hi
I have tried to add a gpio recovery gpio controller to the designware i2c
driver. The attempt is
attached below. I have a Intel(Altera) Cyclone V SOC Platform attached to a
buggy power
supply which gives a lockup on the i2c controller as a external device gives to
much noise
on the signal an
On 04/28/17 02:44, Arnd Bergmann wrote:
> We get a link error when the new tests are used by overlays
> are not:
>
> drivers/of/built-in.o: In function `unflatten_device_tree':
> (.init.text+0x967): undefined reference to `unittest_unflatten_overlay_base'
>
> This makes the #ifdef check match the
On 04/28/2017 08:09 AM, Yury Norov wrote:
> On Fri, Apr 28, 2017 at 03:52:34PM +0100, Mark Rutland wrote:
>> On Fri, Apr 28, 2017 at 04:24:29PM +0300, Yury Norov wrote:
>>> Hi all,
>>
>> Hi,
>>
>> [adding Dave Miller, netdev, lkml]
>
> thanks
>
On Thu, Apr 13, 2017 at 01:33:09PM +0300, Yury Norov wrote:
> On Wed, Apr 12, 2017 at 01:04:55PM -0400, Adam Wallis wrote:
> > On 4/10/2017 5:35 PM, Yury Norov wrote:
> > > The patch of Jan Glauber enables queued spinlocks on arm64. I rebased it
> > > on
> > > latest kernel sources, and added a co
On Fri, Apr 28, 2017 at 6:16 PM, Chris Brandt wrote:
> On Friday, April 28, 2017, Andy Shevchenko wrote:
>> Had you read the following, esp. Note there?
>>
>> * @PIN_CONFIG_INPUT_ENABLE: enable the pin's input. Note that this does
>> not
>> * affect the pin's ability to drive output. 1 enab
On Thu, Apr 27, 2017 at 9:37 PM, Mika Penttilä
wrote:
> Hi,
>
> Just wondering the pmem struct device vs gendisk lifetimes.. from
> pmem_attach_disk():
>
> device_add_disk(dev, disk);
> devm_add_action_or_reset(dev, pmem_release_disk, disk);
>
>
> where:
> static void pmem_release
Disable the generic address limit check in favor of an architecture
specific optimized implementation.
The address limit is checked on each syscall return path to user-mode.
If it was changed, a generic handler is called to stop the kernel on an
explicit check.
Signed-off-by: Thomas Garnier
Revi
Disable the generic address limit check in favor of an architecture
specific optimized implementation.
The address limit is checked on each syscall return path to user-mode
path as well as the irq user-mode return function. If the address limit
was changed, a generic handler is called to stop the
Disable the generic address limit check in favor of an architecture
specific optimized implementation.
The user-mode state check is added to the prepare_exit_to_usermode
function. This function is called before any user-mode return on 32-bit
and on the 64-bit syscall slowpath. For the 64-bit sysca
Ensure that a syscall does not return to user-mode with a kernel address
limit. If that happens, a process can corrupt kernel-mode memory and
elevate privileges [1].
The CONFIG_ADDR_LIMIT_CHECK option disables the generic check so each
architecture can create optimized versions. This option is ena
Checkpatch emits WARNING: Avoid line continuations in quoted strings.
Remove line continuations - split strings using quotes.
Signed-off-by: Ilia Sergachev
---
Changes for v4:
- improve indentation for better readability
drivers/staging/ks7010/ks_hostif.c | 30 --
On Thu, Apr 27, 2017 at 8:47 PM, Paul Moore wrote:
> In that case please send a proper inline patch to the audit mailing list
> and we'll review it.
>
> Thanks.
Now that I'm back in front of a proper screen/keyboard I've been
looking over your patch and while you are very right in that the
curren
On Fri, Apr 21, 2017 at 06:54:30PM +0100, Al Viro wrote:
> On Wed, Apr 12, 2017 at 03:03:18PM -0400, Dave Jones wrote:
>
> > Well it's been running an hour without incident, which looks promising.
> > I'll leave it run, but I'd say you're on the right track given how quick
> > it reproduced s
On Fri, 28 Apr 2017, Joerg Roedel wrote:
> On Fri, Apr 28, 2017 at 02:46:34PM +0200, Gerald Schaefer wrote:
> > On Thu, 27 Apr 2017 23:03:25 +0200
> > Joerg Roedel wrote:
> >
> > > > Well, there is a separate zpci_dev for each pci_dev on s390,
> > > > and each of those has its own separate dma-ta
On 04/28/17 04:25, Geert Uytterhoeven wrote:
> Hi Frank,
>
> On Wed, Apr 26, 2017 at 2:09 AM, wrote:
>> From: Frank Rowand
>>
>> Existing overlay unit tests examine individual pieces of the overlay
>> code. The new tests target the entire process of applying an overlay.
>>
>> Signed-off-by: Fr
On 04/02/2017 06:19 AM, Guenter Roeck wrote:
On 03/14/2017 01:55 PM, Eddie James wrote:
From: "Edward A. James"
Add a generic mechanism to expose the sensors provided by the OCC in
sysfs.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ | 62
2017-04-27 20:47 GMT+02:00 Stephen Smalley :
>> I just checked, with the method of computing the checksum on a (data,
>> len) pair on entry to security_load_policy() the checksum does not
>> change after using setsebool. So it seems I would need to call
>> security_read_policy() to retrieve the bin
On Friday, April 28, 2017, Andy Shevchenko wrote:
> Had you read the following, esp. Note there?
>
> * @PIN_CONFIG_INPUT_ENABLE: enable the pin's input. Note that this does
> not
> * affect the pin's ability to drive output. 1 enables input, 0
> disables
> * input.
>
> For me manual i
* Arnd Bergmann [170428 08:06]:
> Tony Lindgren reports a kernel oops that resulted from my compile-time
> fix on the default config. This shows two problems:
>
> a) configurations that did not already enable PTP_1588_CLOCK will
>now miss the cpts driver
>
> b) when cpts support is disabled,
On Fri, Apr 28, 2017 at 03:52:34PM +0100, Mark Rutland wrote:
> On Fri, Apr 28, 2017 at 04:24:29PM +0300, Yury Norov wrote:
> > Hi all,
>
> Hi,
>
> [adding Dave Miller, netdev, lkml]
thanks
> > On QEMU the next-20170428 hangs on boot for me due to kernel p
Hi Andrew,
Andrew Lunn writes:
>> +/* Write the VID to iterate from only once */
>> +if (!entry->valid) {
>> +err = mv88e6xxx_g1_vtu_vid_write(chip, entry);
>> +if (err)
>> +return err;
>> +}
>
> Please could you add a bigger comment. It is
Hello
Since next-20170428
the ARTPEC-6 SoC (MACH_ARTPEC6) does no longer boot.
It works fine with next-20170427.
I've bisected it to the following commit:
6d684e54690caef45cf14051ddeb7c71beeb681b is the first bad commit
commit 6d684e54690caef45cf14051ddeb7c71beeb681b
Author: Herbert Xu
> On Thursday, April 27, 2017 8:37 AM, Geert Uytterhoeven wrote:
> > On Tue, Apr 25, 2017 at 6:36 PM, Jingoo Han wrote:
> > > On Monday, April 24, 2017 1:56 PM, Olimpiu Dejeu wrote:
> > >>
> > >> On Mon, April 24, 2017 11:10 AM, Rob Herring < r...@kernel.org> wrote:
> > >>
> > >> > On Wed, Mar 15,
201 - 300 of 718 matches
Mail list logo