public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux•org.uk>
To: "Guilherme G. Piccoli" <gpiccoli@igalia•com>
Cc: linux-arm-kernel@lists•infradead.org,
	Marc Zyngier <maz@kernel•org>,
	will@kernel•org, Mark Rutland <mark.rutland@arm•com>,
	arnd@arndb•de, Catalin Marinas <catalin.marinas@arm•com>,
	kexec@lists•infradead.org, pmladek@suse•com, bhe@redhat•com,
	akpm@linux-foundation•org, linux-kernel@vger•kernel.org,
	linux-hyperv@vger•kernel.org, netdev@vger•kernel.org,
	x86@kernel•org, kernel-dev@igalia•com, kernel@gpiccoli•net,
	halves@canonical•com, fabiomirmar@gmail•com,
	alejandro.j.jimenez@oracle•com,
	andriy.shevchenko@linux•intel.com, bp@alien8•de, corbet@lwn•net,
	d.hatayama@jp•fujitsu.com, dave.hansen@linux•intel.com,
	dyoung@redhat•com, feng.tang@intel•com,
	gregkh@linuxfoundation•org, mikelley@microsoft•com,
	hidehiro.kawai.ez@hitachi•com, jgross@suse•com,
	john.ogness@linutronix•de, keescook@chromium•org,
	luto@kernel•org, mhiramat@kernel•org, mingo@redhat•com,
	paulmck@kernel•org, peterz@infradead•org, rostedt@goodmis•org,
	senozhatsky@chromium•org, stern@rowland•harvard.edu,
	tglx@linutronix•de, vgoyal@redhat•com, vkuznets@redhat•com,
	xuqiang36@huawei•com
Subject: Re: [PATCH V3 01/11] ARM: Disable FIQs (but not IRQs) on CPUs shutdown paths
Date: Mon, 17 Oct 2022 18:47:06 +0100	[thread overview]
Message-ID: <Y02VGh+eDLMyi/Aj@shell.armlinux.org.uk> (raw)
In-Reply-To: <aea7dad7-987d-43ad-3abc-815ede97a127@igalia.com>

On Mon, Oct 17, 2022 at 11:50:05AM -0300, Guilherme G. Piccoli wrote:
> On 17/10/2022 11:17, Russell King (Oracle) wrote:
> > [...]
> >> Monthly ping - let me know if there's something I should improve in
> >> order this fix is considered!
> > 
> > Patches don't get applied unless they end up in the patch system.
> > Thanks.
> > 
> 
> Thanks Russell! Can you show me some documentation on how should I send
> the patches to this patch system? My understanding based in the
> MAINTAINERS file is that we should send the arm32 patches to you + arm ML.

Look below in my signature --.
                             |
			     v
