From: Frank Rowand <frank.rowand@am.sony.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "Rowand, Frank" <Frank_Rowand@sonyusa.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Linearized 2.6.33.7-rt30 patch set available (with free coffee!)
Date: Mon, 31 Jan 2011 18:15:26 -0800 [thread overview]
Message-ID: <4D476CBE.4000407@am.sony.com> (raw)
In-Reply-To: <4D474736.40703@windriver.com>
On 01/31/11 15:35, Paul Gortmaker wrote:
< snip >
> OK, so it is simply a matter of quilt dying while git am is capable
> of doing the right thing (see below for evidence).
< snip >
Yes, when I use git am I get the same result that you show here:
> tip-debare$git checkout quilt-junk
> Switched to branch 'quilt-junk'
> tip-debare$git am patches/genirq-support-forced-threading-of-interrupts.patch
> Applying: genirq: support forced threading of interrupts
>
> (git am is happy,
Yes, git am somehow managed to apply the patch cleanly.
If at this point you do
git show >junk
diff junk patches/genirq-support-forced-threading-of-interrupts.patch
you will see that the patch as applied by git am has cleaned up the
problem with the original patch. Pretty cool magic...
> now rewind/pop that commit and retry with quilt)
>
> tip-debare$git reset --hard HEAD^
> HEAD is now at fd659fd7 quilt-junk
> tip-debare$quilt push
> Applying patch genirq-support-forced-threading-of-interrupts.patch
> patching file include/linux/interrupt.h
> patching file include/linux/irq.h
> patching file include/linux/sched.h
> patching file kernel/irq/chip.c
> patching file kernel/irq/handle.c
> patching file kernel/irq/manage.c
> Hunk #2 succeeded at 465 (offset 3 lines).
> Hunk #3 succeeded at 633 (offset 3 lines).
> Hunk #4 succeeded at 706 (offset 3 lines).
> Hunk #5 succeeded at 736 (offset 3 lines).
> Hunk #6 succeeded at 804 (offset 3 lines).
> Hunk #7 FAILED at 829.
> 1 out of 7 hunks FAILED -- rejects in file kernel/irq/manage.c
> patching file kernel/irq/migration.c
> patching file kernel/sched.c
> Hunk #1 succeeded at 5147 (offset 3 lines).
> Patch genirq-support-forced-threading-of-interrupts.patch does not apply (enforce with -f)
> tip-debare$
Again, I get the same result. And I get the same "Hunk #7 FAILED" with
patch --dry-run -p1 < patches/genirq-support-forced-threading-of-interrupts.patch
-Frank
next prev parent reply other threads:[~2011-02-01 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 21:05 Linearized 2.6.33.7-rt30 patch set available (with free coffee!) Frank Rowand
2011-01-31 21:12 ` Paul Gortmaker
2011-01-31 21:57 ` Frank Rowand
2011-01-31 23:35 ` Paul Gortmaker
2011-02-01 1:07 ` Frank Rowand
2011-02-01 2:15 ` Frank Rowand [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-24 17:00 Paul Gortmaker
2011-01-24 17:21 ` Madovsky
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=4D476CBE.4000407@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=Frank_Rowand@sonyusa.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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.