mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Michal Simek <michal.simek@xilinx.com>,
	<linux-kernel@vger.kernel.org>, <monstr@monstr.eu>,
	<git@xilinx.com>
Cc: Mahesh Bodapati <mbodapat@xilinx.com>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 0/1] microblaze: Fix issues with freestanding
Date: Fri, 25 Feb 2022 14:56:10 +0100	[thread overview]
Message-ID: <ce6cf9f3-0543-c9af-b5cf-bf166c974ad7@xilinx.com> (raw)
In-Reply-To: <cover.1645797022.git.michal.simek@xilinx.com>



On 2/25/22 14:50, Michal Simek wrote:
> Hi,
> 
> with GCC 10 there is issue with simple memset implementation which is
> called recursively. There are couple of discussions about it and the first
> two patches are trying to workaround this.
> The third patch only removes simple implementations from arch code and use
> generic one which is the same.
> 
> Thanks,
> Michal
> 
> 
> Michal Simek (1):
>    microblaze: Use simple memmove/memcpy implementation from lib/string.c
> 
>   arch/microblaze/include/asm/string.h |  2 +-
>   arch/microblaze/lib/memcpy.c         | 18 ++---------------
>   arch/microblaze/lib/memmove.c        | 29 ++--------------------------
>   3 files changed, 5 insertions(+), 44 deletions(-)
> 

I didn't send all 3 patches. Sorry about it. V2 has all required changes.

Thanks,
Michal

      parent reply	other threads:[~2022-02-25 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 13:50 Michal Simek
2022-02-25 13:50 ` [PATCH 1/1] microblaze: Use simple memmove/memcpy implementation from lib/string.c Michal Simek
2022-02-25 13:56 ` Michal Simek [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=ce6cf9f3-0543-c9af-b5cf-bf166c974ad7@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=git@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbodapat@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=rdunlap@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

all inboxes | Powered by JetHome®