From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] MIPS: octeon: Add __raw_copy_[from|to|in]_user symbols
Date: Fri, 9 Apr 2021 11:44:55 +0200 [thread overview]
Message-ID: <20210409094455.GA8810@alpha.franken.de> (raw)
In-Reply-To: <1fa6ff61-25af-7d24-2d03-de03ec73e8f6@gmail.com>
On Fri, Apr 09, 2021 at 11:42:46AM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 09.04.2021 0:48, Thomas Bogendoerfer wrote:
>
> > Cavium Octeon has it's own memcpy implementation and also need the change
>
> Its. :-)
applied (with typo fixed) to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-04-09 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 21:48 [PATCH] MIPS: octeon: Add __raw_copy_[from|to|in]_user symbols Thomas Bogendoerfer
2021-04-09 8:42 ` Sergei Shtylyov
2021-04-09 9:44 ` Thomas Bogendoerfer [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=20210409094455.GA8810@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sergei.shtylyov@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