This very minor change is still useful because it aligns
ARC PGU driver name with other DRM drivers and makes usage of
that driver name a bit easier.
For example in libdrm's test app we'll use "arcpgu" instead of
a bit more ugly "drm-arcpgu".
Signed-off-by: Alexey Brodkin
Cc: Daniel Vetter
---
From: Colin Ian King
trivial fix to spelling mistake in MODULE_DESCRIPTION text
Signed-off-by: Colin Ian King
---
drivers/i2c/busses/i2c-tegra-bpmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-tegra-bpmp.c
b/drivers/i2c/busses/i2c-tegra-bpmp.c
i
On Fri 21-04-17 10:35:03, Joonsoo Kim wrote:
[...]
> Hello, Michal.
>
> If you don't have any more question, I will send next version with
> updated cover-letter.
I am sorry but I am bussy as hell this week and didn't get to your email
yet. I will try as soon as possible.
--
Michal Hocko
SUSE La
Hi all,
Changes since 20170420:
The arm tree gained a build failure so I used the version from
next-20170420.
The pci tree gained a conflict against the kbuild tree.
The pm tree gained conflict against the arm-soc tree.
The rdma tree gained a build failure so I used the version from
next
Am 21.04.2017 um 01:21 schrieb Mauro Carvalho Chehab :
> - I'm not a python programmer ;-) I just took Markus "generic" kernel-cmd
> code, hardcoding there a call to the script.
>
> With (a lot of) time, I would likely be able to find a solution to add
> the entire ABI logic there, but, in th
On 04/21/2017 05:11 AM, Dmitry Torokhov wrote:
On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Xen input para-virtual protocol defines string constants
used by both back and frontend. Use those instead of
explicit strings in the frontend d
Hi, Dmitry!
On 04/21/2017 05:10 AM, Dmitry Torokhov wrote:
Hi Oleksandr,
On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Extend xen_kbdfront to provide multi-touch support
to unprivileged domains.
Signed-off-by: Oleksandr Andrushchenko
On 4/20/17 10:53 PM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 2:54 AM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the pm tree got a conflict in:
include/dt-bindings/genpd/k2g.h
between commit:
7cc119f29b19 ("dt-bindings: Add TI SCI PM Domains")
from the arm-soc tre
On 04/20/2017 06:49 PM, Joe Perches wrote:
> On Thu, 2017-04-20 at 17:39 +0200, Jerome Forissier wrote:
>> When using checkpatch on out-of-tree code, it may occur that some
>> project-specific types are used, which will cause spurious warnings.
>> Add the --typedefsfile option as a way to extend
> > I think it doesn't make sense to print a dev_err and return ENODEV which
> > is treated by the driver core as a non-error. It means "not present, but
> > OK". You probably want other error codes here.
>
> How about -EINVAL for these -ENODEV error codes? Do you have any suggestion?
-EINVAL wi
Hello Mike,
On 03/21/2017 03:01 PM, Mike Rapoport wrote:
> Hello Michael,
>
> On Mon, Mar 20, 2017 at 09:08:05PM +0100, Michael Kerrisk (man-pages) wrote:
>> Hello Andrea, Mike, and all,
>>
>> Mike: thanks for the page that you sent. I've reworked it
>> a bit, and also added a lot of further info
+++ Kees Cook [12/04/17 16:16 -0700]:
Accessing the mod structure (e.g. for mod->name) prior to having completed
check_modstruct_version() can result in writing garbage to the error logs
if the layout of the mod structure loaded from disk doesn't match the
running kernel's mod structure layout. T
From: Jeroen Hofstee
KBuild abuses the asm statement to write to a file and
clang chokes about these invalid asm statements. Hack it
even more by fooling this is actual valid asm code.
[masahiro:
Import Jeroen's work for U-Boot:
http://patchwork.ozlabs.org/patch/375026/
Tweak sed script a lit
1/2 is a trivial cleanup of sed script
2/2 imports clang work-around from U-Boot.
Changes in v2:
- V1 did not work with LLVM's integrated assembler because
it uses instead of around the .ascii string.
Restore [:space:].
Jeroen Hofstee (1):
kbuild: fix asm-offset generation to work
This part ended up in redundant code after touched by multiple
people.
[1] Commit 3234282f33b2 ("x86, asm: Fix CFI macro invocations to
deal with shortcomings in gas") added parentheses for defined
expressions to support old gas for x86.
[2] Commit a22dcdb0032c ("x86, asm: Fix ancient-GAS workaro
On 04/21/2017 02:17 AM, Zi Yan wrote:
> From: Zi Yan
>
> If one of callers of page migration starts to handle thp,
> memory management code start to see pmd migration entry, so we need
> to prepare for it before enabling. This patch changes various code
> point which checks the status of given pm
On Wed, 2017-04-19 at 15:06 +0800, Huang, Ying wrote:
> From: Huang Ying
>
> In this patch, splitting huge page is delayed from almost the first
> step of swapping out to after allocating the swap space for the
> THP (Transparent Huge Page) and adding the THP into the swap cache.
> This will batc
On Thu, Apr 20, 2017 at 10:24 PM, Serge E. Hallyn wrote:
> On Fri, Apr 21, 2017 at 01:09:59AM -0400, Matt Brown wrote:
>> On 04/20/2017 01:41 PM, Serge E. Hallyn wrote:
>> >Quoting m...@nmatt.com (m...@nmatt.com):
>> >>On 2017-04-20 11:19, Serge E. Hallyn wrote:
>> >>>Quoting Matt Brown (m...@nmat
On Fri, Apr 21, 2017 at 2:54 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the pm tree got a conflict in:
>
> include/dt-bindings/genpd/k2g.h
>
> between commit:
>
> 7cc119f29b19 ("dt-bindings: Add TI SCI PM Domains")
>
> from the arm-soc tree and commit:
>
> 45da8edd
Hi Masahiro,
On 20.04.2017 11:56, Masahiro Yamada wrote:
> Include instead of relative path from include/drm, then
> remove the -Iinclude/drm compiler flag.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> drivers/gpu/drm/bridge/Makefile| 2 --
> drivers/gpu/drm/bridge/nxp-ptn3460.c | 10
Remove the individual encrypt/decrypt function for easch algorithm.
This is in prepration of adding more crypto algorithms supported by
hardware. While at that simplify create_ctx_hdr/create_input_list
function interfaces.
Signed-off-by: George Cherian
---
drivers/crypto/cavium/cpt/cptvf_algs.c
Mailbox interrupt is common and it is not an error interrupt.
So downgrade the print from dev_err to dev_dbg.
Signed-off-by: George Cherian
---
drivers/crypto/cavium/cpt/cptvf_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/cavium/cpt/cptvf_main.c
b/dr
This series adds more algorithem support for CPT.
Add support for
-ecb(aes)
-cfb(aes)
-ecb(des3_ede)
Some cleanups too.
George Cherian (3):
crypto: cavium: Downgrade the annoying misc interrupt print from
dev_err to dev_dbg
crypto: cavium: Remove the individual e
Add more algorithm support for the driver.
Add support for ecb(aes), cfb(aes) and ecb(des3_ede).
Signed-off-by: George Cherian
---
drivers/crypto/cavium/cpt/cptvf_algs.c | 63 ++
1 file changed, 63 insertions(+)
diff --git a/drivers/crypto/cavium/cpt/cptvf_algs.c
Looks good,
Reviewed-by: Christoph Hellwig
On 20-04-17, 22:14, Robert Jarzmik wrote:
> Viresh Kumar writes:
>
> > Compiling the DT file with W=1, DTC warns like follows:
> >
> > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a
> > unit name, but no reg property
> >
> > Fix this by replacing '@' with '-' as the OPP node
On 20-04-17, 18:09, Krzysztof Kozlowski wrote:
> On Thu, Apr 20, 2017 at 04:25:07PM +0530, Viresh Kumar wrote:
> > Compiling the DT file with W=1, DTC warns like follows:
> >
> > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a
> > unit name, but no reg property
> >
> > Fix th
On 4/18/2017 2:39 PM, Niklas Cassel wrote:
From: Niklas Cassel
The hardware has a LPI interrupt.
There is already code in the stmmac driver to parse and handle the
interrupt. However, this information was missing from the DT binding.
At the same time, improve the description of the existing in
On Fri, Apr 21, 2017 at 01:09:59AM -0400, Matt Brown wrote:
> On 04/20/2017 01:41 PM, Serge E. Hallyn wrote:
> >Quoting m...@nmatt.com (m...@nmatt.com):
> >>On 2017-04-20 11:19, Serge E. Hallyn wrote:
> >>>Quoting Matt Brown (m...@nmatt.com):
> On 04/19/2017 07:53 PM, Serge E. Hallyn wrote:
> >
On Fri, Apr 21, 2017 at 05:15:46AM +, Andriy Gelman wrote:
> This is a patch to the ks_wlan_ioctl.h file that fixes paranthesis error
> found by the checkpatch.pl tool
No, it also does other things :(
Also, please fix up the subject to look like other patches done for this
file/driver.
And f
This is a patch to the ks_wlan_ioctl.h file that fixes paranthesis error
found by the checkpatch.pl tool
Signed-off-by: Andriy Gelman
---
drivers/staging/ks7010/ks_wlan_ioctl.h | 53 +-
1 file changed, 26 insertions(+), 27 deletions(-)
diff --git a/drivers/stagin
On 04/20/2017 01:41 PM, Serge E. Hallyn wrote:
Quoting m...@nmatt.com (m...@nmatt.com):
On 2017-04-20 11:19, Serge E. Hallyn wrote:
Quoting Matt Brown (m...@nmatt.com):
On 04/19/2017 07:53 PM, Serge E. Hallyn wrote:
Quoting Matt Brown (m...@nmatt.com):
On 04/19/2017 12:58 AM, Serge E. Hallyn
On one system found strange "no compatible bridge window" warning
even we already had pref_compat support that add extra pref bit for device
resource.
PCI: Claiming :00:01.0: Resource 14: 00020001..000200010fff
[10220c]
PCI: Claiming :01:00.0: Resource 1: 00020001..000
Hi Bjorn,
Please check sparc related 64bit resource handling patches.
patch 1-8: parse MEM64 for sparc and other system with OF.
So device 64bit resource could find their parent resource.
patch 9-12: MMIO64 handling enhancement
treat non-pref mmio64 as pref mmio64 if all bridges
For device resource PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource.
This patch set IORESOUCE_MEM_64 for 64bit resource during OF device
resource flags parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link: https://bugzilla
After we added 64bit mmio parsing, we got some "no compatible bridge window"
warning on anther new model that support 64bit resource.
It turns out that we can not use mem_space.start as 64bit mem space
offset, aka there is mem_space.start != offset.
Use child_phys_addr to calculate exact offset a
If host bridge does not have mmio64 above 4G, We don't need to
treat device non-pref mmio64 as as pref mmio64.
Signed-off-by: Yinghai Lu
Tested-by: Khalid Aziz
---
drivers/pci/setup-bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/s
Add pci_find_bus_resource() to return bus resource for input resource.
In some case, we may only have bus instead of dev.
It is same as pci_find_parent_resource, but take bus as input.
Signed-off-by: Yinghai Lu
---
drivers/pci/pci.c | 27 ---
include/linux/pci.h | 2 +
We still get "no compatible bridge window" warning on sparc T5-8
after we add support for 64bit resource parsing for root bus.
PCI: scan_bus[/pci@300/pci@1/pci@0/pci@6] bus no 8
PCI: Claiming :00:01.0: Resource 15: 8001..8004afff
[220c]
PCI: Claiming :01:00.0: Resou
If any bridge up to root only have 32bit pref mmio, We don't need to
treat device non-pref mmio64 as as pref mmio64.
We need to move pci_bridge_check_ranges calling early.
For parent bridges pref mmio BAR may not allocated by BIOS, res flags
is still 0, we need to have it correct set before we che
Hi
> sound/soc/sh/rcar/adg.c:462:54-55: Unneeded semicolon
>
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
>
> CC: Kuninori Morimoto
> Signed-off-by: Fengguang Wu
Where is my brown paper bag ?
Acked-by: Kuninori Morimoto
> ---
>
> adg.c |
Same as sparc version.
Make resource with consistent sequence
like other arch or directly from pci_read_bridge_bases(),
even when non-pref mmio is missing, or out of ordering in firmware reporting.
Just hold i = 1 for non pref mmio, and i = 2 for pref mmio.
Signed-off-by: Yinghai Lu
Cc: linuxpp
For device resource with PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource.
so this patch set IORESOUCE_MEM_64 for 64bit resource during OF device
resource flags parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link: https://
For device resource PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource.
This patch set IORESOUCE_MEM_64 for 64bit resource during OF device
resource flags parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link: https://bugzilla
>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit
resources), we change the logic for pref mmio allocation:
When bridge pref support mmio64, we will only put children pref
that support mmio64 into it, and will put children pref mmio32
into bridge's non-pref mmio32.
That c
Add has_mem64 for struct host_bridge, on root bus that does not support
mmio64 above 4g, will not set that.
We will use that info next two following patches:
1. Don't treat non-pref mmio64 as pref mmio, so will not put
it under bridge's pref range when rescan the devices
2. will keep pref mmio6
On one system found bunch of claim resource fail from pci device.
pci_sun4v f02b894c: PCI host bridge to bus :00
pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus
address [0x-0xfff])
pci_bus :00: root bus resource [mem 0x2-0x27eff] (b
Thanks Stephen. Looks good to me.
Logan
On 20/04/17 08:10 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in
> initializer
sound/soc/sh/rcar/adg.c:462:54-55: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Kuninori Morimoto
Signed-off-by: Fengguang Wu
---
adg.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/sound/soc/sh/rcar/adg.c
+++ b/s
Hi Matthias,
2017-04-05 2:27 GMT+09:00 Matthias Kaehlcke :
> From: Vinícius Tinti
>
> Add rules to kbuild in order to generate LLVM bitcode files with the .ll
> extension when using clang.
First, I'd like to be sure about the terminology "LLVM bitcode"
because "bitcode" sounds like human-unrea
On Thu, Apr 20, 2017 at 4:07 PM, Stephen Bates wrote:
>>> Yes, this makes sense I think we really just want to distinguish host
>>> memory or not in terms of the dev_pagemap type.
>>
>>> I would like to see mutually exclusive flags for host memory (or not) and
>>> persistence (or not).
>>>
>>
>>
On Fri, Apr 21, 2017 at 02:45:40PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/misc/Makefile
>
> between commit:
>
> 58c89c8aa0e8 ("misc: Add host side PCI driver for PCI test function device")
>
> from the pci
Hi Linus,
Please pull two final powerpc fixes for 4.11:
The following changes since commit 4749228f022893faf54a3dbc70796f78b7d4f342:
powerpc/crypto/crc32c-vpmsum: Fix missing preempt_disable() (2017-04-07
21:12:58 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
drivers/misc/Makefile
between commit:
58c89c8aa0e8 ("misc: Add host side PCI driver for PCI test function device")
from the pci tree and commits:
6c4e97678501 ("drivers/misc: Add Aspeed LPC control driver")
51c1
Hi Cyril,
On Thu, Apr 20, 2017 at 02:57:50PM +0200, Cyril Hrubis wrote:
> >
> > In my opinion this is a valid behavior, and the test is just weird; it's
> > passing
> > in *both* an unaddressable payload and an invalid description, so it's not
> > clear
> > which case it's meant to be testing.
On Thu, Apr 20, 2017 at 09:28:20AM +0200, Michal Hocko wrote:
> On Thu 20-04-17 10:27:55, Joonsoo Kim wrote:
> > On Mon, Apr 17, 2017 at 10:15:15AM +0200, Michal Hocko wrote:
> [...]
> > > Which pfn walkers you have in mind?
> >
> > For example, kpagecount_read() in fs/proc/page.c. I searched it b
On 04/21/2017 02:17 AM, Zi Yan wrote:
> From: Naoya Horiguchi
>
> Introduces CONFIG_ARCH_ENABLE_THP_MIGRATION to limit thp migration
> functionality to x86_64, which should be safer at the first step.
>
> Signed-off-by: Naoya Horiguchi
Aneesh's latest HugeTLB migration enablement on powerpc sh
On Thu, Apr 20, 2017 at 08:38:16PM -0700, Guenter Roeck wrote:
> On 04/20/2017 12:53 PM, Greg Kroah-Hartman wrote:
> > On Thu, Apr 20, 2017 at 04:28:03PM +0200, Greg Kroah-Hartman wrote:
> > > On Thu, Apr 20, 2017 at 06:46:11AM -0700, Guenter Roeck wrote:
> > > > On 04/19/2017 11:34 PM, Greg Kroah-
Add support for adding min/max values for the inband sensors copied by
OCC to main memory. And also add current(mA) sensors to the list.
Signed-off-by: Shilpasri G Bhat
---
drivers/hwmon/ibmpowernv.c | 55 --
1 file changed, 53 insertions(+), 2 deletio
On 04/21/2017 02:17 AM, Zi Yan wrote:
> From: Naoya Horiguchi
>
> TTU_MIGRATION is used to convert pte into migration entry until thp split
> completes. This behavior conflicts with thp migration added later patches,
> so let's introduce a new TTU flag specifically for freezing.
>
> try_to_unmap
Hi all,
Today's linux-next merge of the usb tree got a conflict in:
Documentation/media/v4l-drivers/philips.rst
between commit:
9b06f754133c ("convert philips.txt to ReST and add to media docs")
from the jc_docs tree and commit:
21470e32ca7f ("usb: fix some references for /proc/bus/usb"
On Fri, Apr 21, 2017 at 11:42:01AM +1000, Michael Ellerman wrote:
> "Paul E. McKenney" writes:
> > On Thu, Apr 20, 2017 at 05:28:32PM +0200, Paolo Bonzini wrote:
> >> On 20/04/2017 05:40, Michael Ellerman wrote:
> >> > "Paul E. McKenney" writes:
> >> >
> >> > This change seems to have had the no
On Wed, 2017-04-19 at 16:35 -0500, Rob Herring wrote:
> On Thu, Apr 13, 2017 at 03:33:05PM +0800, Minghsiu Tsai wrote:
> > If the mdp_* nodes are under an mdp sub-node, their corresponding
> > platform device does not automatically get its iommu assigned properly.
> >
> > Fix this by moving the md
On 04/21/2017 02:17 AM, Zi Yan wrote:
> From: Naoya Horiguchi
>
> Introduce a separate check routine related to MPOL_MF_INVERT flag.
> This patch just does cleanup, no behavioral change.
Can you please send it separately first, this should be debated
and merged quickly and not hang on to the ser
kernel coding style doesn't allow the return statement
in void function.
Signed-off-by: Surenderp
---
Changes for v2:
corrected subject line as suggested
Changes for v3:
modified from line as suggested by Greg KH
placed a semicolon in label for fixing build error
---
drivers/staging/rtl8188eu/ha
On Thu, Apr 20, 2017 at 11:58 PM, Rob Herring wrote:
> On Tue, Apr 18, 2017 at 09:34:16AM +0200, Quentin Schulz wrote:
>> The X-Powers AXP20X and AXP22X PMICs can have a battery as power supply.
>>
>> This patch adds the DT binding documentation for the battery power
>> supply which gets various d
From: Orson Zhai
SC9860G is a 8 cores of A53 SoC with 4G LTE support SoC from Spreadtrum.
According to regular hierarchy of sprd dts, whale2.dtsi contains SoC
peripherals IP nodes, sc9860.dtsi contains stuff related to ARM core stuff
and sp9860g dts is for the board level.
Signed-off-by: Orson
dax_invalidate_mapping_entry() currently removes DAX exceptional entries
only if they are clean and unlocked. This is done via:
invalidate_mapping_pages()
invalidate_exceptional_entry()
dax_invalidate_mapping_entry()
However, for page cache pages removed in invalidate_mapping_pages() there
Users of DAX can suffer data corruption from stale mmap reads via the
following sequence:
- open an mmap over a 2MiB hole
- read from a 2MiB hole, faulting in a 2MiB zero page
- write to the hole with write(3p). The write succeeds but we incorrectly
leave the 2MiB zero page mapping intact.
-
On 04/20/2017 12:53 PM, Greg Kroah-Hartman wrote:
On Thu, Apr 20, 2017 at 04:28:03PM +0200, Greg Kroah-Hartman wrote:
On Thu, Apr 20, 2017 at 06:46:11AM -0700, Guenter Roeck wrote:
On 04/19/2017 11:34 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.50 re
On Tue, Apr 18, 2017 at 12:22 PM, Chen-Yu Tsai wrote:
> The pinmux setting nodes all have an address element in their node
> names, however the pinctrl node does not have #address-cells.
>
> Rename the existing pinmux setting nodes and labels in sun8i-a83t.dtsi,
> dropping identifiers for function
On 2017-04-20 19:03, Marek Vasut wrote:
> On 04/21/2017 03:07 AM, Stefan Agner wrote:
>> Add support for i.MX 7 SoC. The i.MX 7 has a slightly different
>> clock architecture requiring only two clocks to be referenced.
>> The IP is slightly different compared to i.MX 6SoloX, but currently
>> none o
From: Ryosuke Saito
Since we use the default primary handler for the irq, IRQF_ONESHOT must
be set. Otherwise the request fails and the following errors are
displayed:
genirq: Threaded irq requested with handler=NULL and !ONESHOT for irq 129
sbs-battery 0-000b: Failed to request irq: -22
Signed
Hi Megha,
[auto build test ERROR on next-20170420]
[also build test ERROR on v4.11-rc7]
[cannot apply to crypto/master sparc-next/master v4.9-rc8 v4.9-rc7 v4.9-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
We actually can't allow the missing of the regualor name, thus update
the binding doc to make regulator-name property to be required.
Cc: Mark Rutland
Cc: devicet...@vger.kernel.org
Cc: Mark Brown
Acked-by: Rob Herring
Signed-off-by: Dong Aisheng
---
Documentation/devicetree/bindings/regulat
FYI, we noticed the following commit:
commit: 73821bb516920b2b38732ce992d11c08c5d8bd7d ("your mail")
url:
https://github.com/0day-ci/linux/commits/Michal-Hocko/mm-consider-zone-which-is-not-fully-populated-to-have-holes/20170420-173046
in testcase: trinity
with following
On 04/21/2017 03:07 AM, Stefan Agner wrote:
> This patchset adds support for i.MX 7 SoC for the GPMI NAND controller.
> There have been similar patchsets already:
> https://lkml.org/lkml/2016/2/23/912
>
> However, this patchset does not make use of any of the new features.
> The current feature se
Hi Doug,
On Thu, 20 Apr 2017 22:21:15 -0400 Doug Ledford wrote:
>
> I created a fix and added it to my tree.
Thanks.
--
Cheers,
Stephen Rothwell
On Thu, 2017-04-20 at 23:02 +0200, SF Markus Elfring wrote:
> >
> > I've dropped this entire series. If you want me to consider it,
> > you
> > need to respin it with the following changes:
>
> How do you think about to integrate any of my update suggestions
> which you do not find controversial
Hi, Dann,
On 04/21/2017 04:57 AM, dann frazier wrote:
> On Thu, Mar 30, 2017 at 9:26 AM, zhichang.yuan
> wrote:
>> On some platforms(such as Hip06/Hip07), the legacy ISA/LPC devices access I/O
>> with some special host-local I/O ports known on x86. To access the I/O
>> peripherals, an indirect-
> On 20 Apr 2017, at 20:40, Alexander Graf wrote:
>
> The file open flags (O_foo) are platform specific and should never go
> out to an interface that is not local to the system.
>
> Unfortunately these flags have leaked out onto the wire in the cephfs
> implementation. That lead to bogus flags
Hi Joe,
On Thu, 20 Apr 2017 18:58:55 -0700 Joe Perches wrote:
>
> Pretty sure there were crossing commits adding PDBG()
> as the original patches were written against next-20170209
>
> From my tree:
>
> $ git log --pretty=oneline -5 747edc68212781296de30dd2b4e63711240da7a9
> 747edc68212781296de
6req->rsvd);
> > ^
> >
> > Caused by commit
> >
> > a9a42886d0b3 ("cxgb4: Convert PDBG to pr_debug")
> >
> > I have used the rdma tree from next-20170420 for today.
> >
> > There was another PDBG() missed in that file as wel
On Fri, Apr 14, 2017 at 5:19 AM, Rob Herring wrote:
> On Fri, Apr 07, 2017 at 10:27:10PM +0930, Andrew Jeffery wrote:
>> Signed-off-by: Andrew Jeffery
>> ---
>> .../devicetree/bindings/pinctrl/pinctrl-aspeed.txt | 40
>> +-
>> 1 file changed, 31 insertions(+), 9 deletions(-)
On Wed, Apr 19, 2017 at 11:36 PM, Olof Johansson wrote:
> On Wed, Apr 12, 2017 at 12:29:10PM +0930, Joel Stanley wrote:
>> Hello Arnd, Olof,
>>
>> These are the Aspeed defconfig changes for 4.12.
>>
>> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>>
>> Linux 4.11-
Paolo Bonzini writes:
> Michael, if you want to move the two srcu structs at the end of struct
> kvm, that would be fine by me. Please send a patch yourself so you can
> test it on PPC. Thanks,
Paul beat me to it :)
I've confirmed it fixes the build break and the resulting kernel can
boot a KV
On Thu, 2017-04-20 at 10:15 +0200, Arnd Bergmann wrote:
> We should not select drivers that depend on I2C when that is disabled,
> as it results in a build error:
>
> warning: (SND_SOC_MT2701_WM8960) selects SND_SOC_WM8960 which has unmet
> direct dependencies (SOUND && !M68K && !UML && SND && SN
On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Xen input para-virtual protocol defines string constants
> used by both back and frontend. Use those instead of
> explicit strings in the frontend driver.
>
> Signed-off-by: Oleksandr And
Hi all,
After merging the drm-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in
initializer
.kmap_atomic = tee_shm_op_kmap_atomic,
^
drivers/tee/tee_shm.c:87:17: error: initialization from i
Hi Oleksandr,
On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Extend xen_kbdfront to provide multi-touch support
> to unprivileged domains.
>
> Signed-off-by: Oleksandr Andrushchenko
> ---
> drivers/input/misc/xen-kbdfront.c | 142
On 04/21/2017 03:07 AM, Stefan Agner wrote:
> Add device specific list of clocks required, and handle all clocks
> in a single for loop. This avoids further code duplication when
> adding i.MX 7 support.
>
> Signed-off-by: Stefan Agner
[...]
> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.h
On 04/21/2017 03:07 AM, Stefan Agner wrote:
> Add support for i.MX 7 SoC. The i.MX 7 has a slightly different
> clock architecture requiring only two clocks to be referenced.
> The IP is slightly different compared to i.MX 6SoloX, but currently
> none of this differences are in use so there is no d
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem - an update to Elan PS/2
driver to allow working on yet another Lifebook.
Changelog:
-
Thorsten Leemhuis (1):
Input: elantech - ad
nfiniband/hw/cxgb4/cm.c:830:5: error: implicit declaration of
> function 'PDBG' [-Werror=implicit-function-declaration]
> PDBG("%s snd_isn %u\n", __func__, t6req->rsvd);
> ^
>
> Caused by commit
>
> a9a42886d0b3 ("cxgb4: Convert PDBG to p
Hi Megha,
[auto build test WARNING on next-20170420]
[also build test WARNING on v4.11-rc7]
[cannot apply to crypto/master sparc-next/master v4.9-rc8 v4.9-rc7 v4.9-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Frank Rowand writes:
> On 04/20/17 09:51, Tyrel Datwyler wrote:
>> On 04/19/2017 09:43 PM, Frank Rowand wrote:
...
>>> Which ends up being this code:
>>>
>>>of_platform_default_populate_init()
>>> of_platform_default_populate()
>>> of_platform_populate()
>>> [[ of_f
Hello,
On (04/20/17 15:11), Petr Mladek wrote:
[..]
> Good analyze. I would summarize it that we need to be careful of:
>
> + logbug_lock
> + PRINTK_SAFE_CONTEXT
> + locks used by console drivers
>
> The first two things are easy to check. Except that a check for logbuf_lock
> might produc
On Fri, Apr 21, 2017 at 3:59 AM, Priit Laes wrote:
> On Fri, Apr 07, 2017 at 03:38:05PM +0200, Maxime Ripard wrote:
>> Hi Priit,
>>
>> On Tue, Apr 04, 2017 at 08:09:19PM +, Priit Laes wrote:
>> > > > +/* Not documented on A10 */
>> > > > +static SUNXI_CCU_GATE(pll_periph_sata_clk, "pll-periph-
"Paul E. McKenney" writes:
> On Thu, Apr 20, 2017 at 05:28:32PM +0200, Paolo Bonzini wrote:
>> On 20/04/2017 05:40, Michael Ellerman wrote:
>> > "Paul E. McKenney" writes:
>> >
>> > This change seems to have had the non-obvious effect of breaking the
>> > powerpc KVM build.
...
>>
>> Michael, i
icit-function-declaration]
PDBG("%s snd_isn %u\n", __func__, t6req->rsvd);
^
Caused by commit
a9a42886d0b3 ("cxgb4: Convert PDBG to pr_debug")
I have used the rdma tree from next-20170420 for today.
There was another PDBG() missed in that file as well.
--
Cheers,
Stephen Rothwell
1 - 100 of 914 matches
Mail list logo
