public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
	Arnd Bergmann <arnd@arndb•de>,
	John Williams <john.williams@petalogix•com>,
	linux-next@vger•kernel.org
Subject: Re: Microblaze merge
Date: Wed, 27 May 2009 15:33:49 +0200	[thread overview]
Message-ID: <4A1D413D.5090507@petalogix.com> (raw)
In-Reply-To: <20090527232437.d5509976.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi Michal,
>
> On Wed, 27 May 2009 15:06:23 +0200 Michal Simek <michal.simek@petalogix•com> wrote:
>   
>>> 	posted to a relevant mailing list
>>>   
>>>       
>> was
>>     
>>> 	reviewed
>>>   
>>>       
>> It was reviewed v1 - v2 contains all reported problems
>>     
>>> 	unit tested
>>>   
>>>       
>> I tested it
>>     
>>> 	destined for the next merge window (or the current release)
>>>   
>>>       
>> it is for next merge open window.
>>     
>
> All good.
>
>   
>> I see the first problem that I should use {GIT PULL] prefix in subject.
>>     
>
> Not for me.  Now that you have asked for inclusion, I will fetch the
> tree/branch that you pointed me to every day until you tell me not to any
> more.  So all you have to do is update that branch when your new stuff
> meets the above criteria.
>   
ok
> I usually don't expect any problems from the architecture trees since, as
> you say, they are usually pretty much contained to their own arch/
> directory.
>   
:-) I too.
> One thing - is it easy for me to build a cross compiler for microblaze
> (i.e. does some GNU release of gcc just work)?  If so, I could add some
> microblaze configs to my automated builds.
>   
We have two approaches - script/crosstools. I will talk with John and
let you know.
We have to provide new tools for others too.

Anyway thanks for your offer I let you know about.

Michal





-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

      reply	other threads:[~2009-05-27 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  7:22 Microblaze merge Michal Simek
2009-05-27  8:10 ` Stephen Rothwell
2009-05-27 13:06   ` Michal Simek
2009-05-27 13:24     ` Stephen Rothwell
2009-05-27 13:33       ` Michal Simek [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=4A1D413D.5090507@petalogix.com \
    --to=michal.simek@petalogix$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=john.williams@petalogix$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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