All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/12] sparc: diverse cleanup patches
Date: Fri, 02 May 2014 15:09:52 +0000	[thread overview]
Message-ID: <20140502150952.GA17048@ravnborg.org> (raw)
In-Reply-To: <20140502145859.GA5042@ravnborg.org>

On Fri, May 02, 2014 at 04:59:00PM +0200, Sam Ravnborg wrote:
> After the introduction of the generic io.h for sparc32 there was
> some cleanup left to do to trim io_32.h further.
> sparc64 cannot use the generic version because there are
> so many dedicated functions for little/big endian.
> 
> The quest to get rid of sparse warnings for sparc32 continues,
> and what is left is a bunch of "shift too big" in the
> soft floating point code that I do not plan to address.
> With sparc32 mostly clean start to fix the sparc64 sparse warnings.
> 
> Two patches touches the inline asm statements. They need extra review
> as I do not know what I am doing here..
> 
> tadpole.c got dropped - the code in this file had not been in use for
> more than 5 years.
> 
> The biggest change in terms of lines changed are the patches that drops
> the use of extern for prototypes in all the sparc specific header files.

Hi David.

I only now realized that the first patch was included in the previous
set - so please ignore the patch [01/12] which do a cleanup of io_32.h.
Sorry for this confusion.

If I get inspired next step is to try to get sparc64 down to same low
level of sparse warnings as we now have for sparc32.
As you already did a lot of work this looks quite do-able.

	Sam

  reply	other threads:[~2014-05-02 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 14:59 [PATCH 0/12] sparc: diverse cleanup patches Sam Ravnborg
2014-05-02 15:09 ` Sam Ravnborg [this message]
2014-05-03 17:21 ` Sam Ravnborg
2014-05-03 19:46 ` David Miller

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=20140502150952.GA17048@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.