From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze fixes for 2.6.35-rc3
Date: Mon, 07 Jun 2010 20:13:23 +0200 [thread overview]
Message-ID: <4C0D36C3.4040709@monstr.eu> (raw)
In-Reply-To: <alpine.LFD.2.00.1006071052410.3515@i5.linux-foundation.org>
Linus Torvalds wrote:
>
> On Mon, 7 Jun 2010, Michal Simek wrote:
>> please pull the following changes.
>
> No. See my -rc2 announcement. Also, this has clearly not even been tested,
> since it's been rebased on top of a recent commit.
>
> So I'm being a hard-ass this time around. I don't care what subsystem it
> is, I want pull requests to follow the after-merge-window rules.
> Regressions, security bugs, and major oopses. Not just random changes.
ok. No problem. There is only 2-3 patches which bring new functionality.
The rest is bug fixes. I am going to send next pull request just with fixes.
Michal
>
> Linus
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2010-06-07 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 13:53 [GIT PULL] arch/microblaze fixes for 2.6.35-rc3 Michal Simek
2010-06-07 17:54 ` Linus Torvalds
2010-06-07 18:13 ` 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=4C0D36C3.4040709@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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