From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
Cc: linux-rt-users@vger.kernel.org, rostedt@goodmis.org
Subject: Re: RT patches against v2.6.27-rc7 available
Date: Tue, 30 Sep 2008 18:50:46 -0400 [thread overview]
Message-ID: <48E2AD46.7060403@windriver.com> (raw)
In-Reply-To: <1222765114.30330.7.camel@sven.thebigcorporation.com>
Sven-Thorsten Dietrich wrote:
> On Mon, 2008-09-29 at 23:32 -0400, Paul Gortmaker wrote:
>
> Paul,
>
> First of all thanks for taking a shot at the forward-port.
>
>
>
>> I've completed a carry forward of the 26rt9 broken out patchset onto
>> the 2.6.27-rc7 kernel. There were a lot of changes in 2.6.27, so this
>> wasn't just a simple case of having all the patches magically work as-is.
>>
>
> Never is :)
>
>
>
> A lot of the patches have a lot of fuzz, in my experience, mis-patches
> occur more frequently with fuzz.
>
> You might want to refresh those patches.
>
I was originally thinking that there might be some value in seeing which
ones really didn't need a change, but given that Steven does a refresh
cycle over the patches for each release it probably makes sense for me
to refresh the fuzz/offset ones as well.
I'll have a patchset updated to 27rc8 available within a couple hours, and
for those working from the patches vs. the git tree, the patches will be
all fuzz/offset free.
Thanks,
Paul.
> Thanks,
>
> Sven
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-09-30 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 3:32 RT patches against v2.6.27-rc7 available Paul Gortmaker
2008-09-30 8:58 ` Sven-Thorsten Dietrich
2008-09-30 22:50 ` Paul Gortmaker [this message]
2008-10-01 5:12 ` Paul Gortmaker
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=48E2AD46.7060403@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sven@thebigcorporation.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.