From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: LEON SPARC git repository
Date: Sat, 06 Jun 2009 07:11:16 +0000 [thread overview]
Message-ID: <20090606071116.GA25951@uranus.ravnborg.org> (raw)
In-Reply-To: <4A27926C.5010501@gaisler.com>
On Fri, Jun 05, 2009 at 11:57:48AM +0200, Konrad Eisele wrote:
> Hi Sam,
> Thanks for the clarification, I'll send the divided patches next week.
A few other things you can do to ease review/integration is:
1) run all patches through checkpatch (see scripts/checkpatch)
Try to address the relevant warning/errors.
It is not a prerequisite you are down to 0/0 - but
it eases review that you have addressed the obvious things
that checkpatch can warn you about.
2) Run the code through sparse.
Use "make C=2".
Again it is not a prereqisite that you are down to 0 warnings.
But at least having declaration for all functions and
variables are a must.
And fix all usages so you use NULL and not 0 for a null pointer.
One main reason to do so is that you then are not faced with
a lot of janitorial mails doing so after you have had your
code applied.
To get sparse you should clone this version of it:
http://git.kernel.org/?pÞvel/sparse/chrisl/sparse.git;a=summary
This is the most updated version atm.
Do not be shy and ask for help if you cannot dechiper the warnings.
Sam
prev parent reply other threads:[~2009-06-06 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 9:22 LEON SPARC git repository Kristoffer Glembo
2009-06-04 18:11 ` Sam Ravnborg
2009-06-05 8:39 ` Konrad Eisele
2009-06-05 9:19 ` Sam Ravnborg
2009-06-05 9:40 ` Konrad Eisele
2009-06-05 9:55 ` Sam Ravnborg
2009-06-05 9:57 ` Konrad Eisele
2009-06-06 7:11 ` 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=20090606071116.GA25951@uranus.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.