From: "John Stoffel" <john@stoffel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Blackfin Architecture Team
<uclinux-dist-devel@blackfin.uclinux.org>,
David Howells <dhowells@redhat.com>,
stable@kernel.org
Subject: Re: Fix for shared flat binary format in 2.6.30
Date: Mon, 22 Jun 2009 16:39:08 -0400 [thread overview]
Message-ID: <19007.60396.259650.682653@stoffel.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0906221137580.3240@localhost.localdomain>
>>>>> "Linus" == Linus Torvalds <torvalds@linux-foundation.org> writes:
Linus> On Mon, 22 Jun 2009, Bernd Schmidt wrote:
>>
>> This fixes a crash in 2.6.30 with shared flat binaries. prepare_binfmt now
>> requires a cred pointer to be set up, which isn't done in binfmt_flat.c.
Linus> This has so many bugs in patch submission that I literally
Linus> almost gave up despite it being a trivial patch.
I just recently submitted a patch, and it took me a while to figure
out a git flow for stupid, simple patches so that I, a moron, could
understand it. Here's what I've documented. Maybe it should be added
to Documentation/SubmittingPatches so that people like me, who only
rarely use git for anything, can use it to submit stuff properly?
###################################################################
# References
http://linux.yyz.us/git-howto.html
http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html
http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html
# One time commands
> apt-get install git-email
> git config --global user.name "John Stoffel"
> git config --global user.email "john@stoffel.org"
# Only to be done infrequently
> mkdir /var/tmp/git-tree
> cd /var/tmp/git-tree
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6
# Make a new branch <branch> for the patch you're doing. In this
case, we'll do 'sym_hipd-ratelimit'
> git checkout -b sym_hipd-ratelimit
# Now edit the file
> vi drivers/scsi/sym53c8xx_2/sym_hipd.c
> git commit -a
# Put in a simple message of a line or two.
ratelimit parity error reporting, which helps alot on bootup over serial
console when you get 10,000+ lines of this message.
# Now exit the editor
# Check the commit, which is the most recent one by default
> git log -1
# See the actual patch with:
> git diff master..HEAD
# Make a patch you can send out, including any CC: and the signoff (-s)
> git format-patch --cc=linux-scsi@vger.kernel.org --cc=stable@kernel.org -s
0001-ratelimit-parity-error-reporting-which-helps-alot-on.patch
# Now look the patch over and see if you need to edit the subject or
# anything
# In this case, I don't like the commit message
vi 0001-ratelimit-parity-error-reporting-which-helps-alot-on.patch
# Now do a dry run to send the email
> git send-email --dry-run --to=linux-kernel@vger.kernel.org 0001-ratelimit-parity-error-reporting-which-helps-alot-on.patch
# Looks good, send for real
> git send-email --to=linux-kernel@vger.kernel.org 0001-ratelimit-parity-error-reporting-which-helps-alot-on.patch
# Cleanup, got back to the main branch and merge in our change, just
# for fun
> git branch master
> git merge sym_hipd-ratelimit
next prev parent reply other threads:[~2009-06-22 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 10:36 Bernd Schmidt
2009-06-22 18:44 ` Linus Torvalds
2009-06-22 18:56 ` Linus Torvalds
2009-06-22 19:35 ` [PATCH] FLAT: fix uninitialized ptr with shared libs Mike Frysinger
2009-06-22 20:48 ` Linus Torvalds
2009-06-22 21:00 ` [Uclinux-dist-devel] " Mike Frysinger
2009-06-23 10:14 ` Bernd Schmidt
2009-06-29 23:44 ` [stable] " Greg KH
2009-06-22 20:39 ` John Stoffel [this message]
2009-06-22 21:06 ` Fix for shared flat binary format in 2.6.30 Linus Torvalds
2009-06-23 1:59 ` John Stoffel
2009-06-23 2:44 ` Linus Torvalds
2009-06-25 7:12 ` Junio C Hamano
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=19007.60396.259650.682653@stoffel.org \
--to=john@stoffel.org \
--cc=bernds_cb1@t-online.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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
all inboxes | Powered by JetHome®