From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 00/34] sparc sparse fixes + diverse cleanup
Date: Sun, 25 May 2014 20:44:34 +0000 [thread overview]
Message-ID: <20140525204434.GA27452@ravnborg.org> (raw)
In-Reply-To: <20140516212259.GA17389@ravnborg.org>
On Sat, May 24, 2014 at 11:41:50PM -0400, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Mon, 19 May 2014 18:55:33 +0200
>
> > On Sun, May 18, 2014 at 10:06:49PM -0400, David Miller wrote:
> >>
> >> Ok I reviewed all of this, it all looks good.
> >>
> >> Thanks a lot for doing this, all applied to sparc-next.
> > Good. And I am glad you spotted the bug in the first
> > version so we did not have that applied.
> >
> > If you find time and have any hints how to fix
> > the remaining sparse warnings in arch/sparc/
> > please let me know.
>
> Sorry Sam I've lost context.
>
> Is there a specific list you posted or should I run an sparse build
> of my own and check it out?
I posted a list of remaining sparse issues in the original cover mail.
But I think we should let them wait and maybe address then in next
round. arch/sparc already have lots of stuff pending for next
merge window.
On top of this I have a few other things that has higher priority.
I will re-post a list of open issues when I plan to look at them again.
Sam
prev parent reply other threads:[~2014-05-25 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 21:22 [PATCH v2 00/34] sparc sparse fixes + diverse cleanup Sam Ravnborg
2014-05-19 2:06 ` David Miller
2014-05-19 16:55 ` Sam Ravnborg
2014-05-25 3:41 ` David Miller
2014-05-25 20:44 ` Sam Ravnborg [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=20140525204434.GA27452@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.