From: Mike Frysinger <vapier.adi@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.32 -mm Blackfin patches
Date: Tue, 15 Sep 2009 23:56:21 -0400 [thread overview]
Message-ID: <8bd0f97a0909152056h61bfc487g6b8631966c6d72be@mail.gmail.com> (raw)
On Tue, Sep 15, 2009 at 19:15, Andrew Morton wrote:
> blackfin-convert-to-use-arch_gettimeoffset.patch
i thought John was merging this via some sort of patch series, but i
can pick it up in the Blackfin tree to make sure things are really
sane
> blackfin-fix-read-buffer-overflow.patch
the latter patch i merged into my tree (and i thought that i followed
up in the original posting about this)
> checkpatch-possible-types-else-cannot-start-a-type.patch
> checkpatch-handle-c99-comments-correctly-performance-issue.patch
> checkpatch-indent-checks-stop-when-we-run-out-of-continuation-lines.patch
> checkpatch-make-f-alias-file-add-help-more-verbose-help-message.patch
> checkpatch-format-strings-should-not-have-brackets-in-macros.patch
> checkpatch-limit-sn-un-matches-to-actual-bit-sizes.patch
> checkpatch-version-029.patch
> checkpatch-add-some-common-blackfin-checks.patch
>
> Grumpy. These spit perl warnings but maintainer won't talk to me.
the last one shouldnt cause any warnings at all ;)
-mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2009-09-16 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 3:56 Mike Frysinger [this message]
2009-09-16 4:18 ` Andrew Morton
2009-09-16 4:24 ` Mike Frysinger
2009-09-16 6:06 ` Stephen Rothwell
2009-09-16 12:53 ` Mike Frysinger
2009-09-16 13:17 ` Stephen Rothwell
2009-09-16 6:03 ` Stephen Rothwell
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=8bd0f97a0909152056h61bfc487g6b8631966c6d72be@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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