ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Andrey Abramov <st5pub@yandex.ru>, vgupta <vgupta@synopsys.com>,
	benh <benh@kernel.crashing.org>, paulus <paulus@samba.org>,
	tglx <tglx@linutronix.de>, mingo <mingo@redhat.com>,
	bp <bp@alien8.de>, hpa <hpa@zytor.com>, x86 <x86@kernel.org>,
	mark <mark@fasheh.com>, jlbec <jlbec@evilplan.org>,
	richard <richard@nod.at>, dedekind1 <dedekind1@gmail.com>,
	"adrian.hunter" <adrian.hunter@intel.com>,
	gregkh <gregkh@linuxfoundation.org>,
	"naveen.n.rao" <naveen.n.rao@linux.vnet.ibm.com>,
	jpoimboe <jpoimboe@redhat.com>,
	Dave Chinner <dchinner@redhat.com>,
	"darrick.wong" <darrick.wong@oracle.com>,
	"ard.biesheuvel" <ard.biesheuvel@linaro.org>,
	George Spelvin <lkml@sdf.org>,
	linux-snps-arc <linux-snps-arc@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	ocfs2-devel <ocfs2-devel@oss.oracle.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	sfr <sfr@canb.auug.org.au>
Cc: malat <malat@debian.org>,
	"yamada.masahiro" <yamada.masahiro@socionext.com>,
	npiggin <npiggin@gmail.com>
Subject: [Ocfs2-devel] [PATCH v3 2/5] powerpc: module_[32|64].c: replace swap function with built-in one
Date: Tue,  9 Jun 2020 15:58:30 +1000 (AEST)	[thread overview]
Message-ID: <49gzvB1bJMz9sSy@ozlabs.org> (raw)
In-Reply-To: <994931554238042@iva8-b333b7f98ab0.qloud-c.yandex.net>

On Tue, 2019-04-02 at 20:47:22 UTC, Andrey Abramov wrote:
> Replace relaswap with built-in one, because relaswap
> does a simple byte to byte swap.
> 
> Since Spectre mitigations have made indirect function calls more
> expensive, and the default simple byte copies swap is implemented
> without them, an "optimized" custom swap function is now
> a waste of time as well as code.
> 
> Signed-off-by: Andrey Abramov <st5pub@yandex.ru>
> Reviewed by: George Spelvin <lkml@sdf.org>
> Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)

Applied to powerpc next, thanks.

https://urldefense.com/v3/__https://git.kernel.org/powerpc/c/bac7ca7b985b72873bd4ac2553b13b5af5b1f08a__;!!GqivPVa7Brio!LocsSQ-zlIql0GWmmMG2Ry4W0wSo1gzfh36_pvi7Zc-ccRgumoV9gaJm3n89_0RPl8Z-mQ$ 

cheers

           reply	other threads:[~2020-06-09  5:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <994931554238042@iva8-b333b7f98ab0.qloud-c.yandex.net>]

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=49gzvB1bJMz9sSy@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=adrian.hunter@intel.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=benh@kernel.crashing.org \
    --cc=bp@alien8.de \
    --cc=darrick.wong@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=dedekind1@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jlbec@evilplan.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkml@sdf.org \
    --cc=malat@debian.org \
    --cc=mark@fasheh.com \
    --cc=mingo@redhat.com \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=paulus@samba.org \
    --cc=richard@nod.at \
    --cc=sfr@canb.auug.org.au \
    --cc=st5pub@yandex.ru \
    --cc=tglx@linutronix.de \
    --cc=vgupta@synopsys.com \
    --cc=x86@kernel.org \
    --cc=yamada.masahiro@socionext.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).