From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] fbdev fixes for 3.0-rc2
Date: Mon, 06 Jun 2011 09:04:58 +0000 [thread overview]
Message-ID: <BANLkTik1nLG6f27JkR0kBvcJEoqUrq602A@mail.gmail.com> (raw)
In-Reply-To: <20110606033900.GF26101@linux-sh.org>
On Mon, Jun 6, 2011 at 12:39 PM, Paul Mundt <lethal@linux-sh.org> wrote:
>
> Bruno Prémont (1):
> video: Fix use-after-free by vga16fb on rmmod
Do you even *look* at what you ask me to pull from you?
Spend a bit of effort in not sending obviously bogus and corrupted
authorship patches. That one has Bruno's name correctly in the
sign-off, but you've done something horrible to it in the authorship.
Linus
next prev parent reply other threads:[~2011-06-06 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 3:39 [GIT PULL] fbdev fixes for 3.0-rc2 Paul Mundt
2011-06-06 9:04 ` Linus Torvalds [this message]
2011-06-06 9:15 ` Paul Mundt
2011-06-06 9:39 ` Bruno Prémont
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=BANLkTik1nLG6f27JkR0kBvcJEoqUrq602A@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@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).