On Mon, Jan 1, 2018 at 8:02 PM, David Lechner wrote:
> This adds a new driver for Sitronix ST7735R display panels.
>
> This has been tested using an Adafruit 1.8" TFT.
>
> Signed-off-by: David Lechner
> Reviewed-by: Noralf Trønnes
Am 01.01.2018 um 19:08 schrieb Ilia Mirkin:
On Sun, Dec 31, 2017 at 3:53 PM, Mike Galbraith wrote:
On Sun, 2017-12-31 at 13:27 -0500, Ilia Mirkin wrote:
On Tue, Dec 19, 2017 at 8:45 AM, Christian König
wrote:
Am 19.12.2017 um 11:39 schrieb
The mxc_rtc_remove is incorrectly annotated as __exit:
`mxc_rtc_remove' referenced in section `.data' of drivers/rtc/rtc-mxc_v2.o:
defined in discarded section `.exit.text' of drivers/rtc/rtc-mxc_v2.o
This should not be done, as devices can be dynamically bound
and unbound to a driver.
Fixes:
Christoph Hellwig writes:
> We want to use the dma_direct_ namespace for a generic implementation,
> so rename powerpc to the second best choice: dma_nommu_.
I'm not a fan of "nommu". Some of the users of direct ops *are* using an
IOMMU, they're just setting up a 1:1 mapping once
On 02/01/18 00:58, Paolo Bonzini wrote:
The POSTED_INTR_NV field is constant (though it differs between the vmcs01 and
vmcs02), there is no need to reload it on vmexit to L1.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/vmx.c | 3 ---
1 file changed, 3 deletions(-)
On 02/01/2018 at 13:10:07 +0800, Baolin Wang wrote:
> From our investigation for all RTC drivers, 1 driver will be expired before
> year 2017, 7 drivers will be expired before year 2038, 23 drivers will be
> expired before year 2069, 72 drivers will be expired before 2100 and 104
> drivers will be
A bugfix introduce a link failure in configurations without CONFIG_MODULES:
In file included from drivers/media/usb/dvb-usb/pctv452e.c:20:0:
drivers/media/usb/dvb-usb/pctv452e.c: In function 'pctv452e_frontend_attach':
drivers/media/dvb-frontends/stb0899_drv.h:151:36: error: weak declaration of
On Tue, Dec 26, 2017 at 12:37:13PM +0100, Mathieu Malaterre wrote:
> Fix non-fatal warning:
>
> arch/mips/kernel/setup.c:158:13: warning: no previous prototype for
> ‘memory_region_available’ [-Wmissing-prototypes]
> bool __init memory_region_available(phys_addr_t start, phys_addr_t size)
>
On Tue, Jan 02, 2018 at 01:46:54PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for 4.16 merge window below.
>
> It includes a fix in exynos5-usbdrd to enumerate SuperSpeed devices on
> Odroid XU3 and includes fixes/cleanups in Broadcom and Mediatek PHYs.
>
Hi Linus,
Please pull this capabilities fix for v4.15.
The following changes since commit 30a7acd573899fd8b8ac39236eff6468b195ac7d:
Linux 4.15-rc6 (2017-12-31 14:47:43 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
Correct what appears to be a typo in the spelling of pulse.
Signed-off-by: Simon Horman
---
Documentation/devicetree/bindings/timer/renesas,tpu.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Friday 29 December 2017 11:33 PM, Trent Piepho wrote:
> On Fri, 2017-12-29 at 15:46 +0530, Vignesh R wrote:
>> On Friday 29 December 2017 12:24 AM, Trent Piepho wrote:
>> >
>> > > Vignesh has suggested to call virt_addr_valid() instead.
>> > > I think Boris has also told me about this
Make a couple minor short-circuiting order and const changes
- Since the pointed-to objects are never modified through
these pointers, const-qualify type and compressor
variables.
- Test boolean before calling `strcmp()` to take
advantage of short-circuiting.
Joey Pabalinas (2):
`zwap_has_pool` is a simple boolean, so it should be tested first
to avoid unnecessarily calling `strcmp()`. Test `zswap_has_pool`
first to take advantage of the short-circuiting behavior of && in
`__zswap_param_set()`.
Signed-off-by: Joey Pabalinas
1 file changed, 1
The characters pointed to by `zswap_compressor`, `type`, and `compressor`
aren't ever modified. Add const to the static variable and both parameters in
`zswap_pool_find_get()`, `zswap_pool_create()`, and `__zswap_param_set()`
Signed-off-by: Joey Pabalinas
1 file
>From the pci power documentation:
"The driver itself should not call pm_runtime_allow(), though. Instead,
it should let user space or some platform-specific code do that (user space
can do it via sysfs as stated above)..."
However, the S0ix residency cannot be reached without MEI device getting
> On 21 Dec 2017, at 7:43 PM, Daniel Drake wrote:
>
> On Wed, Dec 20, 2017 at 6:53 PM, Brian Norris
> wrote:
>>
>> On Wed, Dec 20, 2017 at 07:00:07PM +0800, Kai-Heng Feng wrote:
>>> This commit causes a regression on some QCA ROME chips. The USB
The series moves dmtimer out of plat-omap to drivers/clocksource.
The series also does a bunch of changes to pwm-omap-dmtimer code
to adapt to the driver migration and clean up plat specific
pdata-quirks and use the dmtimer platform data.
Boot tested on DRA7-EVM and AM437X-GP-EVM.
Compile tested
Wrap the inline functions under OMAP2PLUS/OMAP1 defines.
Signed-off-by: Keerthy
Tested-by: Ladislav Michl
---
arch/arm/plat-omap/include/plat/dmtimer.h | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
On 30.12.2017 22:03, Himanshu Jha wrote:
Use dma_zalloc_coherent for allocating zeroed
memory and remove unnecessary memset function.
Done using Coccinelle.
Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci
0-day tested with no failures.
Suggested-by: Luis R. Rodriguez
Add timer ops to the platform data structure
Signed-off-by: Keerthy
Reviewed-by: Sebastian Reichel
Tested-by: Ladislav Michl
---
include/linux/platform_data/dmtimer-omap.h | 38 ++
1 file
From: Ladislav Michl
In the case of device tree boot the device platform data is usually
NULL so hook the platform data obtained from the match.
As part of un-constify the platform_data pointer.
Signed-off-by: Ladislav Michl
Signed-off-by: Keerthy
Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks.
Signed-off-by: Keerthy
Tested-by: Ladislav Michl
---
drivers/pwm/pwm-omap-dmtimer.c | 39 ++-
1 file changed, 22 insertions(+), 17 deletions(-)
diff
Remove unused timer pdata.
Signed-off-by: Keerthy
Reviewed-by: Sebastian Reichel
Tested-by: Ladislav Michl
---
arch/arm/mach-omap2/pdata-quirks.c | 32
1 file changed, 32 deletions(-)
Move the dmtimer driver out of plat-omap to clocksource.
So that non-omap devices also could use this.
No Code changes done to the driver file only renamed to timer-dm.c.
Also removed the config dependencies for OMAP_DM_TIMER.
Signed-off-by: Keerthy
Reviewed-by: Sebastian
Remove all the unwanted exports from the driver
Signed-off-by: Keerthy
Reviewed-by: Sebastian Reichel
Tested-by: Ladislav Michl
---
arch/arm/plat-omap/dmtimer.c | 27 ---
1 file changed, 27
From: Ladislav Michl
Invalid prescaler value is silently ignored. Fix that
by returning -EINVAL in such case. As invalid value
disabled use of the prescaler, use -1 explicitely for
that purpose.
Signed-off-by: Ladislav Michl
---
The header file is currently under plat-omap directory
under arch/omap. Move this out to an accessible place.
No Code changes done to the header file.
Signed-off-by: Keerthy
Reviewed-by: Sebastian Reichel
Tested-by: Ladislav Michl
Add the timer ops to the platform data
Signed-off-by: Keerthy
Reviewed-by: Sebastian Reichel
Tested-by: Ladislav Michl
---
drivers/clocksource/timer-dm.c | 25 +
1 file changed, 25 insertions(+)
The newly added callback pointers cause a warning for some configurations:
In file included from net/ipv6/af_inet6.c:45:0:
include/linux/netfilter_ipv6.h:38:51: error: 'struct nf_queue_entry' declared
inside parameter list will not be visible outside of this definition or
declaration [-Werror]
On 31 December 2017 at 10:15, Greg Kroah-Hartman
wrote:
>>
>> I re-tested ldt_gdt_64 again locally and in testing LAB. The test
>> failed again so I think this is a regression. I did the bisection
>> which resulted in
>>
>> 2c8e9099aecec2baaac8d34c7b823493f2d0eeed is
Hi,
On 02/01/18 10:54, Aishwarya Pant wrote:
> Hi
>
> In Documentation/arm/OMAP/DSS, there is a description of the DSS and FB sysfs
> interfaces which could be moved to Documentation/ABI.
>
> Would such a change be useful? I can see that the sysfs interface is still in
> testing.
>
> The ABI
If OF_FLATTREE=y, but OF_EARLY_FLATTREE=n:
drivers/tty/serial/earlycon.o: In function `param_setup_earlycon':
earlycon.c:(.init.text+0x3a4): undefined reference to
`early_init_dt_scan_chosen_stdout'
Fix this by moving the early flattree forward declarations and dummy
implementations
On Tue, Jan 2, 2018 at 7:36 AM, Du, Changbin wrote:
> Hi Wysocki and Brown,
> May I know wether you have checked this? Thanks!
There's a commit changing this queued up already, see
https://patchwork.kernel.org/patch/10085579/
Thanks!
On Sat, Dec 23, 2017 at 10:36:53AM +0900, Minchan Kim wrote:
> > code path. It appears that similar situation is possible for them too.
> >
> > The file cache pages will be delete from file cache address_space before
> > address_space (embedded in inode) is freed. But they will be deleted
> >
On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman wrote:
> Christoph Hellwig writes:
>
>> We want to use the dma_direct_ namespace for a generic implementation,
>> so rename powerpc to the second best choice: dma_nommu_.
>
> I'm not a fan of "nommu". Some of the
Hi Cyrille,
On Wed, Dec 27, 2017 at 10:40:00PM +0100, Cyrille Pitchen wrote:
> Hi Rob,
>
> + Ludovic Desroches, maintainer of the DMA controller drivers for AT91 SoCs.
>
> Le 27/12/2017 à 00:23, Rob Herring a écrit :
> > On Sun, Dec 24, 2017 at 05:36:05AM +0100, Cyrille Pitchen wrote:
> >> The
On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim wrote:
> On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote:
>> On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote:
>> > On Fri, Dec 08, 2017 at 03:11:59PM +, Jonathan McDowell wrote:
>> > > I've been
On Tue, Jan 2, 2018 at 10:37 AM, Geert Uytterhoeven
wrote:
> Hi Linus,
>
> On Tue, Jan 2, 2018 at 10:27 AM, Linus Walleij
> wrote:
>> On Fri, Dec 29, 2017 at 2:31 PM, Ulf Hansson wrote:
>>> From: Geert Uytterhoeven
On Thu, Dec 28, 2017 at 08:09:55AM -0800, Stephen Boyd wrote:
> On 12/28, Joao Pinto wrote:
> > > if (pp->ops->get_msi_data)
> > > msg.data = pp->ops->get_msi_data(pp, pos);
> > >
> >
> > Thanks for the patch.
> > Gustavo' patch-set targeting the update of the Interrupt API for
> >
Missing patch description explaining why this change is desirable.
On Fri, Dec 29, 2017 at 9:18 AM, Christoph Hellwig wrote:
> --- a/lib/dma-direct.c
> +++ b/lib/dma-direct.c
> @@ -39,7 +39,7 @@ static void *dma_direct_alloc(struct device *dev, size_t
> size,
> if
On Fri, Dec 29, 2017 at 2:31 PM, Ulf Hansson wrote:
> From: Geert Uytterhoeven
>
> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable
> when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO block's
> module
We now have exports in both architecture code in in common code,
which causes a link failure when symbol versioning is eanbled, on
four architectures:
kernel/exit.o: In function `__crc_abort':
exit.c:(*ABS*+0xc0e2ec8b): multiple definition of `__crc_abort'
This removes the four architecture
The 'ret' variable is used to store the integer return value of
ocfs2_get_clusters(), as shown by this warning from modern
compilers:
fs/ocfs2/aops.c: In function 'ocfs2_range_has_holes':
fs/ocfs2/aops.c:2437:11: error: comparison of constant '0' with boolean
expression is always false
Hi Christoph,
On Fri, Dec 29, 2017 at 9:18 AM, Christoph Hellwig wrote:
> CONFIG_ALPHA_JENSEN has failed to compile since commit aca05038
> ("alpha/dma: use common noop dma ops"), so mark it as broken.
unknown revision or path not in the working tree.
Ah, you dropped the leading
On Fri, Dec 29, 2017 at 9:18 AM, Christoph Hellwig wrote:
> Life the code from x86 so that we behave consistently. In the future we
> should probably warn if any of these is set.
>
> Signed-off-by: Christoph Hellwig
For m68k:
Acked-by: Geert Uytterhoeven
On Fri, Dec 29, 2017 at 9:18 AM, Christoph Hellwig wrote:
> The current PCI_DMA_BUS_IS_PHYS decided if a dma implementation is bound
> by the dma mask in the device because it directly maps to a physical
> address range (modulo an offset in the device), or if it is virtualized
> by
The CLKRUN fix caused a few harmless compile-time warnings:
drivers/char/tpm/tpm_tis.c: In function 'tpm_tis_pnp_remove':
drivers/char/tpm/tpm_tis.c:274:23: error: unused variable 'priv'
[-Werror=unused-variable]
drivers/char/tpm/tpm_tis.c: In function 'tpm_tis_plat_remove':
Hi Rafael,
On Tue, Jan 2, 2018 at 11:32 AM, Rafael J. Wysocki wrote:
> On Fri, Dec 29, 2017 at 2:31 PM, Ulf Hansson wrote:
>> From: Geert Uytterhoeven
>>
>> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock
-fixes
tagged thusly:
afs-fixes-20180102
David
---
Dan Carpenter (1):
afs: Potential uninitialized variable in afs_extract_data()
David Howells (3):
fscache: Fix the default for fscache_maybe_release_page()
afs: Fix unlink
afs: Fix missing error handling
afs_write_end() is missing page unlock and put if afs_fill_page() fails.
Reported-by: Al Viro
Signed-off-by: David Howells
---
fs/afs/write.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/fs/afs/write.c
Repeating creation and deletion of a file on an afs mount will run the box
out of memory, e.g.:
dd if=/dev/zero of=/afs/scratch/m0 bs=$((1024*1024)) count=512
rm /afs/scratch/m0
The problem seems to be that it's not properly decrementing the nlink count
so that the inode can be
From: Dan Carpenter
Smatch warns that:
fs/afs/rxrpc.c:922 afs_extract_data()
error: uninitialized symbol 'remote_abort'.
Smatch is right that "remote_abort" might be uninitialized when we pass
it to afs_set_call_complete(). I don't know if that function uses
Below is the list of build error/warning regressions/improvements in
v4.15-rc6[1] compared to v4.14[2].
Summarized:
- build errors: +2/-6
- build warnings: +1292/-796
JFYI, when comparing v4.15-rc6[1] to v4.15-rc5[3], the summaries are:
- build errors: +1/-2
- build warnings: +707/-948
On Tue, Jan 2, 2018 at 11:44 AM, Geert Uytterhoeven
wrote:
> Hi Rafael,
>
> On Tue, Jan 2, 2018 at 11:32 AM, Rafael J. Wysocki wrote:
>> On Fri, Dec 29, 2017 at 2:31 PM, Ulf Hansson wrote:
>>> From: Geert Uytterhoeven
The previous patch addressed a warning but not the cause:
drivers/slimbus/qcom-ctrl.c: In function 'qcom_slim_probe':
drivers/slimbus/qcom-ctrl.c:584:9: error: passing argument 3 of
'dmam_alloc_coherent' from incompatible pointer type
[-Werror=incompatible-pointer-types]
There are two things
On Tue, Jan 2, 2018 at 11:47 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.15-rc6[1] to v4.15-rc5[3], the summaries are:
> - build errors: +1/-2
+ {standard input}: Error: unknown opcode: => 4554, 3363, 2025,
1819, 788, 2605, 2035, 6420, 4224, 1442, 3788,
Hi AceLan,
> Device 0cf3:e010 is one of the QCA ROME family.
>
> T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=03 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0cf3 ProdID=e010 Rev=00.01
> C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I: If#= 0 Alt= 0
Fix the default for fscache_maybe_release_page() for when the cookie isn't
valid or the page isn't cached. It mustn't return false as that indicates
the page cannot yet be freed.
The problem with the default is that if, say, there's no cache, but a
network filesystem's pages are using up
When the hci support is built-in, but mvmem is a loadable module, we
get a link failure:
drivers/bluetooth/hci_ll.o: In function `hci_ti_probe':
hci_ll.c:(.text+0x226): undefined reference to `nvmem_cell_get'
hci_ll.c:(.text+0x238): undefined reference to `nvmem_cell_read'
hci_ll.c:(.text+0x244):
On Tue, Jan 02, 2018 at 01:56:28AM +0100, Rafael J. Wysocki wrote:
> + if (atomic_read(>power.usage_count) <= 1 &&
> + atomic_read(>power.child_count) == 0)
> + pm_runtime_set_suspended(dev);
>
> - pm_runtime_set_suspended(dev);
The ->runtime_suspend callback *has*
On Thu, Dec 28, 2017 at 09:39:12AM +0800, Honghui Zhang wrote:
> On Wed, 2017-12-27 at 12:45 -0600, Bjorn Helgaas wrote:
> > On Wed, Dec 27, 2017 at 08:59:54AM +0800, honghui.zh...@mediatek.com wrote:
> > > From: Honghui Zhang
> > >
> > > The hardware default value of
On Tue, Jan 02, 2018 at 12:16:18PM +0200, Tomi Valkeinen wrote:
> Hi,
>
> On 02/01/18 10:54, Aishwarya Pant wrote:
> > Hi
> >
> > In Documentation/arm/OMAP/DSS, there is a description of the DSS and FB
> > sysfs
> > interfaces which could be moved to Documentation/ABI.
> >
> > Would such a
All other architectures use 'unsigned int' as the data in readl/write,
but m32r uses 'unsigned long', leading to lots of harmless build warnings
like:
drivers/mmc/host/dw_mmc.c: In function 'dw_mci_regs_show':
drivers/mmc/host/dw_mmc.c:168:31: warning: format '%x' expects argument of type
Many uses of strncpy() on sh causes a warning like
arch/sh/include/asm/string_32.h:50:42: warning: array subscript is above array
bounds [-Warray-bounds]
This avoids the warning by turning the pointer arithmetic into an
integer operation that does not get checked the same way.
Signed-off-by:
Many uses of strncpy() on xtensa causes a warning like
arch/xtensa/include/asm/string.h:56:42: warning: array subscript is above array
bounds [-Warray-bounds]
: "0" (__dest), "1" (__src), "r" (__src+__n)
This avoids the warning by turning the pointer arithmetic into an
integer operation
Hi Gang,
On 2017/12/28 18:07, Gang He wrote:
> Add ocfs2_overwrite_io function, which is used to judge if
> overwrite allocated blocks, otherwise, the write will bring extra
> block allocation overhead.
>
> Signed-off-by: Gang He
> ---
> fs/ocfs2/extent_map.c | 45
The missing 'volatile' keyword on the iounmap argument leads to lots of
harmless warnings in an allmodconfig build:
sound/pci/echoaudio/echoaudio.c:1879:10: warning: passing argument 1 of
'iounmap' discards 'volatile' qualifier f
pointer target type [-Wdiscarded-qualifiers]
Signed-off-by: Arnd
On Tue, Jan 2, 2018 at 11:51 AM, Lukas Wunner wrote:
> On Tue, Jan 02, 2018 at 01:56:28AM +0100, Rafael J. Wysocki wrote:
>> + if (atomic_read(>power.usage_count) <= 1 &&
>> + atomic_read(>power.child_count) == 0)
>> + pm_runtime_set_suspended(dev);
>>
>>
On 2018/1/2 14:49, Chao Yu wrote:
On 2017/12/30 15:42, Yunlong Song wrote:
In some case, the node blocks has wrong blkaddr whose segment type is
You mean *data block* has wrong blkaddr whose segment type is NODE?
Yes.
NODE, e.g., recover inode has missing xattr flag and the blkaddr is in
On 08/12/2017 09:42, Jason Yan wrote:
Now the libsas hotplug has some issues, Dan Williams report
a similar bug here before
https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html
Hi Martin, James,
At this point we feel that we have a decent solution to the
long-standing
On Tue, Jan 02, 2018 at 11:16:23AM +0100, Arnd Bergmann wrote:
> The newly added callback pointers cause a warning for some configurations:
>
> In file included from net/ipv6/af_inet6.c:45:0:
> include/linux/netfilter_ipv6.h:38:51: error: 'struct nf_queue_entry' declared
> inside parameter list
On uniprocessor systems, critical and non-critical tasks cannot be
isolated, as there is only a single CPU core. Hence enabling CPU
isolation by default on such systems does not make much sense.
Instead of changing the default for !SMP, fix this by making the feature
depend on SMP, with an
There are some global registers in Spreadtrum sc27xx PMICs, which will
be accessed by other drivers. So this patch adds one syscon cell to
help to access the PMIC's global registers.
Signed-off-by: Baolin Wang
---
drivers/mfd/sprd-sc27xx-spi.c |3 +++
1 file changed,
Hi Arnd,
On 2018/1/2 18:34, Arnd Bergmann wrote:
> Fixes: mmotm
> ("ocfs2-fall-back-to-buffer-io-when-append-dio-is-disabled-with-file-hole-existing-fix")
I think this patch is not fit for mainline and will not be apply to mainline in
the future.
Andrew can remove it from mm-tree.
Thanks,
Alex
On Tue, Jan 02, 2018 at 11:31:12AM +0100, Arnd Bergmann wrote:
> We now have exports in both architecture code in in common code,
> which causes a link failure when symbol versioning is eanbled, on
> four architectures:
>
> kernel/exit.o: In function `__crc_abort':
> exit.c:(*ABS*+0xc0e2ec8b):
Thanks Bartosz fo adding me in to the loop!!
On 28/12/17 21:42, Bartosz Golaszewski wrote:
2017-12-28 12:28 GMT+01:00 Johan Hovold :
On Wed, Dec 27, 2017 at 03:10:38PM +0100, Bartosz Golaszewski wrote:
This function can fail with -EBUSY, but we don't check its return
value
Hi Arnd,
> When the hci support is built-in, but mvmem is a loadable module, we
> get a link failure:
>
> drivers/bluetooth/hci_ll.o: In function `hci_ti_probe':
> hci_ll.c:(.text+0x226): undefined reference to `nvmem_cell_get'
> hci_ll.c:(.text+0x238): undefined reference to `nvmem_cell_read'
>
On Tue, Jan 02, 2018 at 11:18:31AM +0100, Rafael J. Wysocki wrote:
> On Tue, Jan 2, 2018 at 7:36 AM, Du, Changbin wrote:
> > Hi Wysocki and Brown,
> > May I know wether you have checked this? Thanks!
>
> There's a commit changing this queued up already, see
>
On Tue, Jan 2, 2018 at 12:02 PM, Rafael J. Wysocki wrote:
> On Tue, Jan 2, 2018 at 11:51 AM, Lukas Wunner wrote:
>> On Tue, Jan 02, 2018 at 01:56:28AM +0100, Rafael J. Wysocki wrote:
[cut]
>
>> One addition that would be really helpful:
On 12/08/2017 09:45 PM, Michal Hocko wrote:
> From: Michal Hocko
>
> do_pages_move is supposed to move user defined memory (an array of
> addresses) to the user defined numa nodes (an array of nodes one for
> each address). The user provided status array then contains resulting
This series adds support for the PMU in ARM DynamIQ Shared Unit (DSU).
The DSU integrates one or more cores with an L3 memory system, control
logic, and external interfaces to form a multicore cluster. The PMU
allows counting the various events related to L3, SCU etc, using 32bit
independent
Add support for the Cluster PMU part of the ARM DynamIQ Shared Unit (DSU).
The DSU integrates one or more cores with an L3 memory system, control
logic, and external interfaces to form a multicore cluster. The PMU
allows counting the various events related to L3, SCU etc, along with
providing a
This patch documents the devicetree bindings for ARM DSU PMU.
Cc: Mark Rutland
Cc: Will Deacon
Cc: devicet...@vger.kernel.org
Cc: frowand.l...@gmail.com
Acked-by: Rob Herring
Signed-off-by: Suzuki K Poulose
Use the new generic helper, of_cpu_node_to_id(), to map a
a phandle to the logical CPU number while parsing the
PMU irq affinity.
Cc: Will Deacon
Acked-by: Mark Rutland
Signed-off-by: Suzuki K Poulose
---
Make use of the new generic helper to convert an of_node of a CPU
to the logical CPU id in parsing the topology.
Cc: Catalin Marinas
Cc: Leo Yan
Cc: Will Deacon
Acked-by: Mark Rutland
Signed-off-by: Suzuki
Use the new generic helper of_cpu_node_to_id() instead
of using our own version to map a device node to logical CPU
number.
Acked-by: Marc Zyngier
Signed-off-by: Suzuki K Poulose
---
Changes since V3:
- Reflect the change in the helper name and
Reuse the new generic helper, of_cpu_node_to_id() to map a
given CPU phandle to a logical CPU number.
Acked-by: Mathieu Poirier
Tested-by: Leo Yan
Signed-off-by: Suzuki K Poulose
---
Changes since V4:
- Fix a regression
Export perf_event_update_userpage() so that PMU driver using them,
can be built as modules.
Acked-by: Peter Zilstra
Signed-off-by: Suzuki K Poulose
---
kernel/events/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/events/core.c
Add a helper to map a device node to a logical CPU number to avoid
duplication. Currently this is open coded in different places (e.g
gic-v3, coresight). The helper tries to map device node to a "possible"
logical CPU id, which may not be online yet. It is the responsibility
of the user to make
On Tue, Jan 2, 2018 at 3:00 AM, Arnd Bergmann wrote:
> Many uses of strncpy() on xtensa causes a warning like
>
> arch/xtensa/include/asm/string.h:56:42: warning: array subscript is above
> array bounds [-Warray-bounds]
>: "0" (__dest), "1" (__src), "r" (__src+__n)
>
> This
On Tue 02-01-18 10:21:03, Mel Gorman wrote:
> On Sat, Dec 23, 2017 at 10:36:53AM +0900, Minchan Kim wrote:
> > > code path. It appears that similar situation is possible for them too.
> > >
> > > The file cache pages will be delete from file cache address_space before
> > > address_space
On Tue, Jan 02, 2018 at 10:29:35AM +0800, Xiongfeng Wang wrote:
> Hi,
>
> On 2017/12/18 20:42, Morten Rasmussen wrote:
> > On Fri, Dec 15, 2017 at 10:36:35AM -0600, Jeremy Linton wrote:
> >> Hi,
> >>
> >> On 12/13/2017 12:02 PM, Lorenzo Pieralisi wrote:
> >>> [+Morten, Dietmar]
> >>>
> >>>
Currently the bits to be set in the watchhi register in addition to that
requested by the user is defined inline for each register. To avoid
this, define the bits once and or that in for each register.
Signed-off-by: Matt Redfearn
---
arch/mips/kernel/watch.c | 17
Currently the bits to be masked when watchhi is read is defined inline
for each register. To avoid this, define the bits once and mask each
register with that value.
Signed-off-by: Matt Redfearn
---
arch/mips/kernel/watch.c | 14 ++
1 file changed, 6
On Sunday, December 10, 2017 12:55:23 AM CET Rafael J. Wysocki wrote:
> Hi All,
>
> This series is a follow-up for
>
> https://marc.info/?l=linux-doc=151101644105835=2
>
> Patches[1-3/6] from the above have been reviewed and agreed on, so
> they are in linux-next now and here's a next version
Hi Arnd,
On Tue, Jan 02, 2018 at 11:31:12AM +0100, Arnd Bergmann wrote:
> We now have exports in both architecture code in in common code,
> which causes a link failure when symbol versioning is eanbled, on
> four architectures:
>
> kernel/exit.o: In function `__crc_abort':
>
On Tue, Jan 02, 2018 at 11:34:45AM +, Sudip Mukherjee wrote:
> Hi Arnd,
>
> On Tue, Jan 02, 2018 at 11:31:12AM +0100, Arnd Bergmann wrote:
> > We now have exports in both architecture code in in common code,
> > which causes a link failure when symbol versioning is eanbled, on
> > four
In case of error, the function ioremap() returns NULL pointer not
ERR_PTR(). The IS_ERR() test in the return value check should be
replaced with NULL test.
Fixes: 9b54470afd83 ("irqchip: add initial support for ompic")
Signed-off-by: Wei Yongjun
---
Thanks for the Patch,
On 01/01/18 23:22, Andrey Smirnov wrote:
Add code to allow avoid having nvmem core append a numeric suffix to
the end of the name by passing config->id of -1.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
501 - 600 of 1720 matches
Mail list logo