From: Kuninori Morimoto
This patch enables to use thermal-zone on DT if it was calles as
"renesas,rcar-thermal-gen2".
Previous style (= non thermal-zone) is still supported by
"renesas,rcar-thermal" to keep compatibility for "git bisect".
Signed-off-by: Kuninori Morimoto
---
v5 -> v6
- "was
Print the base address for each range in decimal alongside the size.
Use a "(size @ base)" format similar to the fake_memmap kernel parameter.
Print the range and base in the best-fit B, KiB, MiB, etc. units rather
than always MiB. This avoids rounding, which can be misleading.
Use proper IEC bi
On (12/01/15 21:36), Sergey Senozhatsky wrote:
> When we're using LZ4 multi compression streams for zram swap, we found out
> page allocation failure message in system running test. That was not only
> once, but a few(2 - 5 times per test). Also, some failure cases were
> continually occurring to
Add the NV memory attribute introduced in UEFI 2.5 and add a column
for it in the types and attributes string used when printing the UEFI
memory map.
old:
efi: mem61: [type=14| | | | | | | |WB|WT|WC|UC]
range=[0x00088000-0x000c7fff) (16384MB)
new:
efi: mem61:
Adjust efi_print_memmap to print the real end address of each
range, not 1 byte beyond. This matches other prints like those for
SRAT and nosave memory.
Change the closing ) to ] to match the opening [.
old:
efi: mem61: [Persistent Memory | | | | | | | |WB|WT|WC|UC]
range=[0x00
Date: Thu, 17 Dec 2015 17:40:55 -0600
Subject: [PATCH 0/4] x86/efi: support persistent memory in efi_print_memmap
This series adds support for persistent memory type and NV attribute
in the efi_print_memmap function, which is only used if EFI_DEBUG is true
(which is the case for x86).
Robert Ell
Add the "Persistent Memory" string for type 14 introduced in
UEFI 2.5. This is used when printing the UEFI memory map.
old:
efi: mem61: [type=14| | | | | | | |WB|WT|WC|UC]
range=[0x00088000-0x000c7fff) (16384MB)
new:
efi: mem61: [Persistent Memory | | |
Hi Bean,
On Tue, Dec 08, 2015 at 06:21:00AM +, Bean Huo 霍斌斌 wrote:
> > -Original Message-
> > From: Brian Norris [mailto:computersforpe...@gmail.com]
> >
> > I'll admit I'm a little fuzzy on the differences between dual and quad
> > modes on
> > various flash manufacturers. Can you h
Hi,
On 2015년 12월 15일 12:41, Krzysztof Kozlowski wrote:
> On 14.12.2015 15:38, Chanwoo Choi wrote:
>> This patch adds the generic exynos bus frequency driver for AMBA AXI bus
>> of sub-blocks in exynos SoC with DEVFREQ framework. The Samsung Exynos SoC
>> have the common architecture for bus betwee
The mm-of-the-moment snapshot 2015-12-17-16-35 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
Hi Heiko,
On 12/18/2015 07:51 AM, Heiko Stübner wrote:
Hi Yakir,
Am Mittwoch, 16. Dezember 2015, 11:20:18 schrieb Yakir Yang:
The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller
share the same IP, so a lot of parts can be re-used. I split the common
code into bridge direct
On Thu, Dec 17, 2015 at 04:29:01PM -0800, Brian Norris wrote:
> On Tue, Dec 08, 2015 at 06:21:00AM +, Bean Huo 霍斌斌 wrote:
> OK, so I think your patch is broken:
>
> > > commit 548cd3ab54da ("mtd: spi-nor: Add quad I/O support for Micron
> > > SPI NOR")
>
> How did you test this? Spec
On 2015년 12월 18일 09:34, Chanwoo Choi wrote:
> Hi,
>
> On 2015년 12월 15일 12:41, Krzysztof Kozlowski wrote:
>> On 14.12.2015 15:38, Chanwoo Choi wrote:
>>> This patch adds the generic exynos bus frequency driver for AMBA AXI bus
>>> of sub-blocks in exynos SoC with DEVFREQ framework. The Samsung Exyn
On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
> [Starting a new thread from https://lkml.org/lkml/2015/12/15/663, as
> now my laptop is displaying values in the sysfs *raw* files.]
>
> So I'm trying to understand exactly how the hid-sensor-accel-3d
> driver works.
>
> If I turn up deb
On 12/17/2015 8:06 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/17/2015 3:53 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/17/2015 2:51 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/17/2015 1:59 PM, Måns Rullgård wrote:
Julian Margetson writes:
I have
Hi Andy,
As per Nish these patches are impacting sensors on Yoga.
https://lkml.org/lkml/2015/11/30/441
Can you help?
Thanks,
Srinivas
On Thu, 2015-12-17 at 16:51 -0800, Srinivas Pandruvada wrote:
> On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
> > [Starting a new thread from https:/
On 2015년 12월 18일 06:20, Sergei Shtylyov wrote:
> Hello.
>
> On 12/17/2015 05:34 AM, Chanwoo Choi wrote:
>
>>> On 2015년 12월 17일 03:07, Sergei Shtylyov wrote:
Maxim Integrated MAX3355E chip integrates a charge pump and comparators to
enable a system with an integrated USB OTG dual-role tr
On Thu, Dec 17, 2015 at 4:51 PM, Srinivas Pandruvada
wrote:
> On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
>> [Starting a new thread from https://lkml.org/lkml/2015/12/15/663, as
>> now my laptop is displaying values in the sysfs *raw* files.]
>>
>> So I'm trying to understand exactly
On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote:
> With built-in netconsole and IXGBE, configuring netconsole via the kernel
> cmdline results in the following panic at boot:
>
> netpoll: netconsole: device eth0 not up yet, forcing it
> usb 2-1: new high-speed USB device number 2 usi
On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
wrote:
> Hi Andy,
>
> As per Nish these patches are impacting sensors on Yoga.
> https://lkml.org/lkml/2015/11/30/441
To be clear, without that series, the touchpad and touchscreen on the
Yoga 900 don't work at all. So they are necessary for f
On Thu, 17 Dec 2015 15:52:39 -0800
Calvin Owens wrote:
> With built-in netconsole and IXGBE, configuring netconsole via the kernel
> cmdline results in the following panic at boot:
>
> netpoll: netconsole: device eth0 not up yet, forcing it
> usb 2-1: new high-speed USB device number 2 u
On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
> On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
> wrote:
> > Hi Andy,
> >
> > As per Nish these patches are impacting sensors on Yoga.
> > https://lkml.org/lkml/2015/11/30/441
>
> To be clear, without that series, the touchpad and
On Thu, Nov 19, 2015 at 02:26:33PM +0200, Irina Tirdea wrote:
> This patchset depends on Dmitry's patch that fixes the
> GPIO ACPI API[1], so devm_gpiod_get_optional can be properly
> used in the code.
>
> [1] https://lkml.org/lkml/2015/11/11/465
Applied 1 through 5 (see my goodix branch), looki
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
changbin-du-intel-com/usb-gadget-forbid-queuing-request-to-a-disabled-ep/20151217-180958
commit 6ee844ac2efe94605f8b630053739fdae8fd617c ("usb: gadget: forbid queuing
request to a disabl
On Sat, Nov 21, 2015 at 02:30:19PM +0100, Karsten Merker wrote:
> Hello,
>
> this is v4 of my "Input: goodix - add axis swapping and axis inversion
> support" patchset.
>
> The goodix touchscreen driver has gained device-tree support in kernel
> 4.1, but doesn't currently support the touchscreen-
Hi Sergei,
Except for just one comment below, Looks good to me.
Acked-by: Chanwoo Choi
I'll wait for a few days to get the review from DT maintainer
before applying it on extcon-next branch.
On 2015년 12월 18일 07:47, Sergei Shtylyov wrote:
> Maxim Integrated MAX3355E chip integrates a charge pump
Commit 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq")
replaced spin_lock_irqsave() calls with
rcu_read_lock() calls in sysrq. Since rcu_read_lock() does not
disable preemption, faulthandler_disabled() in
__do_page_fault() in x86/fault.c returns false. When the code
later calls might_sleep() in th
On Thu, 2015-12-17 at 17:07 -0800, Nish Aravamudan wrote:
> On Thu, Dec 17, 2015 at 4:51 PM, Srinivas Pandruvada
> wrote:
> > On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
> > > [Starting a new thread from https://lkml.org/lkml/2015/12/15/663,
> > > as
> > > now my laptop is displaying
On Thu, Dec 17, 2015 at 9:28 AM, Greg KH wrote:
> On Wed, Dec 16, 2015 at 11:25:21AM -0500, Rik van Riel wrote:
>> On 12/15/2015 07:52 PM, Ani Sinha wrote:
>> > Rik, should I send a separate email with the patch or you are OK
>> > with what I sent in the email? Are you queueing up my patch for
>>
On 2015년 12월 14일 18:04, MyungJoo Ham wrote:
>>
>> This patch adds the new passive governor for DEVFREQ framework. The
>> following
>> governors are already present and used for DVFS (Dynamic Voltage and
>> Frequency
>> Scaling) drivers. The following governors are independently used for one
Heiko,
在 2015年12月18日 07:28, Heiko Stübner 写道:
Am Donnerstag, 17. Dezember 2015, 22:21:47 schrieb Caesar Wang:
The pinctrl gpio pull up/down is incorrect since the rk3036 SoCs
can't set the status in the internal.
We should keep the default status for enable the gpio status,
In fact, the pull_n
Similar to the questions about the arm64 efi boot stub
handing persistent memory, some of the arm64 kernel code
looks fishy.
In arch/arm64/kernel/efi.c:
static int __init is_normal_ram(efi_memory_desc_t *md)
{
if (md->attribute & EFI_MEMORY_WB)
return 1;
return 0;
This fixes CVE-2015-7550.
There's a race between keyctl_read() and keyctl_revoke(). If the revoke
happens between keyctl_read() checking the validity of a key and the key's
semaphore being taken, then the key type read method will see a revoked key.
This causes a problem for the user-defined key
The vfio_iommu_spapr_tce_create struct has 4x32bit and 2x64bit fields
which should have resulted in sizeof(fio_iommu_spapr_tce_create) equal
to 32 bytes. However due to the gcc's default alignment, the actual
size of this struct is 40 bytes.
This fills gaps with __resv1/2 fields.
This should not
Julian Margetson writes:
> On 12/17/2015 8:06 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>
>>> On 12/17/2015 3:53 PM, Måns Rullgård wrote:
Julian Margetson writes:
> On 12/17/2015 2:51 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>
>>> On 12/17/201
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Herbert-Xu/rhashtable-Fix-walker-list-corruption/20151216-164833
commit f9f51b8070be3e829100614a7372b219723b864f ("rhashtable: Fix walker list
corruption")
[8.933376] ===
[8.933376] ==
On Thursday 12/17 at 17:10 -0800, Stephen Hemminger wrote:
> On Thu, 17 Dec 2015 15:52:39 -0800
> Calvin Owens wrote:
>
> > With built-in netconsole and IXGBE, configuring netconsole via the kernel
> > cmdline results in the following panic at boot:
> >
> > netpoll: netconsole: device eth0 n
On Thursday 12/17 at 17:08 -0800, Eric Dumazet wrote:
> On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote:
> > With built-in netconsole and IXGBE, configuring netconsole via the kernel
> > cmdline results in the following panic at boot:
> >
> > netpoll: netconsole: device eth0 not up yet,
On 2015/12/18 7:11, Alexei Starovoitov wrote:
On Thu, Dec 17, 2015 at 05:23:12AM +, Wang Nan wrote:
We are going to uses libbpf to replace old libbpf.[ch] and
bpf_load.[ch]. This is the first patch of this work. In this patch,
several macros and helpers in libbpf.[ch] and bpf_load.[ch] are
Hi all-
I think that, for PKRU in particular, we want the default signal
handling behavior to be a bit unusual.
When a signal is delivered, I think we should save the entire xstate
including PKRU. I see no reason to do anything other than that.
When a signal returns (sigreturn is called), thoug
On 17-12-15, 19:04, Bartlomiej Zolnierkiewicz wrote:
> Commit 01fb4d3c39d3 ("PM / OPP: Parse 'opp--'
> bindings") broke support for parsing standard opp-microvolt and
> opp-microamp properties. Fix it by setting 'name' string to
> proper value for !prop cases.
>
> Cc: Viresh Kumar
> Cc: Lee Jone
Hi Cyrille,
On Mon, Dec 07, 2015 at 03:09:10PM +0100, Cyrille Pitchen wrote:
> The quad (or dual) mode of a spi-nor memory may be enabled at boot time by
> non-volatile bits in some setting register. Also such a mode may have
> already been enabled at early stage by some boot loader.
>
> Hence, w
Thanks for testing.
On Thu, Dec 17, 2015 at 03:31:30PM -0800, Stephane Eranian wrote:
> I would not add a --topdown option but instead a --metric option with
> arguments
> such that other metrics could be added later:
>
>$ perf stat --metrics topdown -I 1000 -a sleep 100
>
> If you do this
Hi Mark:
在 2015/12/17 21:52, Mark Rutland 写道:
> On Thu, Dec 17, 2015 at 07:56:34PM +0800, MaJun wrote:
>> From: Ma Jun
[...]
>> +- compatible: Should be "hisilicon,mbigen-v2"
>> +
>> +- reg: Specifies the base physical address and size of the Mbigen
>> + registers.
>> +
>> +- interrupt controlle
On 17-12-15, 23:30, Mans Rullgard wrote:
> If the "dma-channels" DT property is missing, the dw_dma_parse_dt()
> function return NULL, but not before allocating memory for a struct
> dw_dma_platform_data through devres. If the device supports parameter
> detection, the probe still succeeds and the
On Thu, Dec 17, 2015 at 5:16 PM, Srinivas Pandruvada
wrote:
> On Thu, 2015-12-17 at 17:07 -0800, Nish Aravamudan wrote:
>> On Thu, Dec 17, 2015 at 4:51 PM, Srinivas Pandruvada
>> wrote:
>> > On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
>> > > [Starting a new thread from https://lkml.
Hi Dave,
[auto build test ERROR on v4.4-rc5]
[also build test ERROR on next-20151217]
[cannot apply to tip/x86/core]
url:
https://github.com/0day-ci/linux/commits/Dave-Hansen/x86-pass-in-size-to-early-cmdline-parsing/20151218-060427
config: i386-allyesconfig (attached as .config)
reproduce
On 11/24/2015 07:43 AM, Alex Williamson wrote:
Please see the commit log and comments in patch 1 for a general
explanation of the problems that this series tries to address. The
general problem is that we have several cases where we want to expose
variable sized information to the user, whether
(Hit send too early; a few more comments)
On Mon, Dec 07, 2015 at 03:09:10PM +0100, Cyrille Pitchen wrote:
> drivers/mtd/spi-nor/spi-nor.c | 52
> +++
> include/linux/mtd/spi-nor.h | 23 +--
> 2 files changed, 69 insertions(+), 6 deletion
On 2015/12/18 3:43, Luck, Tony wrote:
As Tony requested, we may need a knob to stop a fallback in "movable->normal",
later.
If the mirrored memory is small and the other is large,
I think we can both enable "non-mirrored -> normal" and "normal ->
non-mirrored".
Size of mirrored memory can
On 12/17/2015 05:48 PM, Andy Lutomirski wrote:
> I think that, for PKRU in particular, we want the default signal
> handling behavior to be a bit unusual.
>
> When a signal is delivered, I think we should save the entire xstate
> including PKRU. I see no reason to do anything other than that.
Ye
On Mon, Dec 07, 2015 at 03:09:11PM +0100, Cyrille Pitchen wrote:
> This patch reworks the support of Quad and Dual SPI protocols for Micron,
> Spansion and Macronix Quad/Dual capable memories. Indeed, in the best
> case, only Spansion memories are correctly supported by the current
> spi-nor framew
On 2015/12/18 6:19, Johannes Weiner wrote:
The config options for the different cgroup controllers use various
terms: resource controller, cgroup subsystem, etc. Simplify this to
"controller", which is clear enough in the cgroup context.
Signed-off-by: Johannes Weiner
---
init/Kconfig | 65 ++
On Fri, Dec 18, 2015 at 12:07:08AM +0800, Xin Long wrote:
>
> I'm just wondering, why do not we handle the genuine double rehash
> issue inside rhashtable? i mean it's just a temporary error that a
> simple retry may fix it.
Because a double rehash means that someone has cracked your hash
function
On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
wrote:
> On 12/17/2015 05:48 PM, Andy Lutomirski wrote:
>> I think that, for PKRU in particular, we want the default signal
>> handling behavior to be a bit unusual.
>>
>> When a signal is delivered, I think we should save the entire xstate
>> including
On Thu, Dec 17, 2015 at 5:11 PM, Pandruvada, Srinivas
wrote:
> On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
>> On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
>> wrote:
>> > Hi Andy,
>> >
>> > As per Nish these patches are impacting sensors on Yoga.
>> > https://lkml.org/lkml/2
On 2015/12/18 6:19, Johannes Weiner wrote:
To make it easier to quickly find what's needed list the basic
resource controllers of cgroup2 first - io, memory, cpu - while
pushing the more exotic and/or legacy controllers to the bottom.
Signed-off-by: Johannes Weiner
Acked-by: Zefan Li
---
Are you in need of private or business loans for various purposes? if yes,apply
now
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
move write data register before excute command to avoid
missing first byte write to nor flash
Change-Id: Ie9d7ae30f9de1f3e976d2e1de5d8ee28837598c8
Signed-off-by: Bayi Cheng
---
drivers/mtd/spi-nor/mtk-quadspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-n
On Fri, 2015-12-18 at 13:05 +1100, Alexey Kardashevskiy wrote:
> On 11/24/2015 07:43 AM, Alex Williamson wrote:
> > Please see the commit log and comments in patch 1 for a general
> > explanation of the problems that this series tries to address. The
> > general problem is that we have several cas
1ddaa021b000220b5f2ad023e4f15ed44990974b:
MAINTAINERS: brcmnand: Add co-maintainer for Broadcom SoCs (2015-11-18
13:16:58 -0800)
are available in the git repository at:
git://git.infradead.org/linux-mtd.git tags/for-linus-20151217
for you to fetch changes up to e488ca9f8d4f62c2dc36bfa5c32f68e7f05ab381:
doc: dt: mtd
On Thu, 17 Dec 2015, Paul Gortmaker wrote:
The Kconfig currently controlling compilation of this code is:
config HUGETLBFS
bool "HugeTLB file system support"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned
On Thu, 2015-12-17 at 16:43 +0100, Jirka Hladky wrote:
> Hi Peter,
>
> I'm not sure how to do the bisecting and avoid landing at:
>
> [2a595721a1fa6b684c1c818f379bef834ac3d65e] sched/numa: Convert
> sched_numa_balancing to a static_branch
>
> I have redone the bisecting but I have landed again a
On Thu, 2015-12-17 at 18:33 -0800, Nish Aravamudan wrote:
> On Thu, Dec 17, 2015 at 5:11 PM, Pandruvada, Srinivas
> wrote:
> > On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
> > > On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
> > > wrote:
> > > > Hi Andy,
> > > >
> > > > As pe
On 2015/12/17 21:30, Vladimir Davydov wrote:
> The rationale of separate swap counter is given by Johannes Weiner.
>
> Signed-off-by: Vladimir Davydov
> ---
> Changes in v2:
> - Add rationale of separate swap counter provided by Johannes.
>
> Documentation/cgroup.txt | 33 +++
On 12/17/2015 06:32 PM, Andy Lutomirski wrote:
> On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
> wrote:
>> But what about the register state when delivering a signal? Don't we
>> set the registers to the init state? Do we need to preserve PKRU state
>> instead of init'ing it? The init state _is
Move write data register before excute command to avoid
missing first byte write to nor flash
Signed-off-by: Bayi Cheng
---
the previous patch didn't drop the Change-Id
---
drivers/mtd/spi-nor/mtk-quadspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-nor/
On Thu, Dec 17, 2015 at 6:50 PM, Pandruvada, Srinivas
wrote:
> On Thu, 2015-12-17 at 18:33 -0800, Nish Aravamudan wrote:
>> On Thu, Dec 17, 2015 at 5:11 PM, Pandruvada, Srinivas
>> wrote:
>> > On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
>> > > On Thu, Dec 17, 2015 at 5:00 PM, Pandru
From: "james.chen"
Something wrong in suspend/resume of kernel v3.14 for the function of
wake-on-touch. The function of device_may_wakeup will return true if
the device supports wake-on-touch (for example, kitty and buddy).
So, modify the code from "if (device_may_wakeup(dev))" to
"if (!device_ma
On 2015/12/17 21:46, Daniel Wagner wrote:
On 12/17/2015 11:09 AM, Wangnan (F) wrote:
On 2015/12/17 16:29, Daniel Wagner wrote:
On 12/17/2015 08:03 AM, Daniel Wagner wrote:
Patch number 2 didn't apply cleanly.
Because I have another patch in my local tree which also modifis bpf
Makefile:
htt
In this series I am splitting up SoC specific PMU configuration data into
mach-exynos folder itself, before moving all of them under
drivers/soc/samsung/. Also instead of making all changes in single patch it
has been broken into SoC specific patches to avoid large size of patch.
With this approach
Moving Exynos PMU specific header file into "include/linux/soc/samsung"
thus updated affected files under "mach-exynos" to use new location of
these header files.
Signed-off-by: Amit Daniel Kachhap
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
[for testing on Trats2 (Exynos4412)
This patch splits up mach-exynos/pmu.c file, and moves exynos4210,
exynos4412 and exynos4212 PMU configuration data and functions handing
data into a common exynos4 SoC specific PMU file mach-exynos/exynos4-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
[for testing on Trats
This patch moves Exynos PMU driver implementation from "arm/mach-exynos"
to "drivers/soc/samsung". This driver is mainly used for setting misc
bits of register from PMU IP of Exynos SoC which will be required to
configure before Suspend/Resume. Currently all these settings are done
in "arch/arm/mac
This patch splits up mach-exynos/pmu.c file, and moves exynos5420,
PMU configuration data and functions handing data into exynos5420
SoC specific PMU file mach-exynos/exynos5420-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
[for testing on Peach-Pi (Exynos5880)]
Tested-by:
This patch splits up mach-exynos/pmu.c file, and moves exynos5250,
PMU configuration data and functions handing data into exynos5250
SoC specific PMU file mach-exynos/exynos5250-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/mach-exynos/Makefile | 4 +
This patch splits up mach-exynos/pmu.c file, and moves exynos3250 PMU
configuration data and functions handing those data into exynos3250
SoC specific PMU file mach-exynos/exynos3250-pmu.c.
Signed-off-by: Pankaj Dubey
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/mach-exynos/Makefile |
Hi Krzysztof,
On Thursday 17 December 2015 10:44 AM, Krzysztof Kozlowski wrote:
> On 12.12.2015 16:43, Pankaj Dubey wrote:
>> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>>
>> Series v5 got merged in kgene/for-next but due to last moment change before
>> pull
>> these pat
all,
I just started getting these "No irq handler for vector" messages
after upgrading to linux-next 20151217+.
(from the first boot)
...
[2.282652] [drm] Initialized drm 1.1.0 20060810
[2.318806] AVX version of gcm_enc/dec engaged.
[2.318810] AES CTR mode by8 optimizati
Hi Krzysztof,
On Thursday 17 December 2015 11:01 AM, Krzysztof Kozlowski wrote:
> On 17.11.2015 15:05, Pankaj Dubey wrote:
>> In this series I am splitting up SoC specific PMU configuration data into
>> mach-exynos folder itself, before moving all of them under
>> drivers/soc/samsung/. Also instea
iproc_gpio *'
static void iproc_gpio_unregister_pinconf(struct cygnus_gpio *chip)
^
Caused by commit
616043d58a89 ("pinctrl: Rename gpio driver from cygnus to iproc")
I have used the pinctrl tree from next-20151217 for today.
--
Cheers,
Stephen Rothwell
On Fri, 18 Dec 2015 03:46:41 +0900,
Russell King - ARM Linux wrote:
>
> On Thu, Dec 17, 2015 at 07:51:14AM -0800, Dan Williams wrote:
> > The commit below causes the libnvdimm sub-system to stop loading.
> > This is due to the fact that nvdimm_bus_match() returns the result of
> > test_bit() which
Move pinctrl initialization earlier in boot so that real devices can find
their pctldev without probe deferring.
Signed-off-by: Daniel Kurtz
---
drivers/pinctrl/mediatek/pinctrl-mt6397.c | 2 +-
drivers/pinctrl/mediatek/pinctrl-mt8127.c | 2 +-
drivers/pinctrl/mediatek/pinctrl-mt8135.c | 2 +-
d
On 12/17/15 15:46, Luis R. Rodriguez wrote:
>
> I explain why I do that there but the gist of it is that on Linux we may also
> want stronger semantics for specific linker table solutions, and solutions
> such
> as those devised on the IOMMU init stuff do memmove() for sorting depending on
> sema
On 18.12.2015 12:32, Pankaj Dubey wrote:
> In this series I am splitting up SoC specific PMU configuration data into
> mach-exynos folder itself, before moving all of them under
> drivers/soc/samsung/. Also instead of making all changes in single patch it
> has been broken into SoC specific patches
On 12/18/2015 01:38 PM, Alex Williamson wrote:
On Fri, 2015-12-18 at 13:05 +1100, Alexey Kardashevskiy wrote:
On 11/24/2015 07:43 AM, Alex Williamson wrote:
Please see the commit log and comments in patch 1 for a general
explanation of the problems that this series tries to address. The
genera
On 12/17/15 20:25, H. Peter Anvin wrote:
>
> /* DECLARE_LINKTABLE_RO */
> extern const struct foo tablename[], tablename__end[];
>
> /* DEFINE_LINKTABLE_RO */
> DECLARE_LINKTABLE_RO(struct foo, tablename);
>
> const struct
> foo__attribute__((used,section(".rodata.tbl.tablename.0"))) tablename[0
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/arm/mm/dma-mapping.c
drivers/iommu/intel-iommu.c
drivers/staging/android/ion/ion_chunk_heap.c
between commit:
3e6110fd5480 ("Revert "scatterlist: use sg_phys()"")
from Linus' tree and commit:
0504b8
Still something with af_unix and/or wake code on rc5 :
[34971.300210] Unable to handle kernel paging request at virtual address
56ac56ac
[34971.307455] pgd = a8c3
[34971.310164] [56ac56ac] *pgd=
[34971.313761] Internal error: Oops: 8005 [#1] PREEMPT SMP ARM
[34971.319683] Modu
On Thu, Dec 17, 2015 at 09:48:44AM -0800, Tony Lindgren wrote:
> * Peter Ujfalusi [151217 05:33]:
> > Hi,
> >
> > Changes since v1:
> > - Updated to use the non 16bit arrays [1]
> > - send the two patch as a series
> >
> > [1]
> > As it has been discussed earlier:
> > https://www.mail-archive.co
On Thu, Dec 17, 2015 at 11:30:57PM +, Mans Rullgard wrote:
> If the "dma-channels" DT property is missing, the dw_dma_parse_dt()
> function return NULL, but not before allocating memory for a struct
> dw_dma_platform_data through devres. If the device supports parameter
> detection, the probe
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/x86/kvm/mmu.c
between commits:
7ee0e5b29d27 ("KVM: x86: MMU: Remove unused parameter of __direct_map()")
029499b47738 ("KVM: x86: MMU: Make mmu_set_spte() return emulate value")
from the kvm tree and com
On Dec 17, 2015 6:53 PM, "Dave Hansen" wrote:
>
> On 12/17/2015 06:32 PM, Andy Lutomirski wrote:
> > On Thu, Dec 17, 2015 at 6:13 PM, Dave Hansen
> > wrote:
> >> But what about the register state when delivering a signal? Don't we
> >> set the registers to the init state? Do we need to preserv
On Wed, Dec 16, 2015 at 03:19:05PM +0200, Peter Ujfalusi wrote:
> Due to changes in device and platform code drivers w/o probe will fail to
> load. This means that the devices for eDMA TPTCs are goign to be without
> driver and omap hwmod code will turn them off after the kernel finished
> loading:
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/powerpc/include/asm/pgtable.h
between commit:
ee4889c7bc2a ("powerpc/mm: Don't have generic headers introduce functions
touching pte bits")
from the powerpc tree and commit:
e0e8474c0d55 ("mm, dax, gpu
On Fri, Dec 18, 2015 at 09:39:22AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux
> Herbert-Xu/rhashtable-Fix-walker-list-corruption/20151216-164833
> commit f9f51b8070be3e829100614a7372b219723b864f ("rhashtable: Fix walker list
> corr
static void iproc_gpio_unregister_pinconf(struct cygnus_gpio *chip)
> ^
>
> Caused by commit
>
> 616043d58a89 ("pinctrl: Rename gpio driver from cygnus to iproc")
>
> I have used the pinctrl tree from next-20151217 for today.
>
> --
> Cheers
On Thu, Dec 10, 2015 at 03:07:23PM +, Damien Horsley wrote:
> From: "Damien.Horsley"
>
> Use of the CANCEL bit in mdc_terminate_all creates an
> additional 'command done' to appear in the registers (in
> addition to an interrupt).
>
> In addition, there is a potential race between
> mdc_term
On Mon, Dec 14, 2015 at 10:47:37PM +0200, Peter Ujfalusi wrote:
> Hi,
>
> As it has been discussed in the following thread:
> http://www.gossamer-threads.com/lists/linux/kernel/2181487#2181487
>
> With this series I have taken a path which would result two new API, which can
> be used to convert
Existing test-all.c doesn't check BPF related features. For environment
with all other features enabled, BPF would be considered enabled
without doing real feature check.
This patch adds test-bpf.c into test-all.c.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: Namhyung Kim
Cc: Jiri
701 - 800 of 834 matches
Mail list logo
