From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Nathan Grennan <linux-rt-users@cygnusx-1.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] RT for v2.6.34.8 now available.
Date: Mon, 07 Mar 2011 16:53:08 -0500 [thread overview]
Message-ID: <4D7553C4.7080801@windriver.com> (raw)
In-Reply-To: <4D754FDC.5050701@cygnusx-1.org>
On 11-03-07 04:36 PM, Nathan Grennan wrote:
>
>> Yes, it is the header cleanup done in the 33-->34 dev cycle, seen
>> between the rev list ^9e74e7c b66696e that changes slab.h use.
>>
>> If you look at 8a2032dba45e24 *in the patch repo* you will see where
>> I fixed it for the baseline RT-enabled defconfig. (Meaning I did a
>> make defconfig, then enabled the RT options). Your config must be
>> setting something different/extra.
>>
>> If you do a git show on the above rev list and on the fix in the patch
>> repo, you will probably be able to tell what is going on. Also please
>> send me your config (off list) so I can ensure it compiles properly myself.
>>
>
> I found the cause. The patching was incomplete. The correct patch
> command is the one below, removing the comment lines.
>
> cat ../rt-patches/series | grep -v '\#' | xargs -i cat ../rt-patches/{}
> | patch -p1
Folks should really use git, or quilt, or guilt, or git quilt-import, or
for that matter, *anything* that at least checks exit status.
I like the fact that "git am" is quite strict about what it accepts
and applies, so I'll typically wrap things around that core operation.
Here is a completely trivial example of using git am:
cat `grep ^[a-zA-Z0-9] series` > /tmp/foo.mbox
git am /tmp/foo.mbox
Paul.
next prev parent reply other threads:[~2011-03-07 21:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 22:24 [ANNOUNCE] RT for v2.6.34.8 now available Paul Gortmaker
2011-03-05 3:05 ` Nathan Grennan
2011-03-07 14:36 ` Paul Gortmaker
2011-03-07 21:36 ` Nathan Grennan
2011-03-07 21:53 ` Paul Gortmaker [this message]
2011-03-05 3:24 ` Madovsky
2011-03-05 4:40 ` Madovsky
2011-03-05 10:44 ` Niccolò Belli
2011-03-07 6:51 ` Fernando Lopez-Lezcano
2011-03-07 14:44 ` Paul Gortmaker
2011-03-08 0:06 ` Nathan Grennan
2011-03-07 20:00 ` Fernando Lopez-Lezcano
2011-03-07 20:41 ` Fernando Lopez-Lezcano
2011-03-07 20:52 ` Paul Gortmaker
2011-03-07 20:54 ` Fernando Lopez-Lezcano
2011-03-08 0:52 ` Paul Gortmaker
2011-03-08 23:40 ` Fernando Lopez-Lezcano
2011-03-07 20:01 ` Arnd Bergmann
2011-03-07 20:40 ` Paul Gortmaker
2011-03-08 16:21 ` Arnd Bergmann
2011-03-18 20:15 ` 2.6.33-7-rt30 and 2.6.38 comparison Madovsky
2011-03-18 20:16 ` Ilyes Gouta
2011-03-18 21:06 ` Niccolò Belli
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=4D7553C4.7080801@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@cygnusx-1.org \
--cc=linux-rt-users@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).