-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2022-10-17 17:47 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 22:17 [PATCH V3 00/11] The panic notifiers refactor - fixes/clean-ups (V3) Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 01/11] ARM: Disable FIQs (but not IRQs) on CPUs shutdown paths Guilherme G. Piccoli
2022-09-18 13:58   ` Guilherme G. Piccoli
2022-10-17 14:00     ` Guilherme G. Piccoli
2022-10-17 14:17       ` Russell King (Oracle)
2022-10-17 14:50         ` Guilherme G. Piccoli
2022-10-17 17:47           ` Russell King (Oracle) [this message]
2022-10-17 19:43             ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 02/11] notifier: Add panic notifiers info and purge trailing whitespaces Guilherme G. Piccoli
2022-11-22 13:19   ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 03/11] alpha: Clean-up the panic notifier code Guilherme G. Piccoli
2022-11-22 13:22   ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 04/11] um: Improve panic notifiers consistency and ordering Guilherme G. Piccoli
2022-09-18 14:00   ` Guilherme G. Piccoli
2022-09-18 21:19     ` Richard Weinberger
2022-09-19 11:44       ` Guilherme G. Piccoli
2022-10-17 14:01       ` Guilherme G. Piccoli
2022-10-17 14:10         ` Richard Weinberger
2022-10-17 14:22           ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 05/11] parisc: Replace regular spinlock with spin_trylock on panic path Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 06/11] tracing: Improve panic/die notifiers Guilherme G. Piccoli
2022-09-18 14:04   ` Guilherme G. Piccoli
2022-10-17 14:02   ` Guilherme G. Piccoli
2022-10-20 21:29   ` Steven Rostedt
2022-10-20 21:53     ` Guilherme G. Piccoli
2022-10-20 22:22       ` Steven Rostedt
2022-10-20 22:37         ` Guilherme G. Piccoli
2022-11-22 13:27         ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 07/11] notifiers: Add tracepoints to the notifiers infrastructure Guilherme G. Piccoli
2022-09-18 14:07   ` Guilherme G. Piccoli
2022-10-17 14:04   ` Guilherme G. Piccoli
2022-11-22 13:30   ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 08/11] EDAC/altera: Skip the panic notifier if kdump is loaded Guilherme G. Piccoli
2022-09-18 14:10   ` Guilherme G. Piccoli
2022-10-17 14:05     ` Guilherme G. Piccoli
2022-11-22 13:33     ` Guilherme G. Piccoli
2022-11-22 15:06       ` Borislav Petkov
2023-02-10 16:01         ` Guilherme G. Piccoli
2022-12-09 16:03   ` Petr Mladek
2022-08-19 22:17 ` [PATCH V3 09/11] video/hyperv_fb: Avoid taking busy spinlock on panic path Guilherme G. Piccoli
2022-09-18 14:12   ` Guilherme G. Piccoli
2022-10-04 16:17   ` Michael Kelley (LINUX)
2022-08-19 22:17 ` [PATCH V3 10/11] drivers/hv/vmbus, video/hyperv_fb: Untangle and refactor Hyper-V panic notifiers Guilherme G. Piccoli
2022-10-04 16:24   ` Michael Kelley (LINUX)
2022-10-04 17:20     ` Guilherme G. Piccoli
2022-10-17 15:26       ` Michael Kelley (LINUX)
2022-11-10 21:32         ` Guilherme G. Piccoli
2022-11-11 22:47           ` Wei Liu
2022-11-11 23:16             ` Wei Liu
2022-11-12 21:53               ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 11/11] panic: Fixes the panic_print NMI backtrace setting Guilherme G. Piccoli
2022-09-18 14:13   ` Guilherme G. Piccoli
2022-11-22 13:35   ` Guilherme G. Piccoli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y02VGh+eDLMyi/Aj@shell.armlinux.org.uk \
    --to=linux@armlinux$(echo .)org.uk \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=alejandro.j.jimenez@oracle$(echo .)com \
    --cc=andriy.shevchenko@linux$(echo .)intel.com \
    --cc=arnd@arndb$(echo .)de \
    --cc=bhe@redhat$(echo .)com \
    --cc=bp@alien8$(echo .)de \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=corbet@lwn$(echo .)net \
    --cc=d.hatayama@jp$(echo .)fujitsu.com \
    --cc=dave.hansen@linux$(echo .)intel.com \
    --cc=dyoung@redhat$(echo .)com \
    --cc=fabiomirmar@gmail$(echo .)com \
    --cc=feng.tang@intel$(echo .)com \
    --cc=gpiccoli@igalia$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=halves@canonical$(echo .)com \
    --cc=hidehiro.kawai.ez@hitachi$(echo .)com \
    --cc=jgross@suse$(echo .)com \
    --cc=john.ogness@linutronix$(echo .)de \
    --cc=keescook@chromium$(echo .)org \
    --cc=kernel-dev@igalia$(echo .)com \
    --cc=kernel@gpiccoli$(echo .)net \
    --cc=kexec@lists$(echo .)infradead.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-hyperv@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=luto@kernel$(echo .)org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=maz@kernel$(echo .)org \
    --cc=mhiramat@kernel$(echo .)org \
    --cc=mikelley@microsoft$(echo .)com \
    --cc=mingo@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=paulmck@kernel$(echo .)org \
    --cc=peterz@infradead$(echo .)org \
    --cc=pmladek@suse$(echo .)com \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=senozhatsky@chromium$(echo .)org \
    --cc=stern@rowland$(echo .)harvard.edu \
    --cc=tglx@linutronix$(echo .)de \
    --cc=vgoyal@redhat$(echo .)com \
    --cc=vkuznets@redhat$(echo .)com \
    --cc=will@kernel$(echo .)org \
    --cc=x86@kernel$(echo .)org \
    --cc=xuqiang36@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox