Andy Lutomirski writes:
> On Wed, Jul 5, 2017 at 9:32 PM, Kees Cook wrote:
>> In an attempt to provide sensible rlimit defaults for setuid execs, this
>> inherits the namespace's init rlimits:
>>
>> $ ulimit -s
>> 8192
>> $ ulimit -s unlimited
>> $ /bin/sh -c 'ulimit -s'
>> unlimited
>> $ sudo
Hi Bjorn:
Could you please give some feedback about this patchset, it looks like no more
comments for more than a week,
thanks. :)
Ding
On 2017/6/29 13:47, Ding Tianhong wrote:
> ping
>
> On 2017/6/22 20:15, Ding Tianhong wrote:
>> Some devices have problems with Transaction Layer Packets
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 9b51f04424e17051a89ab32d892ca66b2a104825 (4.12+).
WARNING: possible recursive locking detected
4.12.0+ #42 Not tainted
On Thu, 2017-07-06 at 13:57 +0100, Daniel Thompson wrote:
> On 06/07/17 13:41, Paul Kocialkowski wrote:
> > > > Some panels have a documented powerup sequence, which usually
> > > > ends with
> > > > the backlight being enabled to avoid showing garbage before the
> > > > panel is
> > > >
On 06/07/17 13:41, Paul Kocialkowski wrote:
Some panels have a documented powerup sequence, which usually ends with
the backlight being enabled to avoid showing garbage before the panel is
initialized completely.
The reason for 3698d7e7d221 was a device with the display disabled out
of the
On Wed, 5 Jul 2017 17:11:47 -0700
Joel Fernandes wrote:
> Currently we stop recording task information if any of them error out or are
> not being recorded. Further if switching to/from the idle thread, we bail out
> early on. Fix these issues.
Can you break this up into three patches. And
High-order allocations are obviously more costly, and it's very useful
to know how many of them happens, if there are any issues
(or suspicions) with memory fragmentation.
This commit changes existing per-zone allocation counters to be
per-zone per-order. These counters are displayed using a new
On 06/07/17 10:01, Hanjun Guo wrote:
> Hi Marc,
>
> On 2017/7/6 15:43, Marc Zyngier wrote:
>> On 06/07/17 05:35, Hanjun Guo wrote:
>>> From: Hanjun Guo
>>>
>>> commit d59f6617eef0 (genirq: Allow fwnode to carry name information only)
>>> forgot to do "domain->fwnode = fwnode;" for irqchips being
Hi Greg,
> Why is this a MIPS config file? What about the "generic" android
> configs we already have? Shouldn't they work just as well here?
You are right, this should not be MIPS specific config.
This patch will be omitted in the next version.
Thanks!
Kind regards,
Miodrag
On Wed, Jul 05, 2017 at 12:25:06PM -0400, Steven Rostedt wrote:
> On Tue, 4 Jul 2017 15:38:55 +0900
> Masami Hiramatsu wrote:
>
> > +local testlog=`mktemp $LOG_DIR/${testname}-log.XX`
> > + else
> > +local testlog=`/proc/self/fd/1`
>
> cute trick.
Shouldn't this be:
local
Hi Greg,
> How well does these patches "work" with the recent goldfish
> images/kernels that are out there? I know the goldfish platform has
> been revamped a lot recently, and I would not like to see these changes
> cause things to break there :)
Actually these changes have been in the Googles
> > > I have a HP ProLiant DL380 G3 server. It has two
> > > dual-core 32-bit Xeon CPUs. CONFIG_NR_CPUS=4 and has always been.
> >
> > Same happens on DL360 G3 - 1U server of the same era.
>
> And the next generation of it, DL380 G4, shows the same problem.
As of 4.12, this has been fixed -
The MAX17211 monitor a single cell pack. The MAX17215 monitor and
balance a 2S or 3S pack or monitor a multiple-series cell pack.
Both device use 1-Wire interfce.
Signed-off-by: Alex A. Mihaylov
---
drivers/power/supply/Kconfig| 13 +
drivers/power/supply/Makefile | 1 +
Fixes: cc5d0db390b0 ("regmap: Add 1-Wire bus support")
Commit de0d6dbdbdb2 ("w1: Add subsystem kernel public interface")
Fix place off w1.h header file
Cosmetic: Fix company name (local to international)
Signed-off-by: Alex A. Mihaylov
---
drivers/base/regmap/regmap-w1.c | 4 ++--
1 file
On Thu, 6 Jul 2017, James Hogan wrote:
> > > + asm volatile(
> > > + " syscall\n"
> > > + : "=r" (ret), "=r" (error)
> > > + : "r" (clkid), "r" (ts), "r" (nr)
> > > + : "memory");
> > > +
> > > + return error ? -ret : ret;
> > > +}
> >
> > Hmm, are you sure it is safe nowadays WRT the
Some PHYs (for example the LAN8710) doesn't allow turning the clocks off
and on again without reset (according to their datasheet). Exactly this
behaviour was introduced for power saving reasons by commit e8fcfcd5684a
("net: fec: optimize the clock management to save power")
Therefore add a
The fec_reset_phy function allowed only one execution during probeing.
As a preparation for future patches move the dt parsing and gpio
allocation to the probe function. The parameters of the phy reset are
added to the fec_enet_private struct. As a result the fec_reset_phy
function may be called
Linus,
Note, this pull request contains one merge. I merged in a commit that
I sent to you earlier that was needed for another fix of the current code.
The commit I merged had the same parent (v4.12-rc5) as the start of this
development tree, and the merge itself is documented in the commit log.
Hi Yunlong,
It looks there is no way to create discard thread redundantly,
so here we don't need to check this?
Thanks,
On 2017/7/6 19:05, Yunlong Song wrote:
> Signed-off-by: Yunlong Song
> ---
> fs/f2fs/segment.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/f2fs/segment.c
On Thu, 6 Jul 2017 22:06:58 +0900
Stafford Horne wrote:
> On Wed, Jul 05, 2017 at 12:25:06PM -0400, Steven Rostedt wrote:
> > On Tue, 4 Jul 2017 15:38:55 +0900
> > Masami Hiramatsu wrote:
> >
> > > +local testlog=`mktemp $LOG_DIR/${testname}-log.XX`
> > > + else
> > > +local
On Thu, Jul 06, 2017 at 03:01:11PM +0200, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while fuzzing the kernel with syzkaller.
>
> On commit 9b51f04424e17051a89ab32d892ca66b2a104825 (4.12+).
It's "fs: implement vfs_iter_write using do_iter_write", actually.
On Thu, Jul 06, 2017 at 02:04:31PM +0100, Roman Gushchin wrote:
> High-order allocations are obviously more costly, and it's very useful
> to know how many of them happens, if there are any issues
> (or suspicions) with memory fragmentation.
>
> This commit changes existing per-zone allocation
On imx6sx accessing OCOTP directly is wrong because the ocotp clock needs to be
enabled first. Fix this by adding a nvmem-cells binding and using it on imx6sx,
imx6ul and imx6ull.
The existing binding is kept around because it works fine on imx6qdl.
This was initially reported by Lothar Waßmann
On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock
needs to be enabled first. Add support for reading those same values through
the nvmem API instead.
The older path is preserved for compatibility with older dts and because it
works correctly on imx6qdl chips.
This works identically to imx6sx-tempmon on both imx6ul and imx6ull.
It just needs to be defined in dts.
Signed-off-by: Leonard Crestez
---
arch/arm/boot/dts/imx6ul.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/imx6ul.dtsi
cc-ing Jin Quian (maintains kernel repo for emulators), Bo Hu & Lingfeng Yang
from Google
Hi Rob,
thank you for taking the time to review the patches.
Let me try to answer some of your comments and concerns:
> This isn't even supported in Google's common kernel tree. If it's not
> important
On newer imx SOCs accessing OCOTP directly is wrong because the ocotp
clock needs to be enabled first. Add a binding for accessing the same
values through the imx-ocotp nvmem driver using nvmem-cells. This is
similar to other thermal drivers.
The old binding is preserved for compatibility and
On imx6sx accessing OCOTP directly is wrong because the ocotp clock
needs to be enabled first. Use the nvmem-cells binding instead.
This requirement does not apply to older imx6qdl chips because there the
ocotp access clock (clk_ipg_s) is always enabled.
This is visible by comparing the "System
cc-ing Arve Hjønnevåg who originally upstreamed Goldfish FB driver
cc-ing Jin Quian, Bo Hu & Lingfeng Yang from Google
Hi Rob,
Thanks for taking the time to review the patches
> I don't know that this should even go upstream. There's no upstream
> qemu support for goldfish-fb. Maybe this is a
This patch adds DMAMUX support for STM32H743 SoC.
Signed-off-by: Pierre-Yves MORDRET
---
arch/arm/boot/dts/stm32h743.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/stm32h743.dtsi b/arch/arm/boot/dts/stm32h743.dtsi
index 3d1cd88..0e24a4c 100644
This patch adds DMA support for STM32F746 SoC.
Signed-off-by: Pierre-Yves MORDRET
---
arch/arm/boot/dts/stm32f746.dtsi | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f746.dtsi b/arch/arm/boot/dts/stm32f746.dtsi
index c2765ce..bfffea4
This patch adds DMA support for STM32H743 SoC.
Signed-off-by: Pierre-Yves MORDRET
---
arch/arm/boot/dts/stm32h743.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/arm/boot/dts/stm32h743.dtsi b/arch/arm/boot/dts/stm32h743.dtsi
index 4685629..3d1cd88
cc-ing Jin Quian, Bo Hu & Lingfeng Yang from Google
Hi Alexandre,
thank you for your comments, answers are inline:
>
> On 28/06/2017 at 17:46:55 +0200, Aleksandar Markovic wrote:
> > From: Aleksandar Markovic
> >
> > Add device driver for a virtual Goldfish RTC clock.
> >
> > The driver can
Hi Mark,
> As it stands, this needs a major amount of reworking. You're most
> probably better off rewriting it from scratch instead of tinkering with
> what looks like 10+ year old code...
thanks for your valuable comments.
We will try to update this code with regards to the latest kernel
On Thu, 6 Jul 2017 10:39:28 +0800
Alex Shi wrote:
> Hi Steven,
>
> Thanks a lot for detailed review. Every suggestion were token except one need
> extra review: the 'Waking up in loop'. Is this OK or need more further change?
>
> BTW, I didn't add you on Reviewers, since you are author
Hi All,
> On 07/05/2017 03:26 AM, Masahiro Yamada wrote:
> >2017-07-05 19:06 GMT+09:00 Keiji Hayashibara
> >:
> >>Hi Guenter,
> >>
> >>Let me confirm if I got it.
> >>
> >>I guess that this series finished the review.
> >>Could you tell me the current state of this series?
> >
> >
> >I will pick
On 07/05/17 at 12:06pm, Kees Cook wrote:
> On Tue, Jun 27, 2017 at 4:24 PM, Baoquan He wrote:
> > Below code was added to fix the kexec/kdump kernel with kaslr disabled,
> > at that time kernel kaslr physical address and virtual address
> > randomization are coupled. What it was doing is to
On Thu, Jul 6, 2017 at 1:32 AM, John Stultz wrote:
> Hey folks,
>I updated my HiKey kernel tree to linus/master today and it stopped
> booting (hitting errors at init and reseting immediately into
> bootloader mode):
>
> [5.289827] init: Skipped setting INIT_AVB_VERSION (not in recovery
On Thu, Jul 6, 2017 at 9:23 PM, Arnd Bergmann wrote:
> On Thu, Jul 6, 2017 at 10:36 AM, Tomasz Figa wrote:
>> On Thu, Jul 6, 2017 at 5:34 PM, Tomasz Figa wrote:
>>> On Thu, Jul 6, 2017 at 5:26 PM, Arnd Bergmann wrote:
On Thu, Jul 6, 2017 at 3:44 AM, Tomasz Figa wrote:
>
>>>
>>> I'd say
On Thu, Jul 06, 2017 at 10:50:11AM +0200, Alvaro Gamez Machado wrote:
> Keep supporting proprietary "xlnx,phy-type" attribute and add support for
> MII connectivity to the PHY.
Hi Alvaro
Thanks for picking this up.
>
> Signed-off-by: Alvaro Gamez Machado
> ---
>
On Thu, Jul 06, 2017 at 12:56:43PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 06, 2017 at 12:45:55PM +0100, Russell King - ARM Linux wrote:
> > Well, from what I can see in 4.12, the cec-notifier stuff is rather
> > broken (tda998x has stopped working as its stuck with a physical
> >
Hi Jaegeuk,
On 2017/7/4 7:08, Jaegeuk Kim wrote:
> In order to avoid lock contention for atomic written pages, we'd better give
> EAGAIN in f2fs_migrate_page. We expect it will be released soon as transaction
> commits.
Hmm.. if atomic write is triggered intensively, there is little change to
On Wed, 5 Jul 2017, Kees Cook wrote:
> @@ -3536,6 +3565,9 @@ static int kmem_cache_open(struct kmem_cache *s,
> unsigned long flags)
> {
> s->flags = kmem_cache_flags(s->size, flags, s->name, s->ctor);
> s->reserved = 0;
> +#ifdef CONFIG_SLAB_FREELIST_HARDENED
> + s->random =
Hello Hans,
Thank you for the time spent to review.
On 07/03/2017 02:32 PM, Hans Verkuil wrote:
> On 06/19/2017 04:48 PM, Todor Tomov wrote:
>> These files handle the video device nodes of the camss driver.
>>
>> Signed-off-by: Todor Tomov
>> ---
>>
Quoting Geert Uytterhoeven (ge...@linux-m68k.org):
> with W=2:
>
> security/apparmor/policy_unpack.c: In function ‘unpack_trans_table’:
> security/apparmor/policy_unpack.c:469: warning: declaration of ‘pos’
> shadows a previous local
> security/apparmor/policy_unpack.c:451: warning:
On 05/07/2017 20:50, Peter Zijlstra wrote:
> On Fri, Jun 16, 2017 at 07:52:33PM +0200, Laurent Dufour wrote:
>> @@ -2294,8 +2295,19 @@ static bool pte_map_lock(struct vm_fault *vmf)
>> if (vma_has_changed(vmf->vma, vmf->sequence))
>> goto out;
>>
>> -pte =
Hi Maddy/Anju,
Comments inline ...
Anju T Sudhakar writes:
> From: Madhavan Srinivasan
>
> Parse device tree to detect IMC units. Traverse through each IMC unit
> node to find supported events and corresponding unit/scale files (if any).
>
> The device tree for IMC counters starts at the node
Andrei Vagin writes:
> I did a few experiments and found that the bug is reproduced for 6-12
> hours on the our test server. Then I reverted two patches and the server
> is working normally for more than 24 hours already, so the bug is
> probably in one of these patches.
>
> commit
On Thu, Jul 6, 2017 at 10:31 PM, Tomasz Figa wrote:
> On Thu, Jul 6, 2017 at 9:23 PM, Arnd Bergmann wrote:
>> On Thu, Jul 6, 2017 at 10:36 AM, Tomasz Figa wrote:
>>> On Thu, Jul 6, 2017 at 5:34 PM, Tomasz Figa wrote:
On Thu, Jul 6, 2017 at 5:26 PM, Arnd Bergmann wrote:
> On Thu, Jul
On Thu, 6 Jul 2017 18:10:58 +0900
Masami Hiramatsu wrote:
> @@ -255,12 +262,18 @@ __run_test() { # testfile
> # Run one test case
> run_test() { # testfile
>local testname=`basename $1`
> - local testlog=`mktemp $LOG_DIR/${testname}-log.XX`
> + if [ ! -z "$LOG_FILE" ] ; then
> +
On 07/06/17 at 09:28pm, Baoquan He wrote:
> > > Do you mean the handling in boot/compressed/head_64.S? Whatever it does,
> > > it's only for physical address. The virtual address mapping is not
> > > touched. Here virt_addr respresents the offset between
> > > 0x8000,
From: Chao Yu
This patch adds to support plain user/group quota.
- setattr() calls dquot_transfer which will transfer inode->i_blocks.
We can't reclaim that during f2fs_evict_inode(). So, we need to count
node blocks as well in order to match i_blocks with dquot's space.
- in f2fs_remount,
Hi Richard
> diff --git a/Documentation/devicetree/bindings/net/fsl-fec.txt
> b/Documentation/devicetree/bindings/net/fsl-fec.txt
> index 6f55bdd..1766579 100644
> --- a/Documentation/devicetree/bindings/net/fsl-fec.txt
> +++ b/Documentation/devicetree/bindings/net/fsl-fec.txt
> @@ -23,6 +23,9
On Thu, Jul 6, 2017 at 3:31 PM, Tomasz Figa wrote:
> On Thu, Jul 6, 2017 at 9:23 PM, Arnd Bergmann wrote:
>> On Thu, Jul 6, 2017 at 10:36 AM, Tomasz Figa wrote:
>>> On Thu, Jul 6, 2017 at 5:34 PM, Tomasz Figa wrote:
>>>
>>> Sorry, I intended to mean:
>>>
>>> IMHO re-implementing the code
On 7/4/2017 11:48 PM, Max Gurtovoy wrote:
On 7/4/2017 10:10 PM, Thomas Gleixner wrote:
On Tue, 4 Jul 2017, Linus Torvalds wrote:
On Tue, Jul 4, 2017 at 8:17 AM, Jens Axboe wrote:
On 07/03/2017 06:00 PM, Linus Torvalds wrote:
If they ever do come online, does that get fixed? I don't
On 7/6/2017 3:59 AM, Tina Zhang wrote:
> Add VFIO_DEVICE_QUERY_GFX_PLANE ioctl command to let user mode query and
> get the plan and its related information.
>
> The dma-buf's life cycle is handled by user mode and tracked by kernel.
> The returned fd in struct vfio_device_query_gfx_plane can
On Thu, Jul 6, 2017 at 3:49 PM, Tomasz Figa wrote:
> On Thu, Jul 6, 2017 at 10:31 PM, Tomasz Figa wrote:
>> On the other hand, if it's strictly about base/dma-mapping, we might
>> not need it indeed. The driver could call iommu-dma helpers directly,
>> without the need to provide its own DMA
On 04/07/17 20:22, Edward Cree wrote:
> I don't know why test_l4lb has to process _fewer_ insns with my patches;
> if anything I'm worrying that I may be incorrectly pruning branches.
> (I've spotted a possible bug in that I'm not looking at 'id' which,
> although it doesn't have to match, if
On Thu, Jul 6, 2017 at 11:02 PM, Arnd Bergmann wrote:
> On Thu, Jul 6, 2017 at 3:49 PM, Tomasz Figa wrote:
>> On Thu, Jul 6, 2017 at 10:31 PM, Tomasz Figa wrote:
>
>>> On the other hand, if it's strictly about base/dma-mapping, we might
>>> not need it indeed. The driver could call iommu-dma
On Thu, Jul 06, 2017 at 01:04:18PM +0200, Daniel Vetter wrote:
> On Thu, Jul 6, 2017 at 12:16 PM, Ville Syrjälä
> wrote:
> >> > + if (!dev->irq_enabled)
> >> > + return -EINVAL;
> >> > +
> >> > + crtc = drm_crtc_find(dev, get_seq->crtc_id);
> >> > + if (!crtc)
> >> > +
On Thu, Jul 06, 2017 at 02:12:37PM +0100, Maciej W. Rozycki wrote:
> On Thu, 6 Jul 2017, James Hogan wrote:
> > > (and would have to forcibly use the 32-bit encoding in the microMIPS
> > > case)?
> >
> > I don't believe there is a 16-bit SYSCALL encoding in microMIPS, at
> > least I can't see one
Greetings,
I'm seeing $subject in master as of this merge window. I don't see it
with my usual stripped down PREEMPT_VOLUNTARY or an enterprise-ish
NOPREEMPT config, but do see it with the attached, derived from my
enterprise-ish PREEMPT_RT config after running make oldconfig on it,
and
On Thu, Jul 06, 2017 at 12:09:45PM +0100, Robin Murphy wrote:
> I suppose another option is to just make the IOMMU and DMA ops a
> self-contained non-modular driver mirroring the VT-d/AMD-Vi IOMMUs -
> AFAICS it shouldn't have to be all that tightly coupled to the IPU bus
> code, the latter more
From: Paul E. McKenney
> Sent: 06 July 2017 00:30
> There is no agreed-upon definition of spin_unlock_wait()'s semantics,
> and it appears that all callers could do just as well with a lock/unlock
> pair. This series therefore removes spin_unlock_wait() and changes
> its users to instead use a
On Thu, Jul 6, 2017 at 5:58 AM, Colin King wrote:
> From: Colin Ian King
>
> The arrays pctl0_data and pctl1_data do not need to be in global scope,
> so them both static.
>
> Cleans up sparse warnings:
> symbol 'pctl0_data' was not declared. Should it be static?
> symbol 'pctl1_data' was not
On Thu, Jul 6, 2017 at 11:10 PM, Christoph Hellwig wrote:
> On Thu, Jul 06, 2017 at 12:09:45PM +0100, Robin Murphy wrote:
>> I suppose another option is to just make the IOMMU and DMA ops a
>> self-contained non-modular driver mirroring the VT-d/AMD-Vi IOMMUs -
>> AFAICS it shouldn't have to be
On Tue, Jun 27, 2017 at 02:23:20PM -0400, Al Cooper wrote:
> Add Device Tree binding document for Broadcom USB Device
> Controller (BDC).
>
> Signed-off-by: Al Cooper
> ---
> .../devicetree/bindings/usb/brcm,bdc-udc.txt | 28
> ++
> 1 file changed, 28 insertions(+)
>
On Tue, Jun 27, 2017 at 02:23:20PM -0400, Al Cooper wrote:
> Add Device Tree binding document for Broadcom USB Device
> Controller (BDC).
Also, "dt-bindings: usb: ..." for the subject.
On Thu, Jul 06, 2017 at 02:38:41PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 06, 2017 at 12:56:43PM +0100, Russell King - ARM Linux wrote:
> > On Thu, Jul 06, 2017 at 12:45:55PM +0100, Russell King - ARM Linux wrote:
> > > Well, from what I can see in 4.12, the cec-notifier stuff is
On 05/07/17 11:41, Thomas Gleixner wrote:
> On Wed, 5 Jul 2017, Paul Menzel wrote:
>> On a Lenovo X60t with coreboot based firmware testing the latest master
>> branch from Linus, the message below is new, and isn’t there with Linux
>> 4.12.
>>
>> ```
>> irq: Invalid fwnode type (2) for irqdomain
Hi Paolo,
On Thu, Jul 6, 2017 at 3:01 AM, Paolo Pisati wrote:
> This patch adds support to the FPGA manager for programming
> MachXO2 device’s internal flash memory, via slave SPI.
>
> Signed-off-by: Paolo Pisati
> ---
> drivers/fpga/Kconfig | 7 ++
> drivers/fpga/Makefile | 1 +
On Thu, Jul 6, 2017 at 11:17 PM, Tomasz Figa wrote:
> On Thu, Jul 6, 2017 at 11:10 PM, Christoph Hellwig wrote:
>> On Thu, Jul 06, 2017 at 12:09:45PM +0100, Robin Murphy wrote:
>>> I suppose another option is to just make the IOMMU and DMA ops a
>>> self-contained non-modular driver mirroring
On Thu, Jul 6, 2017 at 4:06 PM, Tomasz Figa wrote:
> On Thu, Jul 6, 2017 at 11:02 PM, Arnd Bergmann wrote:
>> On Thu, Jul 6, 2017 at 3:49 PM, Tomasz Figa wrote:
>>> On Thu, Jul 6, 2017 at 10:31 PM, Tomasz Figa wrote:
>>
On the other hand, if it's strictly about base/dma-mapping, we might
This patchset contains only two patches.
The first one is a minor fix for the A10 pinctrl driver, add a function
of a pin, which used to be missing in A10/A20 pinctrl driver.
The second one is the real R40 pinctrl part, with fixes suggested by
Chen-Yu.
Icenowy Zheng (2):
pinctrl: sunxi: add a
The PH16 pin has a function with mux id 0x5, which is the DET pin of the
"sim" (smart card reader) IP block.
This function is missing both in the old A10 and A20 drivers, so it's
not found during the merge of these two drivers.
Add it to the driver. As we now merged A20 pinctrl driver to the A10
On 7/6/2017 3:24 AM, Max Filippov wrote:
Hi Babu,
On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger wrote:
Max, Do you have any concerns about xtensa?
no, not ATM. I still haven't got a chance to look closer at moving endianness
macros back to Kconfig for xtensa.
Thanks. Greg, Can you please
R40 is said to be an upgrade of A20, and its pin configuration is also
similar to A20 (and thus similar to A10).
Add support for R40 to the A10 pinctrl driver.
Signed-off-by: Icenowy Zheng
---
drivers/pinctrl/sunxi/Kconfig | 2 +-
drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c | 280
On Thu, Jul 06, 2017 at 04:09:18PM +0200, Mike Galbraith wrote:
> Greetings,
>
> I'm seeing $subject in master as of this merge window. I don't see it
> with my usual stripped down PREEMPT_VOLUNTARY or an enterprise-ish
> NOPREEMPT config, but do see it with the attached, derived from my
>
On Thu, Jul 06, 2017 at 09:28:06AM -0500, Babu Moger wrote:
> On 7/6/2017 3:24 AM, Max Filippov wrote:
> > Hi Babu,
> >
> > On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger wrote:
> > > Max, Do you have any concerns about xtensa?
> > no, not ATM. I still haven't got a chance to look closer at moving
On 07/06/2017 03:55 PM, Andrew Lunn wrote:
>> diff --git a/Documentation/devicetree/bindings/net/fsl-fec.txt
>> b/Documentation/devicetree/bindings/net/fsl-fec.txt
>> index 6f55bdd..1766579 100644
>> --- a/Documentation/devicetree/bindings/net/fsl-fec.txt
>> +++
On Thu, Jun 29, 2017 at 08:04:17AM -0700, Guenter Roeck wrote:
> On Thu, Jun 29, 2017 at 08:39:59AM -0500, Christopher Bostic wrote:
> >
> >
> > On 6/28/17 10:33 PM, Guenter Roeck wrote:
> > >On 06/28/2017 05:28 PM, Christopher Bostic wrote:
> > >>Describe device tree optional properties:
> > >>
On Thu, Jul 6, 2017 at 4:24 PM, Tomasz Figa wrote:
> On Thu, Jul 6, 2017 at 11:17 PM, Tomasz Figa wrote:
>> On Thu, Jul 6, 2017 at 11:10 PM, Christoph Hellwig wrote:
>>> On Thu, Jul 06, 2017 at 12:09:45PM +0100, Robin Murphy wrote:
I suppose another option is to just make the IOMMU and DMA
On Thu, Jul 6, 2017 at 11:27 PM, Arnd Bergmann wrote:
> On Thu, Jul 6, 2017 at 4:06 PM, Tomasz Figa wrote:
>> On Thu, Jul 6, 2017 at 11:02 PM, Arnd Bergmann wrote:
>>> On Thu, Jul 6, 2017 at 3:49 PM, Tomasz Figa wrote:
On Thu, Jul 6, 2017 at 10:31 PM, Tomasz Figa wrote:
>>>
> On the
On Thu, Jul 06, 2017 at 08:49:33PM +0800, Ding Tianhong wrote:
> When enable preempt and ftrace, and perform the following steps, the system
> will hang:
> mount -t debugfs nodev /sys/kernel/debug/
> cd /sys/kernel/debug/tracing/
> echo function_graph > current_tracer
>
> This is because the
On Thu, Jul 6, 2017 at 9:30 AM, Paul Moore wrote:
> On Thu, Jul 6, 2017 at 1:32 AM, John Stultz wrote:
>> Hey folks,
>>I updated my HiKey kernel tree to linus/master today and it stopped
>> booting (hitting errors at init and reseting immediately into
>> bootloader mode):
>>
>> [
On Thu, Jul 6, 2017 at 3:03 PM, Sudeep Holla wrote:
>
>
> On 06/07/17 10:27, Jassi Brar wrote:
>> On Thu, Jul 6, 2017 at 2:48 PM, Sudeep Holla wrote:
>>> Hi Jassi,
>>>
>>> On 06/07/17 07:28, Jassi Brar wrote:
On Wed, Jul 5, 2017 at 11:32 PM, Sudeep Holla wrote:
>
> I have
On Thu, Jul 6, 2017 at 11:35 PM, Arnd Bergmann wrote:
> On Thu, Jul 6, 2017 at 4:24 PM, Tomasz Figa wrote:
>> On Thu, Jul 6, 2017 at 11:17 PM, Tomasz Figa wrote:
>>> On Thu, Jul 6, 2017 at 11:10 PM, Christoph Hellwig wrote:
On Thu, Jul 06, 2017 at 12:09:45PM +0100, Robin Murphy wrote:
On 07/06/17 15:44, Todor Tomov wrote:
> Hello Hans,
>
> Thank you for the time spent to review.
>
> On 07/03/2017 02:32 PM, Hans Verkuil wrote:
>> On 06/19/2017 04:48 PM, Todor Tomov wrote:
>>> These files handle the video device nodes of the camss driver.
>>>
>>> Signed-off-by: Todor Tomov
>>>
On Thu, 6 Jul 2017, Colin King wrote:
> From: Colin Ian King
>
> When us->extra is null the driver is not initialized, however, a
> later call to osd200_scsi_to_ata is made that dereferences
> us->extra, causing a null pointer dereference. The code
> currently detects and reports that the
On Thu, Jul 06, 2017 at 02:19:41PM +0100, Mel Gorman wrote:
> On Thu, Jul 06, 2017 at 02:04:31PM +0100, Roman Gushchin wrote:
> > High-order allocations are obviously more costly, and it's very useful
> > to know how many of them happens, if there are any issues
> > (or suspicions) with memory
On Thu, Jul 06, 2017 at 12:29:12AM +0100, Al Viro wrote:
> On Thu, Jul 06, 2017 at 12:52:35AM +0200, Christoph Hellwig wrote:
> > On Wed, Jul 05, 2017 at 11:38:21PM +0100, Al Viro wrote:
> > > Sure, makes sense - especially since it's not too widely spread yet.
> >
> > Do you want to do that
On Thu, Jul 06, 2017 at 03:46:59PM +0200, Laurent Dufour wrote:
> On 05/07/2017 20:50, Peter Zijlstra wrote:
> > On Fri, Jun 16, 2017 at 07:52:33PM +0200, Laurent Dufour wrote:
> >> @@ -2294,8 +2295,19 @@ static bool pte_map_lock(struct vm_fault *vmf)
> >>if (vma_has_changed(vmf->vma,
Hi Linus,
Here are a couple of changes to the AFS filesystem:
(1) Fix to permission handling on AFS directories.
(2) Add three xattrs so that you can determine an AFS file's cell, volume
and fid.
David
---
David Howells (1):
afs: Add metadata xattrs
Marc Dionne (1):
afs:
Add xattrs to allow the user to get/set metadata in lieu of having pioctl()
available. The following xattrs are now available:
(*) afs.cell
The name of the cell in which the vnode's volume resides.
(*) afs.fid
The volume ID, vnode ID and vnode uniquifier of the file as three hex
From: Marc Dionne
The AFS_ACE_READ and AFS_ACE_WRITE permission bits should not
be used to make access decisions for the directory itself. They
are meant to control access for the objects contained in that
directory.
Reading a directory is allowed if the AFS_ACE_LOOKUP bit is set.
This would
On Wed, 5 Jul 2017 22:08:12 +0530
"Gautham R. Shenoy" wrote:
> From: "Gautham R. Shenoy"
>
> The details of the platform idle state are exposed by the firmware to
> the kernel via device tree.
>
> In the current code, we parse the device tree twice :
>
> 1) During the boot up in
From: Jeff Layton
The init_once routine memsets the whole object to 0, and then
explicitly sets some of the fields to 0 again. Just remove the explicit
initializations.
Signed-off-by: Jeff Layton
---
security/integrity/iint.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
On Thu, Jul 6, 2017 at 9:19 AM, Mel Gorman wrote:
> The alloc counter updates are themselves a surprisingly heavy cost to
> the allocation path and this makes it worse for a debugging case that is
> relatively rare. I'm extremely reluctant for such a patch to be added
> given that the
On Thu, 06 Jul, at 08:31:07AM, Naoya Horiguchi wrote:
>
> KASLR chooses kernel location from E820_TYPE_RAM regions by walking over
> e820 entries now. E820_TYPE_RAM includes EFI_BOOT_SERVICES_CODE and
> EFI_BOOT_SERVICES_DATA, so those regions can be the target. According to
> UEFI spec, all
Daniel Vetter writes:
> Extending the reported/sw vblank counter to u64 makes sense imo, but do we
> have to extend the driver interfaces too? If there's no 64 bit hw vblank
> currently I think I'd be good to postpone that part, simply because I'm
> too lazy to audit all the drivers for
1301 - 1400 of 1854 matches
Mail list logo
