From: Mike Frysinger <vapier.adi@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Bryan Wu <cooloney@kernel.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH] checkpatch: add some common Blackfin checks
Date: Sun, 13 Sep 2009 23:41:52 -0400 [thread overview]
Message-ID: <8bd0f97a0909132041y3705ff59ja51c7065503ba519@mail.gmail.com> (raw)
In-Reply-To: <1243381049-10359-1-git-send-email-vapier@gentoo.org>
On Tue, May 26, 2009 at 19:37, Mike Frysinger wrote:
> Add checks for Blackfin-specific issues that seem to crop up from time to
> time. In particular, we have helper macros to break a 32bit address into
> the hi/lo parts, and we want to make sure people use the csync/ssync
> variant that includes fun anomaly workarounds.
Andrew: could you pick this up ?
-mike
prev parent reply other threads:[~2009-09-14 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 23:37 Mike Frysinger
2009-09-14 3:41 ` Mike Frysinger [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=8bd0f97a0909132041y3705ff59ja51c7065503ba519@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=cooloney@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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®