[no subject]

-0500 Subject: [PATCH 0/5] mm: code and data partitioning improvements Managing allocations to ensure code and data pages are not interleaved is not possible prior to this patch, as ASLR requires programming a dynamic _text offset while the vmalloc infrastructure maintains static VMALLOC_START

Patch "Subject:[For 5.15/5.10/5.4] spi: fsl-spi: Re-organise transfer bits_per_word adaptation" has been added to the 5.15-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 5.15/5.10/5.4] spi: fsl-spi: Re-organise transfer bits_per_word adaptation to the 5.15-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 5.15/5.10/5.4] spi: fsl-cpm: Use 16 bit mode for large transfers with even size" has been added to the 5.15-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 5.15/5.10/5.4] spi: fsl-cpm: Use 16 bit mode for large transfers with even size to the 5.15-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git

Patch "Subject:[For 5.15/5.10/5.4] spi: fsl-spi: Re-organise transfer bits_per_word adaptation" has been added to the 5.10-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 5.15/5.10/5.4] spi: fsl-spi: Re-organise transfer bits_per_word adaptation to the 5.10-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 5.15/5.10/5.4] spi: fsl-cpm: Use 16 bit mode for large transfers with even size" has been added to the 5.10-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 5.15/5.10/5.4] spi: fsl-cpm: Use 16 bit mode for large transfers with even size to the 5.10-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git

Patch "Subject:[For 4.19/4.14] spi: fsl-spi: Re-organise transfer bits_per_word adaptation" has been added to the 4.19-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 4.19/4.14] spi: fsl-spi: Re-organise transfer bits_per_word adaptation to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 4.19/4.14] spi: spi-fsl-spi: automatically adapt bits-per-word in cpu mode" has been added to the 4.19-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 4.19/4.14] spi: spi-fsl-spi: automatically adapt bits-per-word in cpu mode to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 4.19/4.14] spi: fsl-cpm: Use 16 bit mode for large transfers with even size" has been added to the 4.19-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 4.19/4.14] spi: fsl-cpm: Use 16 bit mode for large transfers with even size to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 4.19/4.14] spi: spi-fsl-spi: automatically adapt bits-per-word in cpu mode" has been added to the 4.14-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 4.19/4.14] spi: spi-fsl-spi: automatically adapt bits-per-word in cpu mode to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 4.19/4.14] spi: fsl-spi: Re-organise transfer bits_per_word adaptation" has been added to the 4.14-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 4.19/4.14] spi: fsl-spi: Re-organise transfer bits_per_word adaptation to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

Patch "Subject:[For 4.19/4.14] spi: fsl-cpm: Use 16 bit mode for large transfers with even size" has been added to the 4.14-stable tree

This is a note to let you know that I've just added the patch titled Subject:[For 4.19/4.14] spi: fsl-cpm: Use 16 bit mode for large transfers with even size to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

[no subject]

