From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Cyril Bur <cyrilbur@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: gromero@linux.vnet.ibm.com
Subject: Re: powerpc/tm: Remove struct thread_info param from tm_reclaim_thread()
Date: Tue, 24 Jul 2018 23:59:45 +1000 (AEST) [thread overview]
Message-ID: <41Zg353jZVz9s1x@ozlabs.org> (raw)
In-Reply-To: <20180201010746.413-1-cyrilbur@gmail.com>
On Thu, 2018-02-01 at 01:07:46 UTC, Cyril Bur wrote:
> tm_reclaim_thread() doesn't use the parameter anymore, both callers have
> to bother getting it as they have no need for a struct thread_info
> either.
>
> Just remove it and adjust the callers.
>
> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/edd00b830731be468fd3caf7f9154d
cheers
prev parent reply other threads:[~2018-07-24 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 1:07 [PATCH] powerpc/tm: Remove struct thread_info param from tm_reclaim_thread() Cyril Bur
2018-02-01 4:46 ` Michael Ellerman
2018-02-01 23:34 ` Cyril Bur
2018-07-24 13:59 ` 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=41Zg353jZVz9s1x@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=gromero@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).