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 remap
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 e
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, __find
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 explai
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 read_vmcore(
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 (p
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 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 non-ra
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 087350c9dcf1b38c597b31d7761f736
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, m
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 vir
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
> (par
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 defaul
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 a/drivers/net/w
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 ke
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 array
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 St
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
Documentation/devi
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.
EMI
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 -
d
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(+)
cre
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 e81
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 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 Documentat
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 w
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, &backtrace_flag)) {
+
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 IP
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 = of_get_named_gpio
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.
>
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 e
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 driver
在 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 chip.
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 reason
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.
>>>
>>> There
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
> debu
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, 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 implementati
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 gic_set_irqchip
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 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 s
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;
>> kyungmin.p.
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
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 insertions
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
E
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 = kpageidle_clear_
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 x
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 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.
https://git.kernel.org/powerpc/c/bd664f892e3e2b01c791
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 misleadin
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
-
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 a
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 stag
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 p
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 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
> -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 car
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 follows
> -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 cas
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: all
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 expla
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:-
---
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 pat
Hi Joerg,
On Thu, Jul 16, 2015 at 09:30:44AM +0100, Joerg Roedel wrote:
> 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()
Hi Sudeep,
On 15/07/15 15:38, Sudeep Holla wrote:
> The GIC controller doesn't provides any facility to configure the wakeup
> sources. For the same reason, GIC chip implementation can't provide
> irq_set_wake functionality, but that results in the irqchip core
> preventing the systems from enteri
In f2fs_do_collapse, region cp_rwsem covered is large, since it will be
held until all blocks are left shifted, so if we try to collapse small
area at the beginning of large file, checkpoint who want to grab writer's
lock of cp_rwsem will be delayed for long time.
In order to avoid this condition,
Wolfram,
On Thursday 09 July 2015 02:06 AM, Stephen Warren wrote:
On 06/30/2015 04:54 AM, Laxman Dewangan wrote:
Once the new configuration is set on the conifg register of
I2C controller, it is require to update the CONFIG_LOAD register
to transfer the new SW configuration to actual HW interna
In handle_failed_inode, there is a potential deadlock which can happen
in below call path:
- f2fs_create
- f2fs_lock_op down_read(cp_rwsem)
- f2fs_add_link
- __f2fs_add_link
- init_inode_metadata
- f2fs_init_securityfailed
- truncate_blocksfailed
- handle_failed_inode
-
On Thu, Jul 16, 2015 at 09:30:43AM +0100, Joerg Roedel wrote:
> 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 ag
On Wed, 8 Jul 2015 15:04:48 +0300
Daniel Baluta wrote:
> This is intended to help developers faster find their way
> inside the Industrial I/O core and reduce time spent on IIO
> drivers development.
Seems like good stuff to have, sorry it's taken me so long to have a look
at it. Any other IIO
zdravo
Pozdravljajući iz SUN EAST Federalni Kreditne UNION, mi smo dobro uspostavljena
i odobrena Velikoj Britaniji kredita kompanijama, tokom godina, razvili smo
dobro razumijevanje vaših potreba i individualnim potrebama. mi smo posvećeni
nas da se prema našim kupcima pošteno i ponuditi us
On Wed, 15 Jul 2015 21:14:39 +0200,
Keith Packard wrote:
>
> Takashi Iwai writes:
>
> > Thanks! The new patch looks good, but I think we don't have to use
> > the headset code, as your case looks more like a headphone, not a
> > combo headset that needs the special handling. If so, the change
On Thu, 16 Jul 2015 03:04:10 +0200,
kernelpatch_update wrote:
>
> In kstrdup we should return -ENOMEM when it reports an
> memory allocation failure, while the -ENODEV is referred
> to a failure in finding the cpu node in the device tree.
>
> Signed-off-by: kernelpatch_update
Thanks, applied n
On Thu, 16 Jul 2015 12:27:07 +0200,
Takashi Iwai wrote:
>
> On Thu, 16 Jul 2015 03:04:10 +0200,
> kernelpatch_update wrote:
> >
> > In kstrdup we should return -ENOMEM when it reports an
> > memory allocation failure, while the -ENODEV is referred
> > to a failure in finding the cpu node in the
On Wed, Jul 15, 2015 at 03:26:19PM +0300, Michael S. Tsirkin wrote:
> ANY_LAYOUT is a compatibility feature. It's implied
> for VERSION_1 devices, and non-transitional devices
> might not offer it. Change code to behave accordingly.
>
> Signed-off-by: Michael S. Tsirkin
> ---
> drivers/net/virti
On 16/07/15 03:54, Peter Chen wrote:
> On Wed, Jul 15, 2015 at 04:30:27PM +0300, Roger Quadros wrote:
>> On 14/07/15 03:34, Peter Chen wrote:
>>> On Mon, Jul 13, 2015 at 01:13:54PM +0300, Roger Quadros wrote:
Peter,
On 13/07/15 04:58, Peter Chen wrote:
> On Wed, Jul 08, 2015 at 0
On 07/16/15 at 12:02pm, Denys Vlasenko wrote:
> +/* jhash - hash an arbitrary key
> + * @k: sequence of bytes as key
> + * @length: the length of the key
> + * @initval: the previous hash, or an arbitray value
> + *
> + * The generic version, hashes an arbitrary sequence of bytes.
> + * No alignmen
On Thu, 16 Jul 2015, Baolin Wang wrote:
> On 15 July 2015 at 19:55, Thomas Gleixner wrote:
> > On Wed, 15 Jul 2015, Baolin Wang wrote:
> >
> >> On 15 July 2015 at 18:31, Thomas Gleixner wrote:
> >> > On Wed, 15 Jul 2015, Baolin Wang wrote:
> >> >
> >> >> The cputime_to_timespec() and timespec_to_
Fixed the "unused variable" warning for the driver.
Signed-off-by: Sreenath Madasu
---
drivers/staging/rtl8188eu/core/rtw_ap.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_ap.c
b/drivers/staging/rtl8188eu/core/rtw_ap.c
index 1a32e7b..5bded92 100644
---
Hi Andy/Joe,
I got a warning today for my cover-letter, and it looked like a false
positive. Please have a look, based of v4.2-rc2.
---
-cover-letter.patch
---
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per
line)
#31:
a
This patch fix spelling typos found in coresight.txt
Signed-off-by: Masanari Iida
---
Documentation/trace/coresight.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/trace/coresight.txt
b/Documentation/trace/coresight.txt
index 77d14d5..0a5c329 100644
---
Hi Thomas/Ingo,
This series migrates x86 architecture clockevent drivers to the new
set-state interface. This would enable these drivers to use new states
(like: ONESHOT_STOPPED, etc.) of a clockevent device (if required), as
the set-mode interface is marked obsolete now and wouldn't be expanded
t
Migrate apic driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
We weren't doing anything while switching to
Migrate hpet driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
Forward definition of 'hpet_clockevent' wasn'
Migrate xen driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
Callbacks aren't implemented for modes where w
Migrate lguest driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
We weren't doing anything while switching m
Migrate uv driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
We weren't doing anything while switching modes
Sorry to bother you. I just sent to the wrong mailing list. Please
ignore this thread.
On 07/16/15 at 04:46pm, Baoquan He wrote:
> This patchset includes 3 parts.
>
> -
> 1st part:
> Includes 13 upstream commits. They are recommended by Nigel Croxon
> since he
On Thu, Jul 16, 2015 at 10:05:44AM +0200, Paul Bolle wrote:
> > +static struct platform_driver snd_rk_mc_driver = {
> > + .probe = snd_rk_mc_probe,
> > + .remove = snd_rk_mc_remove,
> > + .driver = {
> > + .name = DRV_NAME,
> > +MODULE_ALIAS("platform:" DRV_NAME);
> This seems on
On Thu, Jun 25, 2015 at 10:29 AM, Michal Simek wrote:
> Add missing pm_runtime_disabled to remove().
>
> Error log:
> root@zynqmp:~# modprobe gpio_zynq
> root@zynqmp:~# lsmod
> Not tainted
> gpio_zynq 7086 0 - Live 0xffbffc00a000
> root@zynqmp:~# rmmod gpio_zynq
> root@zynqmp:~# lsmod
>
Dave Hansen wrote:
> On 07/13/2015 09:53 AM, Oleg Nesterov wrote:
> > On 07/13, Kirill A. Shutemov wrote:
> >>
> >> We don't really need ->vm_ops here: MPX VMA can be detected with VM_MPX
> >> flag. And vma_merge() will not merge MPX VMA with non-MPX VMA, because
> >> ->vm_flags won't match.
> >
>
On Thu, 2 Jul 2015 15:08:11 +0200
Igor Mammedov wrote:
> it became possible to use a bigger amount of memory
> slots, which is used by memory hotplug for
> registering hotplugged memory.
> However QEMU crashes if it's used with more than ~60
> pc-dimm devices and vhost-net enabled since host ker
On Wed, 15 Jul 2015, Russell King wrote:
> x86s NMI backtrace implementation (for arch_trigger_all_cpu_backtrace())
> is fairly generic in nature - the only architecture specific bits are
> the act of raising the NMI to other CPUs, and reporting the status of
> the NMI handler.
>
> These are fair
On 07/11/2015 01:03 AM, Stephen Boyd wrote:
This file doesn't use the clk provider APIs. Remove the include.
Cc: Michal Simek
Cc: Daniel Lezcano
Signed-off-by: Stephen Boyd
---
Please ack if you want this to go through clk-tree, otherwise
it's ok to take it through the clocksource side.
Th
On Wed, 15 Jul 2015, Russell King wrote:
> Convert x86 to use the generic nmi handler code which can be shared
> between architectures.
>
> Signed-off-by: Russell King
Reviewed-and-tested-by: Thomas Gleixner
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Hi Will,
On Thu, Jul 16, 2015 at 11:23:26AM +0100, Will Deacon wrote:
> On Thu, Jul 16, 2015 at 09:30:43AM +0100, Joerg Roedel wrote:
> > +struct of_phandle_args *of_alloc_phandle_args(int size)
> > +{
> > + struct of_phandle_args *args;
> > + int e = max(0, size - MAX_PHANDLE_ARGS);
> > +
> >
On Mon, 13 Jul 2015, Rob Herring wrote:
> On Sun, Jul 12, 2015 at 11:43 AM, Thomas Gleixner wrote:
> > So in most of the irqchip drivers, this is irrelevant.
>
> Agreed, but that's a separate series I think. I'm trying not to change
> behavior with this series. Are you proposing I do something di
Create a file "nest-pmu.c" to contain nest pmu related functions. Code
to detect nest pmu support and parser to collect per-chip reserved memory
region information from device tree (DT).
Detection mechanism is to look for specific property "ibm,ima-chip" in DT.
For Nest pmu, device tree will have
Parse device tree to detect supported nest pmu units. Traverse
through each nest pmu unit folder to find supported events and
corresponding unit/scale files (if any).
The nest unit event file from DT, will contain the offset in the
reserved memory region to get the counter data for a given event.
101 - 200 of 994 matches
Mail list logo
