On Thu 16-07-15 00:30:27, Dave Hansen wrote:
> On 07/16/2015 12:26 AM, Jan Kara wrote:
> > So Dave's patches would go in only in the next merge window anyway so we
> > still have like two-three weeks to decide which patchset to take. If you
> > think it will take you longer, then merging Dave's
On 16/07/15 09:54, Dan Carpenter wrote:
On Thu, Jul 16, 2015 at 08:45:06AM +, Maninder Singh wrote:
where we are checking for (pTDInfo->skb), we are using it in above line.
and it does not look good, thats why we should remove thse checks and i have
suggested
changes.
code snippet:-
Good day and compliment. My name is John Jones the personal lawyers to Gaddafi
son. I was directed to contact you by my boss. I'm sure you know the late Libya
head of state Muammar Muhammad Abu Minyar al-Gaddafi who was killed by the
American government. I'm not in the right disposition to
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Thursday, July 16, 2015 6:38 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 3/3] f2fs:
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Thursday, July 16, 2015 6:38 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 2/3] f2fs: handle error
This patch deinlines jhash, jhash2 and __jhash_nwords.
It also removes rhashtable_jhash2(key, length, seed)
because it was merely calling jhash2(key, length, seed).
With this .config: http://busybox.net/~vda/kernel_config,
after deinlining these functions have sizes and callsite counts
as
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Thursday, July 16, 2015 6:38 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 1/3] f2fs: callers take
On Wed, Jul 15, 2015 at 01:47:15PM -0700, Andres Lagar-Cavilla wrote:
> I think the remaining question here is performance.
>
> Have you conducted any studies where
> - there is a workload
> - a daemon is poking kpageidle every N seconds/minutes
> - what is the daemon cpu consumption?
> - what is
Hi Peter,
On 2015/07/15 4:29, Peter Hurley wrote:
> On 07/13/2015 09:16 PM, Taichi Kageyama wrote:
>> On 2015/07/11 9:12, Peter Hurley wrote:
>>> On 07/09/2015 01:32 AM, Taichi Kageyama wrote:
On 2015/07/08 23:00, Prarit Bhargava wrote:
> On 07/08/2015 09:51 AM, Peter Hurley wrote:
On Thu, 2015-11-06 at 11:27:51 UTC, Rasmus Villemoes wrote:
> C99 says that a precision given as simply '.' with no following digits
> or * should be interpreted as 0. The kernel's printf implementation,
> however, treats this case as if the precision was omitted. C99 also
> says that if both the
On Tue, Jul 14, 2015 at 10:04:03PM +0200, Mateusz Kulikowski wrote:
> This series does some more cleanup for driver.
>
> Changes in V2:
> - Added patch 6/23 (Remove rtllib_stats structure as suggested by Dan)
> - Updated patch 22/23 (remove whitespace - hint by Sudip)
> - Rebased into current
From: Jan Kara
The functionality of ext3 is fully supported by ext4 driver. Major
distributions (SUSE, RedHat) already use ext4 driver to handle ext3
filesystems for quite some time. There is some ugliness in mm resulting
from jbd cleaning buffers in a dirty page without cleaning page dirty
bit
From: Jan Kara
JBD layer wrote back data buffers without setting PageWriteback bit.
Thus standard mechanism for guaranteeing stable pages under IO did not
work. Since JBD is gone now and there is no other user of the
functionality, just remove it.
Acked-by: Jens Axboe
Signed-off-by: Jan Kara
Documentation of journalling layer in
Documentation/DocBook/filesystems.tmpl speaks about JBD layer. Since
that is going away, update the documentation to speak about JBD2. Also
update the parts that have changed since someone last touched the
document and remove some parts which are just
On Thu, 2015-09-07 at 07:39:42 UTC, Johannes Thumshirn wrote:
> Destroy afu->contexts_idr on release of an afu, reclaiming the allocated
> memory.
>
> Signed-off-by: Johannes Thumshirn
> Acked-by: Ian Munsie
Applied to powerpc next, thanks.
On 15/07/15 21:39, Russell King - ARM Linux wrote:
Back in September, I stumbled across a single CPU IRQs-off lockup of an
ARM SMP system, and decided to hack something together based on a much
older hacky implementation used with StrongARM CPUs from early 2000s.
This resulted in a copy of the
On Wed, 2015-08-07 at 15:14:36 UTC, Johannes Thumshirn wrote:
> Destroy cxl_adapter_idr on module exit, reclaiming the allocated memory.
>
> Signed-off-by: Johannes Thumshirn
> Acked-by: Ian Munsie
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b2a02ac65e40fb3900d1
cheers
On Wed, Jul 15, 2015 at 12:42:28PM -0700, Andres Lagar-Cavilla wrote:
> On Wed, Jul 15, 2015 at 6:54 AM, Vladimir Davydov
> wrote:
[...]
> > +static void kpageidle_clear_pte_refs(struct page *page)
> > +{
> > + struct rmap_walk_control rwc = {
> > + .rmap_one =
Hello,
here is the second iteration of my patches to remove ext3 filesystem driver.
Changes since the first version are:
* Regenerated the patch removing ext3 (using git format-patch -D) so that it's
not so huge
* Added Kconfig option handling so that old configs with EXT3_FS set but not
Now that ext4 driver must be used to access ext3 filesystems, improve
the Kconfig help text to better explain that using ext4 driver to access
the filesystem is fully compatible with the old ext3 driver.
Signed-off-by: Jan Kara
---
fs/ext4/Kconfig | 13 +++--
1 file changed, 7
2015-07-16 17:14 GMT+09:00 Duan Andy :
> From: Krzysztof Kozlowski Sent: Thursday, July 16,
> 2015 2:56 PM
>> To: Duan Fugang-B38611
>> Cc: Kamal Mostafa; linux-kernel@vger.kernel.org; sta...@vger.kernel.org;
>> kernel-t...@lists.ubuntu.com; daniel.lezc...@linaro.org; Damian Eppel;
>>
On 16/07/15 10:37, Russell King - ARM Linux wrote:
On Thu, Jul 16, 2015 at 10:11:24AM +0100, Daniel Thompson wrote:
On 15/07/15 21:39, Russell King wrote:
+void nmi_trigger_all_cpu_backtrace(bool include_self,
+ void (*raise)(cpumask_t *mask))
+{
+ struct
On Wed 15-07-15 09:58:22, Andrew Morton wrote:
> On Wed, 15 Jul 2015 12:26:26 +0200 Jan Kara wrote:
>
> > From: Jan Kara
> >
> > The functionality of ext3 is fully supported by ext4 driver. Major
> > distributions (SUSE, RedHat) already use ext4 driver to handle ext3
> > filesystems for quite
On Wed 15-07-15 10:18:36, Ted Tso wrote:
> On Wed, Jul 15, 2015 at 12:26:24PM +0200, Jan Kara wrote:
> >
> > so I have created this patch set which removes ext3 driver (and some
> > related support
> > code) from the kernel. See changelog of patch 2/3 for more details. If
> > noone objects,
>
On Wed, Jul 15, 2015 at 4:38 PM, Sudeep Holla wrote:
> Now that the GIC chip implementation enables IRQCHIP_SKIP_SET_WAKE and
> IRQCHIP_MASK_ON_SUSPEND by default, the platforms requiring them need
> not override the irqchip flags as before.
>
> This patch removes all the users of
On Thu, Jul 16, 2015 at 10:13:26AM +0100, Daniel Thompson wrote:
> On 15/07/15 21:39, Russell King wrote:
> >As we now have generic infrastructure to support backtracing of other
> >CPUs in the system on lockups, we can start to implement this for ARM.
> >Initially, we add an IPI based
On Thu, Jul 16, 2015 at 10:11:24AM +0100, Daniel Thompson wrote:
> On 15/07/15 21:39, Russell King wrote:
> >+void nmi_trigger_all_cpu_backtrace(bool include_self,
> >+ void (*raise)(cpumask_t *mask))
> >+{
> >+struct nmi_seq_buf *s;
> >+int i, cpu, this_cpu =
On Thu, 16 Jul 2015 06:31:16 +
Wang Long wrote:
> This patch update the Documentation/filesystems/debugfs.txt
> file. The main work is to add the description of the following
> functions:
> debugfs_create_atomic_t
> debugfs_create_u32_array
> debugfs_create_devm_seqfile
>
On 16/07/15 10:22, majun (F) wrote:
>
>
> 在 2015/7/16 16:52, Marc Zyngier 写道:
>> On 16/07/15 09:35, majun (F) wrote:
>
I'm a bit puzzled.
>>>
>>> For interrupts connect to mbigen , the interrupt trigger type, device id and
>>> event id value are encoded in mbigen chip already.
>>>
>>>
On Wed, Jul 15, 2015 at 12:03:18PM -0700, Andres Lagar-Cavilla wrote:
> For both /proc/kpage* interfaces you add (and more critically for the
> rmap-causing one, kpageidle):
>
> It's a good idea to do cond_sched(). Whether after each pfn, each Nth
> pfn, each put_user, I leave to you, but a
在 2015/7/16 16:52, Marc Zyngier 写道:
> On 16/07/15 09:35, majun (F) wrote:
>>> I'm a bit puzzled.
>>
>> For interrupts connect to mbigen , the interrupt trigger type, device id and
>> event id value are encoded in mbigen chip already.
>>
>> There are two types of mbigen node within a mbigen
On Wed, Jul 8, 2015 at 12:12 PM, Geert Uytterhoeven
wrote:
> On Fri, Apr 26, 2013 at 11:06 AM, Linus Walleij
> wrote:
>> The documentation already says these are physical addresses, and
>> we have concluded that any translation into the DMA address space
>> needs to reside in the dmaengine
From: Joerg Roedel
Currently the code to bring up secondary CPUs only checks
for cpu_online before it proceeds with launching the per-cpu
threads for the freshly booted remote CPU.
But the code to move these threads to the new CPU checks for
cpu_active to do so. If this check fails the threads
On Thu, 2015-07-16 at 02:32 +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 08, 2015 04:50:23 PM Viresh Kumar wrote:
> > On 08-07-15, 12:17, Jon Medhurst (Tixy) wrote:
> > > I tried these patches without the earlier "cpufreq: Initialize the
> > > governor again while restoring policy" patch.
On Wed, Jul 15, 2015 at 05:25:32PM -0700, Dmitry Torokhov wrote:
> On Thu, Jul 16, 2015 at 12:09:41AM +0200, Sebastian Reichel wrote:
> > On Wed, Jul 15, 2015 at 02:34:04PM -0700, Dmitry Torokhov wrote:
> > > [...]
> > > > if (np) {
> > > > - ts->reset_gpio =
On 15/07/15 21:39, Russell King wrote:
As we now have generic infrastructure to support backtracing of other
CPUs in the system on lockups, we can start to implement this for ARM.
Initially, we add an IPI based implementation, as the GIC code needs
modification to support the generation of FIQ
On 15/07/15 21:39, Russell King wrote:
+void nmi_trigger_all_cpu_backtrace(bool include_self,
+ void (*raise)(cpumask_t *mask))
+{
+ struct nmi_seq_buf *s;
+ int i, cpu, this_cpu = get_cpu();
+
+ if (test_and_set_bit(0, _flag)) {
+
On 07/16/2015 01:13 AM, Dave Hansen wrote:
> +/*
> + * The largest xsave buffer known today is 2752 bytes on a system
> + * implementing AVX-512. This includes the 512-byte i387 state
> + * and 64-byte header. We add a small amount of padding in case
> + * an implementation adds some padding or
This patch add mediatek iommu dts binding document.
Signed-off-by: Yong Wu
---
.../devicetree/bindings/iommu/mediatek,iommu.txt | 61
include/dt-bindings/memory/mt8173-larb-port.h | 105
2 files changed, 166 insertions(+)
create mode 100644
This patch add SMI(Smart Multimedia Interface) driver. This driver
is responsible to enable/disable iommu and control the clocks of each
local arbiter
Signed-off-by: Yong Wu
---
drivers/memory/Kconfig |8 ++
drivers/memory/Makefile|1 +
drivers/memory/mtk-smi.c | 285
This patch add the iommu/larbs nodes for mt8173
Signed-off-by: Yong Wu
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 81 ++
1 file changed, 81 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index
This patch adds support for mediatek m4u (MultiMedia Memory Management
Unit).
Signed-off-by: Yong Wu
---
drivers/iommu/Kconfig | 13 +
drivers/iommu/Makefile|1 +
drivers/iommu/mtk_iommu.c | 724 +
3 files changed, 738 insertions(+)
This patch is for ARM Short Descriptor Format.
Signed-off-by: Yong Wu
---
drivers/iommu/Kconfig| 18 +
drivers/iommu/Makefile |1 +
drivers/iommu/io-pgtable-arm-short.c | 742 ++
drivers/iommu/io-pgtable-arm.c |3 -
This patch adds support for m4u(Multimedia Memory Management Unit),
Currently it only support the m4u with 2 levels of pagetable on mt8173.
It is based on Robin Murphy's arm64 DMA v3: IOMMU-backed DMA mapping[1].
Please check the hardware block diagram of Mediatek IOMMU.
This patch add smi binding document.
Signed-off-by: Yong Wu
---
.../memory-controllers/mediatek,smi-larb.txt | 25
.../bindings/memory-controllers/mediatek,smi.txt | 24 +++
2 files changed, 49 insertions(+)
create mode 100644
On Friday 03 July 2015 12:01 AM, Vitaly Andrianov wrote:
> Interrupts for GPIOs 16 through 31 are enabled by bit 1 in the
> "binten" register (offset 8). Previous versions of GPIO only
> used bit 0, which enables GPIO 0-15 interrupts.
>
> Signed-off-by: Vitaly Andrianov
> Reviewed-by: Grygorii
On Thu, 2015-07-16 at 13:57 +0800, Zumeng Chen wrote:
> Hi All,
>
> 1028ccf5 did a change for sys_call_table from a pointer to an array of
> unsigned long, I think it's not proper, here is my reason:
>
> sys_call_table defined as a label in assembler should be pointer array
> rather than an
On Tuesday 14 July 2015 07:31 PM, Linus Walleij wrote:
> On Thu, Jun 18, 2015 at 7:10 PM, Vitaly Andrianov wrote:
>
>> Interrupts for GPIOs 16 through 31 are enabled by bit 1 in the
>> "binten" register (offset 8). Previous versions of GPIO only
>> used bit 0, which enables GPIO 0-15 interrupts.
Hi David,
On Wed, Jul 15, 2015 at 05:54:43PM +0100, David Daney wrote:
> From: David Daney
>
> The default is to continue doing the what we have done before, but add
> a hook so that this can be overridden.
This commit log is inappropriate. On top of that, it is already
complicated enough to
Ping ?
2015-07-02 10:34 GMT+02:00 Raphael Poggi :
> When wlcore_probe_of failed, return the correct error code instead of ENOMEM
>
> Signed-off-by: Raphaël Poggi
> ---
> drivers/net/wireless/ti/wlcore/sdio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
On Thu, Jul 16, 2015 at 07:27:34AM +, Ranjit Abhimanyu Waghmode wrote:
> For an example take two flashes connected in stacked mode.
> For user it doesn't matter whether how many flashes are really connected.
> There will be situation like, single partition is spread across two flashes
>
Resolves: bz1236437
https://bugzilla.redhat.com/show_bug.cgi?id=1236437
Brew build:
https://brewweb.devel.redhat.com/taskinfo?taskID=9499237
This is back ported from upstream partionly.
The crash_notes data resides in the percpu in the first kernel.
While percpu use vmalloc to allocate by
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 238ec4efeee4461d5cff2ed3e5a15a3ab850959b
Author: Martin Schwidefsky
Date: Mon Oct 25 16:10:07 2010 +0200
[S390] zero page cache synonyms
If the zero page is mapped to
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream. There are conflicts in
arch/s390/include/asm/pgtable.h.
commit 816422ad76474fed8052b6f7b905a054d082e59a
Author: Kirill A. Shutemov
Date: Wed Dec 12 13:52:36 2012 -0800
asm-generic,
Resolves: bz1236437
https://bugzilla.redhat.com/show_bug.cgi?id=1236437
Brew build:
https://brewweb.devel.redhat.com/taskinfo?taskID=9499237
This is back ported from upstream. Conflicts existed since there's no
update_note_header_size_elf64 yet in rhel6.
In commit
On Thu, Jul 16, 2015 at 10:29:13AM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The XR17V35X UART needs the ECB bit set in its XR_EFR
> register to enable access to IER [7:5], ISR [5:4], FCR[5:4],
> MCR[7:5], and MSR [7:0].
>
> Also reset the IER register to mask interrupts after access
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream directly.
commit 997c136f518c5debd63847e78e2a8694f56dcf90
Author: Olaf Hering
Date: Thu May 26 16:25:54 2011 -0700
fs/proc/vmcore.c: add hook to read_from_oldmem() to check for
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream directly.
commit 0fa73b86ef0797ca4fde5334117ca0b330f08030
Author: Andrew Morton
Date: Wed Jul 3 15:02:11 2013 -0700
include/linux/mm.h: add PAGE_ALIGNED() helper
To test whether
On Thu, Jul 16, 2015 at 08:45:06AM +, Maninder Singh wrote:
> where we are checking for (pTDInfo->skb), we are using it in above line.
> and it does not look good, thats why we should remove thse checks and i have
> suggested
> changes.
>
> code snippet:-
> ---
>
> if
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream directly.
commit b27eb186608c89ef0979ae47c649859ceaa1b2e7
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:13 2013 -0700
vmcore: clean up read_vmcore()
Rewrite part of
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream directly.
commit cef2ac3f6c8ab532e49cf69d05f540931ad8ee64
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:17 2013 -0700
vmalloc: make find_vm_area check in range
Currently,
On 16/07/15 09:35, majun (F) wrote:
>
>
> 在 2015/7/8 23:16, Marc Zyngier 写道:
>> On 08/07/15 05:21, majun (F) wrote:
>>> Hi Thomas:
>>>
> [...]
> +
> + nid = GET_NODE_NUM(d->hwirq);
> + ret = get_mbigen_node_type(nid);
> + if (ret)
> + return 0;
Care to
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream. There's a small conflict in
remap_vmalloc_range.
commit e69e9d4aee712a22665f008ae0550bb3d7c7f7c1
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:18 2013 -0700
vmalloc: introduce
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back port from upstream directly.
commit 7f614cd1e052ebbddee7ea49c725dc75fee74a5a
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:15 2013 -0700
vmcore: treat memory chunks referenced by PT_LOAD program header
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 087350c9dcf1b38c597b31d7761f7366e2866e6b
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:19 2013 -0700
vmcore: allocate ELF note segment in the 2nd kernel vmalloc memory
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 591ff71664e764a3806e341370f3c758cb2e7e3c
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:22 2013 -0700
vmcore: calculate vmcore file size from buffer size and total size of
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit ef9e78fd2753213ea01d77f7a76a9cb6ad0f50a7
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:21 2013 -0700
vmcore: allow user process to remap ELF note segment buffer
Now ELF
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream. Conflict exists since
commit 73296bc611cee009f3be6b451e827d1425b9c10f is not back ported.
commit 83086978c63afd7c73e1c173c84aeab184c1e916
Author: HATAYAMA Daisuke
Date: Wed Jul 3
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 5a74953ff56aa870d6913ef4d81934f5c620c59d
Author: Michael Holzheu
Date: Thu Jul 18 12:17:57 2013 +0200
s390/kdump: Disable mmap for s390
The kdump mmap patch series (git
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 9cb218131de1c59dca9063b2efe876f053f316af
Author: Michael Holzheu
Date: Wed Sep 11 14:24:51 2013 -0700
vmcore: introduce remap_oldmem_pfn_range()
For zfcpdump we can't
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream. It need be edited manually since
several irrelevant commits are not back ported.
commit 191a2fa0a8d2bbb64c98f9b1976fcb37ee5eae6b
Author: Michael Holzheu
Date: Thu Jul 18 12:18:27 2013
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 23df79da8eb97757e39af7625665c1c5cecc610b
Author: Jan Willeke
Date: Wed Sep 11 14:24:52 2013 -0700
s390/vmcore: implement remap_oldmem_pfn_range for s390
Introduce the
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream.
commit 0692dedcf64bf3cdcfb9f6a51c70d49c8db351d2
Author: Vitaly Kuznetsov
Date: Fri Aug 8 14:22:05 2014 -0700
fs/proc/vmcore.c:mmap_vmcore: skip non-ram pages reported by hypervisors
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream directly.
commit c2c1b089b44b783bd50fae4bccaa6f367f92e492
Author: Zhang Yanfei
Date: Wed Feb 27 17:03:17 2013 -0800
fs/proc/vmcore.c: put if tests in the top of the while loop to
Resolves: bz1236437
https://bugzilla.redhat.com/show_bug.cgi?id=1236437
Brew build:
https://brewweb.devel.redhat.com/taskinfo?taskID=9499237
This is back ported from upstream. This commit relies on commit
"vmcore: prevent PT_NOTE p_memsz overflow during header update".
commit
Resolves: bz1097904
https://bugzilla.redhat.com/show_bug.cgi?id=1097904
This is back ported from upstream. There are small format conflicts.
commit f2bdacdd597d8d05c3d5f5d36273084f7ef7e6f5
Author: HATAYAMA Daisuke
Date: Wed Jul 3 15:02:14 2013 -0700
vmcore: allocate buffer for ELF
On 16 July 2015 at 02:41, Rafael J. Wysocki wrote:
> On Wednesday, July 15, 2015 02:47:50 PM Alan Stern wrote:
>> On Wed, 15 Jul 2015, Tomeu Vizoso wrote:
>>
>> > If a suitable prepare callback cannot be found for a given device and
>> > its driver has no PM callbacks at all, assume that it can
This patchset includes 3 parts.
-
1st part:
Includes 13 upstream commits. They are recommended by Nigel Croxon
since he back ported this feature to rhel7. This 13 back ports
works for all ARCHs except of s390 since it always broke s390n kdump.
c2c1b08
Hi Dan,
>I hate these patches. I have told Markus to stop sending them but he
>has issues so now I only complain when they introduce a bug. There was
>one bug I have missed because it was a benchmark regression and I knew
>it was theoretically possible but I didn't know the code well enough to
On Thu, Jun 25, 2015 at 5:18 PM, Grygorii Strashko
wrote:
> The spinlock 'slock' is used now to protect pcf857x_irq() from itself
> which is unnecessary (especially after switching to use threaded
> IRQs). Hence, remove it and use mutex to protect device data in IRQ
> handler.
>
> Cc: Geert
On 07/15/2015 11:08 PM, Stephen Boyd wrote:
Some cleanups for the TI clk driver move.
Stephen Boyd (4):
clk: ti: Check kzalloc() for failures
clk: ti: Mark ti_clk_features static
clk: ti: clk-3xxx: Remove unused structures
clk: ti: Force pointer to be __iomem
在 2015/7/8 23:16, Marc Zyngier 写道:
> On 08/07/15 05:21, majun (F) wrote:
>> Hi Thomas:
>>
[...]
+
+ nid = GET_NODE_NUM(d->hwirq);
+ ret = get_mbigen_node_type(nid);
+ if (ret)
+ return 0;
>>>
>>> Care to explain what this does? It seems for some nodes you
On 07/15/2015 11:08 PM, Stephen Boyd wrote:
Sparse complains about these structures missing static, but they
also don't look to be used. Remove them.
drivers/clk/ti/clk-3xxx.c:74:30: warning: symbol
'clkhwops_omap3430es2_ssi_wait' was not declared. Should it be static?
phyCORE-AM335x is a SoM (System on Module) containing
a AM335x SOC. The module can be connected to different
carrier boards.
Some hardware parts are configurable on the phyCORE-AM335x.
So they are disabled on default in this som dtsi file.
They will be enabled in the board dts files, when
在 2015/7/8 21:40, Mark Rutland 写道:
> On Mon, Jul 06, 2015 at 08:09:08AM +0100, Ma Jun wrote:
[...]
>> +
>> +Mbigen means: message based interrupt generator.
>> +
>> +MBI is kind of msi interrupt only used on Non-PCI devices.
>> +
>> +To reduce the wired interrupt number connected to GIC,
>>
phyBOARD-WEGA-AM335x represents a direct soldered
combination of a phyCORE-AM335x SoM and carrier board.
Different kind of SoM options can be connected to
the wega carrier board. So we created a separate
wega dtsi file. The final dts contains the actual
SoM on the carrier board.
WEGA carrier
在 2015/7/8 23:30, Marc Zyngier 写道:
> Hi,
>
> Aside from all the comments Thomas had, the following aspect is worrying
> me a bit:
>
> On 06/07/15 08:09, Ma Jun wrote:
>> This patch contains the mbigen interrupt controller driver.
>
> [...]
>
>> +static int mbigen_set_type(struct irq_data *d,
在 2015/7/8 18:44, Thomas Gleixner 写道:
> On Wed, 8 Jul 2015, majun (F) wrote:
>> 在 2015/7/6 20:33, Thomas Gleixner 写道:
>>> Care to explain what this does? It seems for some nodes you cannot
>>> write the msi message. So how is that supposed to work? How is that
>>> interrupt controlled
On Wed, Jun 24, 2015 at 4:54 PM, Grygorii Strashko
wrote:
> From: Grygorii Strashko
>
> Add missed spin_unlock_irqrestore in omap_gpio_irq_type when
> omap_set_gpio_triggering() is failed.
>
> It fixes static checker warning:
>
> drivers/gpio/gpio-omap.c:523 omap_gpio_irq_type()
>
From: Joerg Roedel
The main use of MAX_PHANDLE_ARGS is to define the number of
args elements in 'struct of_phandle_args'. This struct is
often declared on the stack and thus it is impractical to
increase MAX_PHANDLE_ARGS again and again.
To handle situations where more than MAX_PHANDLE_ARGS
From: Joerg Roedel
The function of_parse_phandle_with_args() can only handle 16
args, but there are systems that require more (25 in my
case). So use the newly introduced function
of_parse_phandle_with_var_args() instead.
Signed-off-by: Joerg Roedel
---
drivers/iommu/arm-smmu.c | 23
From: Joerg Roedel
Hi,
here is the second version of my patches to fix the
MAX_PHANDLE_ARGS limitation for the arm-smmu driver. On my
AMD Seattle system the max value of 16 is not enough to
initialize the SMMU, as the device tree node has an entry
with 25 phandle args (possible are up to 128).
From: Krzysztof Kozlowski Sent: Thursday, July 16,
2015 2:56 PM
> To: Duan Fugang-B38611
> Cc: Kamal Mostafa; linux-kernel@vger.kernel.org; sta...@vger.kernel.org;
> kernel-t...@lists.ubuntu.com; daniel.lezc...@linaro.org; Damian Eppel;
> kyungmin.p...@samsung.com; kg...@kernel.org; Thomas
On wo, 2015-07-15 at 09:54 -0700, David Daney wrote:
> --- a/drivers/pci/host/Kconfig
> +++ b/drivers/pci/host/Kconfig
> +config PCI_THUNDER_PEM
> + bool
Do you expect other symbols to select this symbol in the future? Because
at this moment PCI_THUNDER_PEM is merely an alias for
From: Joerg Roedel
The XR17V35X UART needs the ECB bit set in its XR_EFR
register to enable access to IER [7:5], ISR [5:4], FCR[5:4],
MCR[7:5], and MSR [7:0].
Also reset the IER register to mask interrupts after access
to all bits of this register has been enabled.
This makes my 8-port
On (06/20/15 18:25), Julia Lawall wrote:
> > On (06/17/15 16:14), David Rientjes wrote:
> > [..]
> > > >
> > > > Signed-off-by: Sergey Senozhatsky
> > > > Reported-by: Andrew Morton
> > > > LKML-reference: https://lkml.org/lkml/2015/6/8/583
> > >
> > > Acked-by: David Rientjes
> > >
> > >
On Mon, Jun 22, 2015 at 5:13 PM, Dan Carpenter wrote:
> Checkpatch.pl complains about these:
>
> WARNING: Possible unnecessary 'out of memory' message
>
> The messages use a little extra RAM and they add a few extra lines of
> code. We're probably never going to hit these out of memory
On Mon, Jun 22, 2015 at 5:12 PM, Dan Carpenter wrote:
> We were allocating enough space because sizeof("-grp") and
> sizeof("-mux") are both equal to 5 but in the snprintf() we only allowed
> for 4 characters so the last 'p' and 'x' characters were truncated.
>
> The allocate and sprintf can be
Hi Arnd,
Ok, I will remove the #ifdef in the next version.
Thanks.
Hi All,
Is there any others comments?
Thanks for your review.
Best Regards,
Yuan Yao
On Wednesday, July 15, 2015 10:55 PM Arnd wrote:
> On Wednesday 15 July 2015 10:29:55 Yao Yuan wrote:
> > Hi Arnd,
> >
> > Thanks for your
On a reset cycle of OCC, although the system retires from safe
frequency state the local pstate is not restored to Pmin or last
requested pstate. Now if the cpufreq governor initiates a pstate
change, the local pstate will be in Psafe and we will be reporting a
false positive when we are not
801 - 900 of 1970 matches
Mail list logo
