From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: SF Markus Elfring <elfring@users•sourceforge.net>,
linuxppc-dev@lists•ozlabs.org,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Borislav Petkov <bp@suse•de>,
Brijesh Singh <brijesh.singh@amd•com>,
Josh Sklar <sklar@linux•vnet.ibm.com>,
Kees Cook <keescook@chromium•org>,
Paul Mackerras <paulus@samba•org>,
Thiago Jung Bauermann <bauerman@linux•vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix•de>,
Tom Lendacky <thomas.lendacky@amd•com>
Cc: kernel-janitors@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: powerpc: Use common error handling code in setup_new_fdt()
Date: Mon, 13 Aug 2018 21:22:52 +1000 (AEST) [thread overview]
Message-ID: <41ptcs19GYz9s7c@ozlabs.org> (raw)
In-Reply-To: <0dd9d938-8d89-f0e0-f05f-9a3e5dc42a57@users.sourceforge.net>
On Sun, 2018-03-11 at 08:16:47 UTC, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users•sourceforge.net>
> Date: Sun, 11 Mar 2018 09:03:42 +0100
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users•sourceforge.net>
> Reviewed-by: Thiago Jung Bauermann <bauerman@linux•vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/baedcdf5054c151a33e34392af7d8c
cheers
prev parent reply other threads:[~2018-08-13 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 8:16 [PATCH] powerpc: Use common error handling code in setup_new_fdt() SF Markus Elfring
2018-03-14 21:22 ` Thiago Jung Bauermann
2018-03-15 11:57 ` Dan Carpenter
2018-03-15 15:03 ` Joe Perches
2018-03-15 18:34 ` Thiago Jung Bauermann
2018-03-16 10:29 ` Michael Ellerman
2018-03-16 10:26 ` Michael Ellerman
2018-03-16 10:35 ` Dan Carpenter
2018-08-13 11:22 ` Michael Ellerman [this message]
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=41ptcs19GYz9s7c@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=bauerman@linux$(echo .)vnet.ibm.com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=bp@suse$(echo .)de \
--cc=brijesh.singh@amd$(echo .)com \
--cc=elfring@users$(echo .)sourceforge.net \
--cc=keescook@chromium$(echo .)org \
--cc=kernel-janitors@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=sklar@linux$(echo .)vnet.ibm.com \
--cc=tglx@linutronix$(echo .)de \
--cc=thomas.lendacky@amd$(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