x/linux-picochip-3.0/0001-picoxcell-support-for-Picochip-picoXcell-SoC.patch
>
> Signed-off-by: Arnd Bergmann
Acked-by: Jamie Iles
Thanks Arnd!
Jamie
Hi Arnd,
On Wed, Dec 30, 2020 at 04:20:05PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> dtc points out that the interrupts for some devices are not parsable:
>
> picoxcell-pc3x2.dtsi:45.19-49.5: Warning (interrupts_property):
> /paxi/gem@3: Missing interrupt-parent
> picoxcell-pc
Acked-by: Jamie Iles
for the series. Intel EOLd this product now, good idea to remove it.
Thanks,
Jamie
On Thu, Dec 10, 2020 at 02:03:11PM -0600, Rob Herring wrote:
> PicoXcell has had nothing but treewide cleanups for at least the last 8
> years and no signs of activity. The most
by the end of the series.
>
> This series is a little rough around the monitors, would a fake
> struct resctrl_schema for the monitors simplify things, or be a source
> of bugs?
>
> This series is based on v5.10-rc1, and can be retrieved from:
> git://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git
> mpam/resctrl_merge_cdp/v1
>
> Parts were previously posted as an RFC here:
> https://lore.kernel.org/lkml/20200214182947.39194-1-james.mo...@arm.com/
Reviewed-by: Jamie Iles
Jamie
Hi James,
On Fri, Oct 30, 2020 at 04:11:06PM +, James Morse wrote:
> Move the names used for the schemata file out of the resource and
> into struct resctrl_schema. This allows one resource to have two
> different names, based on the other schema properties.
>
> This patch copies the names, e
aml: gpio@2:
> 'reg-io-width' does not match any of the regexes:
> '^gpio-(port|controller)@[0-9a-f]+$', 'pinctrl-[0-9]+'
>
> Signed-off-by: Krzysztof Kozlowski
Acked-by: Jamie Iles
Thanks!
ich updates engine->stat_irq_thresh,
> therefore initialize it before creating the file in probe function.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Madhuparna Bhowmik
Acked-by: Jamie Iles
Thanks!
rification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov
Reviewed-by: Jamie Iles
On Mon, Nov 06, 2017 at 12:56:09PM +0100, Dmitry Vyukov wrote:
> On Mon, Nov 6, 2017 at 12:25 PM, Jamie Iles wrote:
> > Hi Dmitry,
> >
> > On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote:
> >> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote:
> &
Hi Dmitry,
On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote:
> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote:
> > On 11/01, Dmitry Vyukov wrote:
> >>
> >> On Tue, Oct 31, 2017 at 7:34 PM, Oleg Nesterov wrote:
> >> > Hmm. I do not see reproducer in this email...
> >>
> >> Ah, s
Cc: Jesper Nilsson
> Cc: Lars Persson
> Cc: Niklas Cassel
> Cc: "David S. Miller"
> Cc: Jamie Iles
> Cc: linux-arm-ker...@axis.com
> Cc: linux-cry...@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org
> Signed-off-by: Kees Cook
> ---
Acked-by: Jamie Iles
Thanks,
Jamie
Hi Linus,
On Tue, Sep 12, 2017 at 11:47:52AM +0200, Linus Walleij wrote:
> Jamie, do you consider yourself maintainer? If not
> would someone else using this driver please step up?
I don't think I'm best suited to the job - I don't actually have access
to the docs for this IP block any more so c
fine, but then once debugging has finished, the
init process is left killable which is unlikely what the user expects,
resulting in either an accidentally killed init or an init that stops
reaping zombies.
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
---
kernel/signal.c | 6
Hi Oleg,
On Thu, Apr 27, 2017 at 01:16:51PM +0100, Jamie Iles wrote:
> On Wed, Apr 26, 2017 at 05:18:58PM +0200, Oleg Nesterov wrote:
> > Hi Jamie,
> >
> > On 04/25, Jamie Iles wrote:
> > >
> > > Hi Oleg,
> > >
> > > I'm back
can remove this "clear
> SIGNAL_UNKILLABLE" logic in force_sig_info() altogether.
I was wondering if you had given this any more thought?
Thanks,
Jamie
> On 05/04, Jamie Iles wrote:
> >
> > When forcing a signal, SIGNAL_UNKILLABLE is removed to prevent recursive
>
Hi Oleg,
On Fri, May 05, 2017 at 06:26:07PM +0200, Oleg Nesterov wrote:
> I am sorry for being slow... yes, probably we should start with this
> simple change, and perhaps we do not really need anything else. But
> let me think about this till Monday, perhaps we can remove this "clear
> SIGNAL_UNK
fine, but then once debugging has finished, the
init process is left killable which is unlikely what the user expects,
resulting in either an accidentally killed init or an init that stops
reaping zombies.
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
---
kernel/signal.c | 6
On Wed, Apr 26, 2017 at 05:18:58PM +0200, Oleg Nesterov wrote:
> Hi Jamie,
>
> On 04/25, Jamie Iles wrote:
> >
> > Hi Oleg,
> >
> > I'm back looking at SIGNAL_UNKILLABLE and debugging child reapers again,
> > and the current issue is when running cod
Hi Oleg,
I'm back looking at SIGNAL_UNKILLABLE and debugging child reapers again,
and the current issue is when running code in the target process,
SIGTRAP firing and that causing SIGNAL_UNKILLABLE protection to be
removed in force_sig_info():
if (action->sa.sa_handler == SIG_DFL)
egister addresses.
>
> Signed-off-by: Hoan Tran
Reviewed-by: Jamie Iles
Hi Hoan,
On Tue, Feb 14, 2017 at 05:22:09PM -0800, Hoan Tran wrote:
> Hi Linus, Jamie and all,
>
> Do you have any comments on this patch?
I think that the CONFIG_ACPI ifdef can be removed to clean it up -
acpi_match_device() returns NULL for !CONFIG_ACPI.
Other than that, looks good to me.
J
; > This patch modifies DW GPIO driver to accommodate the difference
> > in a few register addresses.
> >
> > Signed-off-by: Hoan Tran
>
> On next iteration please include Jamie Iles, Weike Chen and Sebastian
> Andrzej Siewior.
> They all provided substantial
crypto: picoxcell - Remove spacc_is_compatible() wrapper function
>
> drivers/crypto/Kconfig| 2 +-
> drivers/crypto/picoxcell_crypto.c | 28 +++-
> 2 files changed, 4 insertions(+), 26 deletions(-)
Acked-by: Jamie Iles
Thanks,
Jamie
pond to future SIGSTOP signals rather than ignoring
them.
Make sure that when setting SIGNAL_STOP_CONTINUED/SIGNAL_STOP_STOPPED
that we don't clear SIGNAL_UNKILLABLE.
Cc: Alexander Viro
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
--
Hi Oleg,
On Tue, Nov 29, 2016 at 03:06:00PM +0100, Oleg Nesterov wrote:
> Jamie,
>
> I am really sorry for the huge delay.
No problem!
> On 11/16, Jamie Iles wrote:
> >
> > Since 00cd5c37af (ptrace: permit ptracing of /sbin/init) we can now
> > trace init
Hi Oleg,
On Thu, Nov 17, 2016 at 08:04:20PM +0100, Oleg Nesterov wrote:
> On 11/16, Jamie Iles wrote:
> >
> > This can result in init becoming stoppable/killable after tracing. For
> > example, running:
> >
> > while true; do kill -STOP 1; done &
>
pond to future SIGSTOP signals rather than ignoring
them.
Instead of direct assignment to struct signal_struct::flags, provide
accessors that protect SIGNAL_UNKILLABLE.
Cc: Alexander Viro
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
---
orentin
Acked-by: Jamie Iles
thanks for doing this!
Jamie
--
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 FAQ at http://www.tux.org/lkml/
6:3: warning: ‘relocs_size’ may be used uninitialized
> in this function [-Wmaybe-uninitialized]
>memset(relocs, 0, relocs_size);
>^
> scripts/sortextable.h:106:6: note: ‘relocs_size’ was declared here
> int relocs_size;
> ^
>
> gcc 4.9.1
>
> Cc: Andrew
Thanks Joe!
On Thu, Jul 03, 2014 at 03:07:52PM -0700, Joe Perches wrote:
> Fix the picoxcell patterns, add the dts directory too.
>
> Signed-off-by: Joe Perches
> cc: Jamie Iles
Acked-by: Jamie Iles
Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
ntime two users
> where one is using edge and the other level.
>
> Acked-by: Alan Tull
> Signed-off-by: Sebastian Andrzej Siewior
Acked-by: Jamie Iles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
> tree. This means this driver has never been buildable. Let's remove it.
> It can be re-added if its dependencies are actually part of the tree.
>
> Signed-off-by: Paul Bolle
I wish I had the bandwidth to get this properly supported, but this
seems sensible to me.
Acked-b
On Tue, Mar 25, 2014 at 09:37:50PM +0100, Linus Walleij wrote:
> Aha Jamie not even on the original thread. Here.
>
> On Tue, Mar 25, 2014 at 9:37 PM, Linus Walleij
> wrote:
> > On Thu, Mar 20, 2014 at 8:55 PM, Sebastian Andrzej Siewior
> > wrote:
> >
> >> This looks kinda wrong I didn't manage
Hi Alan,
One minor comment below, otherwise looks great!
Signed-off-by: Jamie Iles
Thanks,
Jamie
On Tue, Dec 03, 2013 at 10:41:16AM -0600, Alan Tull wrote:
> diff --git a/drivers/gpio/gpio-dwapb.c b/drivers/gpio/gpio-dwapb.c
> new file mode 100644
> index 000..e6dc61f
> -
Hi Alan,
On Wed, Nov 06, 2013 at 04:49:42PM -0600, Alan Tull wrote:
> diff --git a/drivers/gpio/gpio-dwapb.c b/drivers/gpio/gpio-dwapb.c
> new file mode 100644
> index 000..7957dfd
> --- /dev/null
> +++ b/drivers/gpio/gpio-dwapb.c
> @@ -0,0 +1,458 @@
> +/*
> + * Copyr
fall back to the perl version.
Based on 48bb5dc6cd9d30fe0d594947563da1f8bd9abada (ftrace: Make
recordmcount.c handle __fentry__).
Cc: Steven Rostedt
Signed-off-by: Jamie Iles
---
v2: describe the problem for Ksplice and include a hunk for x86_64 where the
regex is overridden.
scripts/recordmcou
On Thu, Oct 31, 2013 at 12:09:26PM -0400, Steven Rostedt wrote:
> On Thu, 31 Oct 2013 15:59:58 +
> Jamie Iles wrote:
>
> > With gcc 4.6.0 the -mfentry feature places the function profiling call
> > at the start of the function. When this is used, the call is to
> >
: Jamie Iles
---
scripts/recordmcount.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
index a674fd5..6460fc68 100755
--- a/scripts/recordmcount.pl
+++ b/scripts/recordmcount.pl
@@ -214,7 +214,7 @@ $local_regex = "^[0-9a
Building with a large config and -ffunction-sections results in a large
number of sections and sortextable needs to be able to handle that.
Implement support for > 64K sections as modpost does.
Cc: Rusty Russell
Signed-off-by: Jamie Iles
---
scripts/sortextable.c |
s inclomplete serial support.
>
> Then we just make minor patches to 8250_dw, and rip out all this
> OCTEON code.
>
> Since the patches are all interdependent, we might want to merge them
> via a single tree (perhaps Ralf's MIPS tree).
Looks good!
Reviewed-by: Jamie Iles
for
ee93dc67da0b77e09776de2,
> 60d4616f3dc63371b3dc367e5e88fd4b4f037f65 and (most importantly)
> dee1f973ca341c266229faa5a1a5bb268bed3531 by Dmitry Monakhov
> . They were backported into the RHEL 6 kernel by
> Lukas Czerner, according to its changelog. Dann got this version from
> Oracle
"picochip,pc3x2-timer",
> dw_apb_timer_init);
> +CLOCKSOURCE_OF_DECLARE(apb_timer, "snps,dw-apb-timer-osc",
> dw_apb_timer_init);
I think maybe we also want CLOCKSOURCE_OF_DECLARE() instances for the
contents of sptimer_ids for completeness, otherwise looks good.
Ac
> The clock-frequency property is kept to act as fallback if no clocks
> are specified.
>
> Signed-off-by: Heiko Stuebner
Acked-by: Jamie Iles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kerne
source as sched_clock instead.
>
> Therefore enable the driver to distiguish between devices with and without
> sptimer based on the devicetree data and select the correct timer as
> sched_clock.
>
> Signed-off-by: Heiko Stuebner
Acked-by: Jamie Iles
--
To unsubscribe from this list:
the core timer and the dt addon.
>
> As dw_apb_timer_of always depends on dw_apb_timer let it select
> DW_APB_TIMER itself without the need for every platform to do it.
>
> Signed-off-by: Heiko Stuebner
Acked-by: Jamie Iles
--
To unsubscribe from this list: send the line "un
ultz
> Cc: Thomas Gleixner
> Cc: Jamie Iles
Acked-by: Jamie Iles
--
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 FAQ at http://www.tux.org/lkml/
On Thu, May 16, 2013 at 10:19:56AM +0200, Maxime Ripard wrote:
> Hi Jamie,
>
> Le 14/05/2013 18:20, Jamie Iles a écrit :
> > Hi Maxime,
> >
> > Thanks for this, I'll add it to my tree. I've modified it slightly to
> > kill off the other irq includes,
only irqchip_init. Remove that
declaration for picoxcell as well.
[ jiles: removed other, unused irq includes. ]
Signed-off-by: Maxime Ripard
Signed-off-by: Jamie Iles
---
arch/arm/mach-picoxcell/common.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/arch/arm/mach-picoxcell/com
t exists on both
> platforms, and adds missing of_node_put() in dw_apb_timer_init().
>
> Signed-off-by: Pavel Machek
Acked-by: Jamie Iles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Hi Thomas,
On Thu, Apr 25, 2013 at 08:31:43PM -, Thomas Gleixner wrote:
> Signed-off-by: Thomas Gleixner
> Cc: Jamie Iles
Looks good, thanks for fixing this.
Acked-by: Jamie Iles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
Hi Pavel,
On Fri, Apr 26, 2013 at 02:14:34PM +0200, Pavel Machek wrote:
> diff --git a/arch/arm/mach-picoxcell/common.c
> b/arch/arm/mach-picoxcell/common.c
> index 70b441a..22759f5 100644
> --- a/arch/arm/mach-picoxcell/common.c
> +++ b/arch/arm/mach-picoxcell/common.c
> @@ -84,11 +84,39 @@ stat
On Thu, Mar 28, 2013 at 09:46:45PM +0100, Maxime Ripard wrote:
> Now that the arm core code calls irqchip_init, we can remove it from all
> the machines that were using it.
>
> Signed-off-by: Maxime Ripard
> Acked-by: Simon Horman
Acked-by: Jamie Iles
Thanks Maxime!
--
To u
On Thu, Feb 07, 2013 at 09:31:22AM -0500, Sasha Levin wrote:
> On 02/07/2013 05:28 AM, Jamie Iles wrote:
> >> +int pthread_rwlock_init(pthread_rwlock_t *rwlock,
> >> > +const pthread_rwlockattr_t *attr)
> >> > +{
> >>
Hi Sasha,
On Wed, Feb 06, 2013 at 05:11:32PM -0500, Sasha Levin wrote:
> This allows lockdep to be used without being compiled in the original program.
>
> Usage is quite simple:
>
> LD_PRELOAD=/path/to/liblockdep.so /path/to/my/program
>
> And magically, you'll have lockdep in your progr
On Mon, Nov 05, 2012 at 09:06:44AM +, Jamie Iles wrote:
> Building with a large config and -ffunction-sections results in a large
> number of sections and sortextable needs to be able to handle that.
> Implement support for > 64K sections as modpost does.
>
> Cc: David Dan
Looks good to me!
On Tue, Dec 04, 2012 at 05:21:52PM +0200, Heikki Krogerus wrote:
> This needs to be done in order to later access the
> Designware specific registers.
>
> Signed-off-by: Heikki Krogerus
Reviewed-by: Jamie Iles
--
To unsubscribe from this list: send the line
able to
> deliver their UART's capabilities when they are registering ports.
Other than my comment on 3/5 it looks great.
Reviewed-by: Jamie Iles
Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vge
Hi Heikki,
On Mon, Dec 03, 2012 at 01:17:57PM +0200, Heikki Krogerus wrote:
> This needs to be done in order to later access the
> Designware specific registers.
>
> Signed-off-by: Heikki Krogerus
> ---
> drivers/tty/serial/8250/8250_dw.c |7 +--
> 1 file changed, 5 insertions(+), 2 del
Building with a large config and -ffunction-sections results in a large
number of sections and sortextable needs to be able to handle that.
Implement support for > 64K sections as modpost does.
Cc: David Daney
Cc: H. Peter Anvin
Signed-off-by: Jamie Iles
---
scripts/sortextable.c |
Hi Axel,
On Sun, Nov 04, 2012 at 11:36:25PM +0800, Axel Lin wrote:
> The platform_device_id table is supposed to be zero-terminated.
>
> Signed-off-by: Axel Lin
Good spot! Thanks for fixing.
Acked-by: Jamie Iles
Jamie
--
To unsubscribe from this list: send the line "uns
60 matches
Mail list logo
