linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hermann <brummer-@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.0-rc7-rt0
Date: Thu, 21 Jul 2011 20:33:22 +0200	[thread overview]
Message-ID: <1311273202.2323.13.camel@box> (raw)
In-Reply-To: <alpine.LFD.2.02.1107211942420.2702@ionos>

Am Donnerstag, den 21.07.2011, 19:43 +0200 schrieb Thomas Gleixner:
> On Thu, 21 Jul 2011, Thomas Gleixner wrote:
> > On Thu, 21 Jul 2011, hermann wrote:
> > > I try to build the 3.0-rc7-rt0 but fail with the following message:
> > >  CC [M]  fs/ext3/balloc.o
> > > In file included from include/linux/jbd.h:247:0,
> > >                  from fs/ext3/balloc.c:18:
> > 
> > Find below a patch on top of rt0 which fixes this build failure and
> > some other stuff.

Many Thanks for the quick response, when I try to apply the patch's on a
fresh patched 3.0-rc7-rt0, I receive some Hunks :

 patch -p1<../patch-3.0-rc7-rt0.1.patch
patching file kernel/timer.c
Hunk #1 succeeded at 654 with fuzz 1.
Hunk #2 FAILED at 729.
1 out of 2 hunks FAILED -- saving rejects to file kernel/timer.c.rej
patching file mm/page_alloc.c
Hunk #1 FAILED at 1943.
1 out of 1 hunk FAILED -- saving rejects to file mm/page_alloc.c.rej
patching file include/linux/buffer_head.h
Hunk #1 FAILED at 74.
1 out of 1 hunk FAILED -- saving rejects to file
include/linux/buffer_head.h.rej
patching file include/linux/buffer_head.h
Hunk #1 FAILED at 109.
1 out of 1 hunk FAILED -- saving rejects to file
include/linux/buffer_head.h.rej

So I apply them per hand, (well some offset here and there). 
Build is running now, will report back if all went well for me now. 

kind regards
hermann


  reply	other threads:[~2011-07-21 18:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 16:22 [ANNOUNCE] 3.0-rc7-rt0 hermann
2011-07-21 17:35 ` Thomas Gleixner
2011-07-21 17:43   ` Thomas Gleixner
2011-07-21 18:33     ` hermann [this message]
2011-07-23  4:08     ` [ANNOUNCE] 3.0-rt1 hermann
2011-07-23  7:37       ` Thomas Gleixner
2011-07-21 18:28   ` [ANNOUNCE] 3.0-rc7-rt0 andi
2011-07-21 18:40     ` hermann
2011-07-21 19:57   ` [PATCH] Various fixups from first bug reports Uwe Kleine-König
2011-07-22  5:43     ` hermann
2011-07-22  6:57       ` Uwe Kleine-König
2011-07-22  7:40         ` hermann
2011-07-22 10:06           ` Trulan Martin
2011-07-22 11:04         ` Rusty Russell
2011-07-22 19:20           ` Uwe Kleine-König
2011-07-23  3:17             ` hermann
2011-07-23  9:57               ` Robin Gareus
     [not found]                 ` <4E2A9B18.6030000-+VlDMftONaMdnm+yROfE0A@public.gmane.org>
2011-07-23 14:19                   ` hermann
2011-07-23 14:33                     ` Robin Gareus
2011-07-23 15:21                       ` hermann
2011-07-23 18:53                     ` Uwe Kleine-König
  -- strict thread matches above, loose matches on Subject: below --
2011-07-20  0:37 [ANNOUNCE] 3.0-rc7-rt0 Thomas Gleixner
2011-07-20  2:48 ` Frank Rowand
2011-07-20  3:22   ` Fernando Lopez-Lezcano
2011-07-20  5:03 ` Paul E. McKenney
2011-07-20  9:02 ` David Kastrup
2011-07-20  9:48 ` Geunsik Lim
2011-07-20 11:08 ` Armin Steinhoff
2011-07-20 15:33   ` Madovsky
2011-07-20 15:56     ` Thomas Gleixner
2011-07-20 15:59       ` Madovsky
2011-07-20 17:02 ` Darren Hart
2011-07-20 19:15 ` Noah Watkins

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=1311273202.2323.13.camel@box \
    --to=brummer-@web.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).