From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Bryan Wu <cooloney.lkml@gmail.com>
Subject: Re: 2.6.32 -mm Blackfin patches
Date: Wed, 16 Sep 2009 16:03:13 +1000 [thread overview]
Message-ID: <20090916160313.aeb61ef7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090915211810.d1b83015.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
Hi Andrew, Mike,
On Tue, 15 Sep 2009 21:18:10 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 15 Sep 2009 23:56:21 -0400 Mike Frysinger <vapier.adi@gmail.com> wrote:
>
> > 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
>
> Sent.
>
> > > 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)
>
> Well, it isn't in linux-next so as far as I'm concerned I have the
> only copy. Should you be getting your tree into linux-next?
There is a blackfin tree in linux-next managed by Bryan Wu:
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git#for-linus
As far as I can tell, it hasn't bee updated since March 30.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-09-16 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 3:56 Mike Frysinger
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 [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=20090916160313.aeb61ef7.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=cooloney.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vapier.adi@gmail.com \
/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