linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: Alexey Dobriyan <adobriyan@gmail.com>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Cc: Bryan Wu <bryan.wu@analog.com>
Subject: Re: [PATCH] Remove fs.h from mm.h
Date: Tue, 31 Jul 2007 10:51:37 +0800	[thread overview]
Message-ID: <1185850297.20043.6.camel@roc-desktop> (raw)
In-Reply-To: <20070730194335.GE5776@martell.zuzino.mipt.ru>

On Mon, 2007-07-30 at 23:43 +0400, Alexey Dobriyan wrote:
> On Mon, Jul 30, 2007 at 12:42:07PM +0800, Bryan Wu wrote:
> > Can I do something to help this regression testing?
> >
> > Please feel free to ask me.
> 
> Sorry, blackfin toolchain doesn't like me, so I can't test this myself.
> Check current -git if I screwed up anything.
> 
Oh, do you need use blackfin toolchain? Actually, it is very simple to
setup it on your machine.
please get the latest binary toolchain here:
http://blackfin.uclinux.org/gf/download/frsrelease/344/3180/blackfin-toolchain-uclinux-SVN.tar.bz2
http://blackfin.uclinux.org/gf/download/frsrelease/344/3181/blackfin-toolchain-linux-uclibc-SVN.tar.bz2

 - untar these 2 tar ball
 - add the path to your environment variables
 - ready to compile the kernel by these blackfin cross toolchain

> It still takes too much time from clean git pull to final patch, so
> sending it to you would  increase risk that someone will touch core
> headers nontrivially invalidating all work.

Need I to generate the patch? I will take a look at the latest git-tree.

Many thanks, we hope you can add our blackfin to your cross-build check.

Best Regards,
- Bryan Wu

  parent reply	other threads:[~2007-07-31  2:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070729223613.GA5916@martell.zuzino.mipt.ru>
     [not found] ` <alpine.LFD.0.999.0707291706490.3442@woody.linux-foundation.org>
2007-07-30 13:00   ` [PATCH] Remove fs.h from mm.h Hirokazu Takata
2007-07-30 19:07     ` Alexey Dobriyan
2007-07-31  1:29       ` Hirokazu Takata
     [not found]   ` <1185770527.22473.2.camel@roc-desktop>
     [not found]     ` <20070730194335.GE5776@martell.zuzino.mipt.ru>
2007-07-31  2:51       ` Bryan Wu [this message]
2007-08-02 19:44         ` blackfin toolchain and build issues Sam Ravnborg
2007-08-03  2:18           ` Bryan Wu
2007-08-03  4:32             ` Sam Ravnborg

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=1185850297.20043.6.camel@roc-desktop \
    --to=bryan.wu@analog.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).