All of lore.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:06:23 +0200	[thread overview]
Message-ID: <4A1D3ACF.2090206@petalogix.com> (raw)
In-Reply-To: <20090527181022.f69d7036.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> HI Michal,
>
> On Wed, 27 May 2009 09:22:36 +0200 Michal Simek <michal.simek@petalogix.com> wrote:
>   
>> Can you please merge my next branch to linux-next?
>>
>> The following changes since commit 5805977e63a36ad56594a623f3bd2bebcb7db233:
>>   Linus Torvalds (1):
>>         Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/drm-2.6
>>
>> are available in the git repository at:
>>
>>   git://git.monstr.eu/linux-2.6-microblaze.git next
>>     
>
> I have added it to the end of the tree for today (you just caught me in
> time :-)).  Tomorrow it will be moved back with all the other
> architectures.
>   
;-)

> What I tell everyone: all patches/commits in the tree/series must
> have been:
>
> 	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.
> *before* they are included.  The linux-next tree is for integration
> testing and to lower the impact of conflicts between subsystems in the
> next merge window.
>   
I would like to know that Kconfig changes (enabling some drivers) + Arnd
generic changes
not caused any problem which I should know about.
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.
>   
next branch is based on my for-linus branch - There are only microblaze
specific changes in arch/microblaze
and these changes shouldn't have impact to any subsystem that's why I
don't expect any problem in it.

If I am wrong in anything let me know. This is my first "pull request to
linux-next".

I see the first problem that I should use {GIT PULL] prefix in subject.

Thanks,
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:06 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 [this message]
2009-05-27 13:24     ` Stephen Rothwell
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=4A1D3ACF.2090206@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=john.williams@petalogix.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.