From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH 1/3] powerpc/64: __ioremap_at clean up in the error case
Date: Sun, 30 Jun 2019 18:37:23 +1000 (AEST) [thread overview]
Message-ID: <45c3lm1lv3z9sN6@ozlabs.org> (raw)
In-Reply-To: <20190610030818.17965-1-npiggin@gmail.com>
On Mon, 2019-06-10 at 03:08:16 UTC, Nicholas Piggin wrote:
> __ioremap_at error handling is wonky, it requires caller to clean up
> after it. Implement a helper that does the map and error cleanup and
> remove the requirement from the caller.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/a72808a7ec5d340417a91a81e5cabdaa50650f2e
cheers
next prev parent reply other threads:[~2019-06-30 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 3:08 [PATCH 1/3] powerpc/64: __ioremap_at clean up in the error case Nicholas Piggin
2019-06-10 3:08 ` [PATCH 2/3] powerpc/64s/radix: ioremap use ioremap_page_range Nicholas Piggin
2019-06-11 6:46 ` Christophe Leroy
2019-06-19 3:59 ` Nicholas Piggin
2019-06-19 12:49 ` Christophe Leroy
2019-06-24 1:03 ` Nicholas Piggin
2019-06-19 16:25 ` Christophe Leroy
2019-06-24 3:12 ` Nicholas Piggin
2019-08-05 12:52 ` Christophe Leroy
2019-06-10 3:08 ` [PATCH 3/3] powerpc/64s/radix: Enable HAVE_ARCH_HUGE_VMAP Nicholas Piggin
2019-06-11 6:28 ` [PATCH 1/3] powerpc/64: __ioremap_at clean up in the error case Christophe Leroy
2019-06-19 4:04 ` Nicholas Piggin
2019-06-19 13:04 ` Christophe Leroy
2019-06-30 8:37 ` Michael Ellerman [this message]
2019-08-20 7:44 ` Christophe Leroy
2019-08-27 8:16 ` Nicholas Piggin
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=45c3lm1lv3z9sN6@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).