From: Sascha Hauer <s.hauer@pengutronix.de>
To: Herve Codina <Herve.CODINA@celad.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/4] exitcall infrastructure
Date: Mon, 6 Jul 2015 13:52:36 +0200 [thread overview]
Message-ID: <20150706115236.GR18700@pengutronix.de> (raw)
In-Reply-To: <1436168207-6433-1-git-send-email-Herve.CODINA@celad.com>
On Mon, Jul 06, 2015 at 09:36:42AM +0200, Herve Codina wrote:
> This series adds shutdown hooks mechanism.
> The mechanism chosen is based on initcall infrastructure and so the name
> given is exitcall.
> The first patch implement the exitcall infrastructure.
> The other patches move old shutdown functions to this new infrastructure.
>
> Herve Codina (4):
> exitcall: Add exitcall infrastructure
> exitcall: move device_shutdown to exitcall infrastructure
> exitcall: move arch_shutdown to exitcall infrastructure
> exitcall: move board_shutdown to exitcall infrastructure
Applied, thanks. Please watch out for trailing whitespaces next time. I
removed several while applying.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-07-06 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 7:36 Herve Codina
2015-07-06 7:36 ` [PATCH 1/4] exitcall: Add " Herve Codina
2015-07-06 7:36 ` [PATCH 2/4] exitcall: move device_shutdown to " Herve Codina
2015-07-06 7:36 ` [PATCH 3/4] exitcall: move arch_shutdown " Herve Codina
2015-07-06 7:36 ` [PATCH 4/4] exitcall: move board_shutdown " Herve Codina
2015-07-06 11:52 ` Sascha Hauer [this message]
2015-07-06 12:19 ` [PATCH 0/4] " Herve Codina
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=20150706115236.GR18700@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Herve.CODINA@celad.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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