From: Stephen Rothwell <sfr@canb•auug.org.au>
To: michal.simek@petalogix•com
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 23:24:37 +1000 [thread overview]
Message-ID: <20090527232437.d5509976.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4A1D3ACF.2090206@petalogix.com>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
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.
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.
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.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-27 13:24 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 [this message]
2009-05-27 13:33 ` Michal Simek
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=20090527232437.d5509976.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--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=michal.simek@petalogix$(echo .)com \
/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