Hello Powerpc folks, I encounter an kdump bug, which I bisect and pin commit 174db9e7f775 ("powerpc/pseries/pci: Add support of MSI domains to PHB hotplug") In that case, using Fedora 36 as host, the mentioned commit as the guest kernel, and virto-block disk, the kdump kernel will hang: [

[no subject]

+Daniel, Thomas, Viresh Subject: Re: rcu_sched self-detected stall on CPU Excerpts from Michael Ellerman's message of April 9, 2022 12:42 am: > Michael Ellerman writes: >> "Paul E. McKenney" writes: >>> On Wed, Apr 06, 2022 at 05:31:10PM +0800, Zhouyi Zhou wro

Re: [PATCH] Subject: [PATCH] macintosh/via-pmu: Avoid compiler warnings when CONFIG_PROC_FS is disabled

Please disregard. I'll send v2 with corrected commit log entry.

[PATCH] Subject: [PATCH] macintosh/via-pmu: Avoid compiler warnings when CONFIG_PROC_FS is disabled

drivers/macintosh/via-pmu.c:897:12: warning: 'pmu_battery_proc_show' defined but not used [-Wunused-function] static int pmu_battery_proc_show(struct seq_file *m, void *v) ^ drivers/macintosh/via-pmu.c:871:12: warning: 'pmu_irqstats_proc_show' defined but not

Re: (No subject)

You should also fix the existing typo in the documentation (inline): > On Dec 27, 2021, at 07:49, Kefeng Wang wrote: > > This patch select HAVE_ARCH_HUGE_VMALLOC to let arm64 support huge > vmalloc mappings. > > Cc: Catalin Marinas > Cc: Will Deacon > Signed-off-by: Kefeng Wang > --- >

Re: [PATCH v4] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

nter argument to > > > security_lockdown() and define NULL as a special value to pass instead > > > of current_cred() in such situations. LSMs that take the subject > > > credentials into account can then fall back to some default or ignore > > > such calls altoge

Re: [PATCH v4] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

r argument to > > > security_lockdown() and define NULL as a special value to pass instead > > > of current_cred() in such situations. LSMs that take the subject > > > credentials into account can then fall back to some default or ignore > > > such calls altogethe

Re: [PATCH v4] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

at would > > directly breach lockdown, leading to SELinux checks that are basically > > bogus. > > > > To fix this, add an explicit struct cred pointer argument to > > security_lockdown() and define NULL as a special value to pass instead > > of current_cred() in such si

Re: [PATCH v4] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

fix this, add an explicit struct cred pointer argument to > security_lockdown() and define NULL as a special value to pass instead > of current_cred() in such situations. LSMs that take the subject > credentials into account can then fall back to some default or ignore > such calls al

Re: [PATCH v4] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

, add an explicit struct cred pointer argument to > security_lockdown() and define NULL as a special value to pass instead > of current_cred() in such situations. LSMs that take the subject > credentials into account can then fall back to some default or ignore > such calls al

[PATCH v4] lockdown, selinux: fix wrong subject in some SELinux lockdown checks

ss instead of current_cred() in such situations. LSMs that take the subject credentials into account can then fall back to some default or ignore such calls altogether. In the SELinux lockdown hook implementation, use SECINITSID_KERNEL in case the cred argument is NULL. Most of the callers are updat

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

On Tue, Aug 31, 2021 at 2:58 PM Dan Williams wrote: > On Tue, Aug 31, 2021 at 6:53 AM Paul Moore wrote: > > On Tue, Aug 31, 2021 at 5:09 AM Ondrej Mosnacek wrote: > > > On Sat, Jun 19, 2021 at 12:18 AM Dan Williams > > > wrote: > > > > On Wed, Jun 16, 2021 at 1:51 AM Ondrej Mosnacek > > > >

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

On Tue, Aug 31, 2021 at 6:53 AM Paul Moore wrote: > > On Tue, Aug 31, 2021 at 5:09 AM Ondrej Mosnacek wrote: > > On Sat, Jun 19, 2021 at 12:18 AM Dan Williams > > wrote: > > > On Wed, Jun 16, 2021 at 1:51 AM Ondrej Mosnacek > > > wrote: > > ... > > > > > diff --git a/drivers/cxl/mem.c

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

On Tue, Aug 31, 2021 at 5:09 AM Ondrej Mosnacek wrote: > On Sat, Jun 19, 2021 at 12:18 AM Dan Williams > wrote: > > On Wed, Jun 16, 2021 at 1:51 AM Ondrej Mosnacek wrote: ... > > > diff --git a/drivers/cxl/mem.c b/drivers/cxl/mem.c > > > index 2acc6173da36..c1747b6555c7 100644 > > > ---

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

On Tue, Aug 31, 2021 at 5:08 AM Ondrej Mosnacek wrote: > Can we move this forward somehow, please? As mentioned previously, I can merge this via the SELinux tree but I need to see some ACKs from the other subsystems first, not to mention some resolution to the outstanding questions. -- paul

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

would > > directly breach lockdown, leading to SELinux checks that are basically > > bogus. > > > > To fix this, add an explicit struct cred pointer argument to > > security_lockdown() and define NULL as a special value to pass instead > > of current_cred() in such situa

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

ectly breach lockdown, leading to SELinux checks that are basically > > bogus. > > > > To fix this, add an explicit struct cred pointer argument to > > security_lockdown() and define NULL as a special value to pass instead > > of current_cred() in such situations. LSM

Re: [PATCHv2 0/3] Subject: [PATCHv2 0/3] Make cache-object aware of L3 siblings by parsing "ibm, thread-groups" property

On Wed, 28 Jul 2021 23:26:04 +0530, Parth Shah wrote: > Changes from v1 -> v2: > - Based on Gautham's comments, use a separate thread_group_l3_cache_map > and modify parsing code to build cache_map for L3. This makes the > cache_map building code isolated from the parsing code. > v1 can be

[PATCHv2 0/3] Subject: [PATCHv2 0/3] Make cache-object aware of L3 siblings by parsing "ibm, thread-groups" property

Changes from v1 -> v2: - Based on Gautham's comments, use a separate thread_group_l3_cache_map and modify parsing code to build cache_map for L3. This makes the cache_map building code isolated from the parsing code. v1 can be found at:

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

On Sat, Jun 19, 2021 at 1:00 PM Thomas Gleixner wrote: > On Wed, Jun 16 2021 at 10:51, Ondrej Mosnacek wrote: > > diff --git a/arch/x86/mm/testmmiotrace.c b/arch/x86/mm/testmmiotrace.c > > index bda73cb7a044..c43a13241ae8 100644 > > --- a/arch/x86/mm/testmmiotrace.c > > +++

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

x this, add an explicit struct cred pointer argument to > security_lockdown() and define NULL as a special value to pass instead > of current_cred() in such situations. LSMs that take the subject > credentials into account can then fall back to some default or ignore > such calls altog

Re: [PATCH v3] lockdown, selinux: fix wrong subject in some SELinux lockdown checks

On Wed, Jun 16 2021 at 10:51, Ondrej Mosnacek wrote: > diff --git a/arch/x86/mm/testmmiotrace.c b/arch/x86/mm/testmmiotrace.c > index bda73cb7a044..c43a13241ae8 100644 > --- a/arch/x86/mm/testmmiotrace.c > +++ b/arch/x86/mm/testmmiotrace.c > @@ -116,7 +116,7 @@ static void

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

, add an explicit struct cred pointer argument to > security_lockdown() and define NULL as a special value to pass instead > of current_cred() in such situations. LSMs that take the subject > credentials into account can then fall back to some default or ignore > such calls al

Re: [PATCH v3] lockdown,selinux: fix wrong subject in some SELinux lockdown checks

, add an explicit struct cred pointer argument to > security_lockdown() and define NULL as a special value to pass instead > of current_cred() in such situations. LSMs that take the subject > credentials into account can then fall back to some default or ignore > such calls al

[PATCH v3] lockdown, selinux: fix wrong subject in some SELinux lockdown checks

ss instead of current_cred() in such situations. LSMs that take the subject credentials into account can then fall back to some default or ignore such calls altogether. In the SELinux lockdown hook implementation, use SECINITSID_KERNEL in case the cred argument is NULL. Most of the callers are updat

[no subject]

@lists.ozlabs.org, linux-ker...@vger.kernel.org, clang-built-li...@googlegroups.com Subject: Re: [PATCH v4 1/2] powerpc/uaccess: Implement unsafe_put_user() using 'asm goto' Message-ID: <20200611223838.ga60...@google.com> References: <23e680624680a9a5405f4b88740d2596d4b17c26.1

Re: [PATCH V2 00/11] Subject: Remove duplicated kmap code

On Mon, May 04, 2020 at 10:02:25PM +0100, Al Viro wrote: > On Mon, May 04, 2020 at 01:17:41PM -0700, Ira Weiny wrote: > > > > || * arm: much, much worse. We have several files that pull > > > linux/highmem.h: > > > || arch/arm/mm/cache-feroceon-l2.c, arch/arm/mm/cache-xsc3l2.c, > > > ||

Re: [PATCH V2 00/11] Subject: Remove duplicated kmap code

On Mon, May 04, 2020 at 01:17:41PM -0700, Ira Weiny wrote: > > || * arm: much, much worse. We have several files that pull > > linux/highmem.h: > > || arch/arm/mm/cache-feroceon-l2.c, arch/arm/mm/cache-xsc3l2.c, > > || arch/arm/mm/copypage-*.c, arch/arm/mm/dma-mapping.c, arch/arm/mm/flush.c, >

Re: [PATCH V2 00/11] Subject: Remove duplicated kmap code

On Mon, May 04, 2020 at 06:33:57AM +0100, Al Viro wrote: > On Sun, May 03, 2020 at 10:04:47PM -0700, Ira Weiny wrote: > > > Grepping for 'asm/highmem.h' and investigations don't reveal any issues... > > But > > you do have me worried. That said 0-day has been crunching on multiple > > versions

Re: [PATCH V2 00/11] Subject: Remove duplicated kmap code

On Sun, May 03, 2020 at 10:04:47PM -0700, Ira Weiny wrote: > Grepping for 'asm/highmem.h' and investigations don't reveal any issues... > But > you do have me worried. That said 0-day has been crunching on multiple > versions of this series without issues such as this (save the mips issue >

Re: [PATCH V2 00/11] Subject: Remove duplicated kmap code

On Mon, May 04, 2020 at 02:35:09AM +0100, Al Viro wrote: > On Sun, May 03, 2020 at 06:09:01PM -0700, ira.we...@intel.com wrote: > > From: Ira Weiny > > > > The kmap infrastructure has been copied almost verbatim to every > > architecture. > > This series consolidates obvious duplicated code by

Re: [PATCH V2 00/11] Subject: Remove duplicated kmap code

On Sun, May 03, 2020 at 06:09:01PM -0700, ira.we...@intel.com wrote: > From: Ira Weiny > > The kmap infrastructure has been copied almost verbatim to every architecture. > This series consolidates obvious duplicated code by defining core functions > which call into the architectures only when

[PATCH V2 00/11] Subject: Remove duplicated kmap code

From: Ira Weiny The kmap infrastructure has been copied almost verbatim to every architecture. This series consolidates obvious duplicated code by defining core functions which call into the architectures only when needed. Some of the k[un]map_atomic() implementations have some similarities but

RE: [PATCH v3 00/11] *** SUBJECT HERE ***

ail.com; > gustavo.pimen...@synopsys.com; linux-...@vger.kernel.org; > devicet...@vger.kernel.org; linux-ker...@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; linuxppc-dev@lists.ozlabs.org > Cc: a...@arndb.de; gre...@linuxfoundation.org; Xiaowei Bao > > Subject: RE: [PATCH v

RE: [PATCH v3 00/11] *** SUBJECT HERE ***

.com; > gustavo.pimen...@synopsys.com; linux-...@vger.kernel.org; > devicet...@vger.kernel.org; linux-ker...@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; linuxppc-dev@lists.ozlabs.org > Cc: a...@arndb.de; gre...@linuxfoundation.org; Z.q. Hou > ; Xiaowei Bao > Subject: [PATCH v3 00/

[PATCH v3 00/11] *** SUBJECT HERE ***

*** BLURB HERE *** Xiaowei Bao (11): PCI: designware-ep: Add multiple PFs support for DWC PCI: designware-ep: Add the doorbell mode of MSI-X in EP mode PCI: designware-ep: Move the function of getting MSI capability forward PCI: designware-ep: Modify MSI and MSIX CAP way of finding

[no subject]

Subject: [PATCH] powerpc: Add back __ARCH_WANT_SYS_LLSEEK macro This partially reverts commit caf6f9c8a326 ("asm-generic: Remove unneeded __ARCH_WANT_SYS_LLSEEK macro") When CONFIG_COMPAT is disabled on ppc64 the kernel does not build. There is resistance to both removing the llse

Re: [PATCH v5 0/4] *** SUBJECT HERE ***

On Mon, Jun 24, 2019 at 07:20:13AM +, Christophe Leroy wrote: > This series is the last set of fixes for the Talitos driver. > > We now get a fully clean boot on both SEC1 (SEC1.2 on mpc885) and > SEC2 (SEC2.2 on mpc8321E) with CONFIG_CRYPTO_MANAGER_EXTRA_TESTS: > > [3.385197] bus:

[PATCH v5 0/4] *** SUBJECT HERE ***

This series is the last set of fixes for the Talitos driver. We now get a fully clean boot on both SEC1 (SEC1.2 on mpc885) and SEC2 (SEC2.2 on mpc8321E) with CONFIG_CRYPTO_MANAGER_EXTRA_TESTS: [3.385197] bus: 'platform': really_probe: probing driver talitos with device ff02.crypto [

[no subject]

prom_init is a rather "special" bit of code. Run once when booting from Open Firmware as pretty much the very first thing we do, it will perform all communications with OF before it gets killed and extract the device-tree for the kernel use. It will then re-enter the kernel at its main entry point

[no subject]

confirm 179e695f420474677205db49a8cbfe950329975c

[no subject]

confirm 0da5e6b1343dcc6395ebcc8054c362d930498440

[PATCH 2/9] powerpc/pseries: radix is not subject to RMA limit, remove it

The radix guest is not subject to the paravirtualized HPT VRMA limit, so remove that from ppc64_rma_size calculation for that platform. Signed-off-by: Nicholas Piggin <npig...@gmail.com> --- arch/powerpc/mm/pgtable-radix.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-)

Re: Subject: [PATCH V4 3/4] hotplug/drc-info: Add code to search ibm,drc-info property

See below. On 11/20/2017 09:38 AM, Nathan Fontenot wrote: > On 11/16/2017 02:11 PM, Michael Bringmann wrote: >> rpadlpar_core.c: Provide parallel routines to search the older device- >> tree properties ("ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types" >> and "ibm,drc-power-domains"), or the

[no subject]

Hello , I have been working on trying to get a newer kernel and Ubuntu version running on the PS3 within otherOS on a PS3 slim. I managed to find a git repository made by Geoff that is still being updated as of a few days ago. That can be found here -

Re: Subject: [PATCH V4 3/4] hotplug/drc-info: Add code to search ibm,drc-info property

On 11/16/2017 02:11 PM, Michael Bringmann wrote: > rpadlpar_core.c: Provide parallel routines to search the older device- > tree properties ("ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types" > and "ibm,drc-power-domains"), or the new property "ibm,drc-info". > > The interface to examine the DRC

Subject: [PATCH V4 3/4] hotplug/drc-info: Add code to search ibm,drc-info property

rpadlpar_core.c: Provide parallel routines to search the older device- tree properties ("ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types" and "ibm,drc-power-domains"), or the new property "ibm,drc-info". The interface to examine the DRC information is changed from a "get" function that returns

Subject: [PATCH V3 2/4] pseries/drc-info: Search DRC properties for CPU indexes

pseries/drc-info: Provide parallel routines to convert between drc_index and CPU numbers at runtime, using the older device-tree properties ("ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types" and "ibm,drc-power-domains"), or the new property "ibm,drc-info". Signed-off-by: Michael Bringmann

[no subject]

Date: Sun, 20 Aug 2017 13:16:16 +1000 Subject: [PATCH] timers: Fix excessive granularity of new timers after a nohz idle When a timer base is idle, it is forwarded when a new timer is added to ensure that granularity does not become excessive. When not idle, the timer tick is expected

[no subject]

Reply-To: X-Mailer: Mutt 1.5.24 (2015-08-30) unsubscribe

Subject: [PATCH V7 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory

On Power systems with shared configurations of CPUs and memory, there are some issues with association of additional CPUs and memory to nodes when hot-adding resources. These patches address some of those problems. powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU or memory

[no subject]

Hi, the commit 5a319350a46572d073042a3194676099dd2c135d has introduces the following warning with CONFIG_DEBUG_PREEMPT enabled: [ 129.314426] BUG: using smp_processor_id() in preemptible [] code: modprobe/5459 [ 129.314580] caller is .kvmppc_book3s_init_hv+0x184/0x350 [kvm_hv] [

[no subject]

> -header-y += msr-index.h I see it on my desktop as /usr/include/asm/msr-index.h and it's been there at least four years - and as such it's part of the UAPI. I don't think you can remove it unless you can guarantee there are no userspace users. David

[no subject]

Nicolas Dichtel wrote: > This header file is exported, thus move it to uapi. Exported how? > +#ifdef __INT32_TYPE__ > +#undef __INT32_TYPE__ > +#define __INT32_TYPE__ int > +#endif > + > +#ifdef __UINT32_TYPE__ > +#undef __UINT32_TYPE__ > +#define

[no subject]

We have seen on a number of benchmarks that the scheduler does not operate like you (I) would expect. One of the tools we have examined a trace file and showed that, for a "long" period of time, two processes were sharing a single cpu. That, in itself, is not startling, but there were a number

[no subject]

vgo...@redhat.com linux-ker...@vger.kernel.org, Eric Biederman <ebied...@xmission.com> Bcc: ruy...@redhat.com Subject: Re: [PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer. Reply-To: In-Reply-To: <5428891.iJNV8CI1We@hactar> On 06/27/1

[no subject]

--- Begin Message --- Definitely would have made sense for years, but could someone possibly look into a proper solution? Michel Dänzer schrieb am Mo., 8. Feb. 2016 11:00: > On 05.02.2016 11:47, Mike wrote: > > Hi. > > Managed to get the Radeon R300 running on mesa 11.1.1

[no subject]

--- Begin Message --- > Since binutils 2.26 BFD is doing suffix merging on STRTAB sections. > But dedotify modifies the symbol names in place, which can also modify > unrelated symbols with a name that matches a suffix of a dotted > name. To remove the leading dot of a symbol name we can just >

[no subject]

--- Begin Message --- On Thu, 28 Jan 2016, David Rientjes wrote: > On Thu, 28 Jan 2016, Christian Borntraeger wrote: > > > Indeed, I only touched the identity mapping and dump stack. > > The question is do we really want to change free_init_pages as well? > > The unmapping during runtime causes

[no subject]

--- Begin Message --- On Thu, 28 Jan 2016, Christian Borntraeger wrote: > Indeed, I only touched the identity mapping and dump stack. > The question is do we really want to change free_init_pages as well? > The unmapping during runtime causes significant overhead, but the > unmapping after init

[no subject]

--- Begin Message --- On Wed, 27 Jan 2016, Christian Borntraeger wrote: > We can use debug_pagealloc_enabled() to check if we can map > the identity mapping with 2MB pages. We can also add the state > into the dump_stack output. > > The patch does not touch the code for the 1GB pages, which

[no subject]

--- Begin Message --- On Wed, 27 Jan 2016, Christian Borntraeger wrote: > We can use debug_pagealloc_enabled() to check if we can map > the identity mapping with 1MB/2GB pages as well as to print > the current setting in dump_stack. > > Signed-off-by: Christian Borntraeger

[no subject]

Bcc: Subject: Re: [PATCH 3/4] CXL: Enable CAPP recovery In-reply-to: 1421437687-12835-3-git-send-email-gr...@linux.vnet.ibm.com References: 1421437687-12835-1-git-send-email-gr...@linux.vnet.ibm.com 1421437687-12835-3-git-send-email-gr...@linux.vnet.ibm.com Acked-by: Ian Munsie imun...@au1

[PATCH 0/6] *** SUBJECT HERE ***

Hi Ben, Here is a short series of updates for PS3, none are critical. Please queue. These are based on v3.18. I can rebase to something else if you like. The first three patches are to have the kernel write the PS3 highmem info to the LV1 hypervisor registry so that the info will be

[no subject]

Hello, This patch series is mostly Freescale's SAI SoC Digital Audio Interface driver implementation. And the implementation is only compatible with device tree definition. This patch series is based on linux-next and has been tested on Vybrid VF610 Tower board using device tree. Changed in

[no subject]

Subject: [PATCH 0/9][v5] powerpc/perf: Export memory hierarchy level in Power7/8. Power7 and Power8 processors save the memory hierarchy level (eg: L2, L3) from which a load or store instruction was satisfied. Export this hierarchy information to the user via the perf_mem_data_src object

[no subject]

Fcc: +outbox Subject: [PATCH v2] powerpc: Avoid link stack corruption for MMU on exceptions In-reply-to: 20130813150617.dba639d38dad2ea41668c...@canb.auug.org.au References: 18522.1376360...@ale.ozlabs.ibm.com 20130813150617.dba639d38dad2ea41668c...@canb.auug.org.au Comments: In-reply-to Stephen

[PATCH v6 0/3] *** SUBJECT HERE ***

Changes for v6: - Only using imx-udc-mx27 and imx-udc-mx51 stands for all kinds of i.mx udc - Fix below build error for platform_device_id at fsl_udc_core.c drivers/usb/gadget/fsl_usb2_udc: struct platform_device_id is 24 bytes.? The last of 5 is: | 0x69 0x6d 0x78 0x2d 0x75 0x64 0x63 0x2d 0x6d

[no subject]

Hi The P1020 manual states (in the PIC chapter) that in the Internal Interrupt Destination register, only 1 CPU (and not both) can be selected as the IRQ destination. How then can we achieve interrupt spraying for the PCI interrupt (we want interrupts to be sent alternately to CPU0 and CPU1).

[no subject]

please remove me from the list... thanks ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

[no subject]

Hi, I'm using the 3.0.3 kernel on an MPC8308 and have turned on GPIO support (CONFIG_GPIOLIB = Y) because the SPI sub-system needed to use it for the GPIO pin I'm using as a CS to a NvRAM part. I also have some jumpers on the processor GPIO pins and I thought it would be really slick to use

[no subject]

From 1a44c074e3ce572cbf60d31ac704e6ce42be4708 Mon Sep 17 00:00:00 2001 From: Tony Breeds t...@bakeyournoodle.com Date: Wed, 23 Nov 2011 10:16:40 +1100 Subject: [PATCH] powerpc: 44x: Add mtd ndfc to the ppx44x defconfig Signed-off-by: Tony Breeds t...@bakeyournoodle.com --- arch/powerpc/configs

[no subject]

From 1a44c074e3ce572cbf60d31ac704e6ce42be4708 Mon Sep 17 00:00:00 2001 From: Tony Breeds t...@bakeyournoodle.com Date: Wed, 23 Nov 2011 10:16:40 +1100 Subject: [PATCH] powerpc: 44x: Add mtd ndfc to the ppx44x defconfig Signed-off-by: Tony Breeds t...@bakeyournoodle.com --- arch/powerpc/configs

[no subject]

Is anyone working on Linus suggestion to combine the defconfigs under 44x or 4xx ? Thanks, Marri ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

[PATCH 0/4] *** SUBJECT HERE ***

Josh, Here are some bug fixes for the powerpc-4xx tree. It'd be nice if they could make it into 2.6.46. Thanks, Shaggy Dave Kleikamp (4): powerpc/47x: Make sure mcsr is cleared before enabling machine check interrupts powerpc/47x: Remove redundant line from cputable.c powerpc/4xx:

[no subject]

Dear Rupjyoti, drivers/ata/sata_dwc_460ex.c fails to build in current mainline: ... CC drivers/ata/sata_dwc_460ex.o drivers/ata/sata_dwc_460ex.c:43:1: warning: DRV_NAME redefined In file included from drivers/ata/sata_dwc_460ex.c:38: drivers/ata/libata.h:31:1: warning: this is the

[no subject]

These patches add the required mappings to use perf probe on PowerPC. Functionality wise it requires patch 359e4284a3f37aba7fd06d993863de2509d86f54 from the powerpc-next tree to provide the HAVE_REGS_AND_STACK_ACCESS_API required for CONFIG_KPROBE_EVENT. The code will still compile cleanly

[PATCH 0/2] *** SUBJECT HERE ***

*** BLURB HERE *** Bill Gatliff (2): Use struct of_i2c_gpio_chip instead of raw struct gpio_chip Reorder initialization to better support device tree data drivers/gpio/pca953x.c | 168 +--- 1 files changed, 88 insertions(+), 80 deletions(-)

Re: [PATCH 0/2] *** SUBJECT HERE ***

Bill Gatliff wrote: *** BLURB HERE *** Dangit, sometimes I really hate it when emacs leaves its backup files around... :( Like now, for example. Please disregard the noise generated by my careless use of filename wildcards... b.g. -- Bill Gatliff Embedded systems training and

[no subject]

Subject: [PATCH][v4] powerpc/85xx: Added P1020RDB Platform support. P1020 is another member of Freescale QorIQ series of processors. It is an e500 based dual core SOC. Being a scaled down version of P2020 it has following differences from P2020: - 533MHz - 800MHz core frequency. - 256Kbyte L2

Subject: Re: PPCboot and latest kernel

vijay sharma wrote: Linux/PowerPC load: Finalizing device tree... flat tree at 0x2f65300 == Beyond this point no output is available. I have found that on my MPC8272 system running 2.6.28 cuImage, the /chosen/linux,stdout-path node is respected by the boot wrapper, but the main kernel always

[no subject]

This patch (against 2.6.30) adds support for the ESTeem 195E Hotfoot SBC. We've been maintaining this out-of-tree for some time now for older kernels, but recently I ported it to the new unified powerpc tree with the intent of pushing it upstream. The board uses an ancient version of u-boot and

Re: Subject: [PATCH v8] spi: Add PPC4xx SPI driver

On Friday 26 June 2009, Steven A. Falco wrote: + +   /* +    * If there are no chip selects at all, or if this is the special +    * case of a non-existent (dummy) chip select, do nothing. +    */ + +   if (!hw-master-num_chipselect || hw-gpios[cs] == -EEXIST) + 

[no subject]

From: Ashish Kalra ashish.ka...@freescale.com Date: Fri, 26 Jun 2009 15:46:02 +0530 Subject: [PATCH][v2] sata_fsl: Add asynchronous notification support Enable device hot-plug support on Port multiplier fan-out ports Signed-off-by: Ashish Kalra ashish.ka...@freescale.com --- drivers/ata

Re: Subject: [PATCH v7] spi: Add PPC4xx SPI driver

David Brownell wrote: On Thursday 25 June 2009, Steven A. Falco wrote: + if (spi-mode ~MODEBITS) { + dev_dbg(spi-dev, setup: unsupported mode bits %x\n, + spi-mode ~MODEBITS); + return -EINVAL; + } This wasn't tested against

Subject: [PATCH v8] spi: Add PPC4xx SPI driver

This adds a SPI driver for the SPI controller found in the IBM/AMCC 4xx PowerPC's. Signed-off-by: Stefan Roese s...@denx.de Signed-off-by: Wolfgang Ocker w...@reccoware.de Acked-by: Josh Boyer jwbo...@linux.vnet.ibm.com Signed-off-by: Steven A. Falco sfa...@harris.com --- Changes in v8: - Removed

Re: Subject: [PATCH v6] spi: Add PPC4xx SPI driver

Stefan suggested that I try to address the comments against the PPC4xx SPI driver, so here goes... A post of version 7 of the driver will follow this email, but I thought it might make it easier on everyone to inline my comments here. Hence, this brief, introductory top post. On Thursday 08

Subject: [PATCH v7] spi: Add PPC4xx SPI driver

This adds a SPI driver for the SPI controller found in the IBM/AMCC 4xx PowerPC's. Signed-off-by: Stefan Roese s...@denx.de Signed-off-by: Wolfgang Ocker w...@reccoware.de Acked-by: Josh Boyer jwbo...@linux.vnet.ibm.com Signed-off-by: Steven A. Falco sfa...@harris.com --- Note, I have not removed

Re: Subject: [PATCH v7] spi: Add PPC4xx SPI driver

On Thursday 25 June 2009, Steven A. Falco wrote: +   if (spi-mode ~MODEBITS) { +   dev_dbg(spi-dev, setup: unsupported mode bits %x\n, +   spi-mode ~MODEBITS); +   return -EINVAL; +   } This wasn't tested against 2.6.30-rc1 was it? See

  1   2   >