public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lee Revell <rlrevell@joe-job.com>,
	Esben Nielsen <nielsen.esben@googlemail.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: 2.6.19-rc6-rt0, -rt YUM repository
Date: Fri, 17 Nov 2006 09:44:55 -0800	[thread overview]
Message-ID: <1163785495.3097.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20061117161742.GA10182@elte.hu>

On Fri, 2006-11-17 at 17:17 +0100, Ingo Molnar wrote:
> * Lee Revell <rlrevell@joe-job.com> wrote:
> 
> > On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> > > * Daniel Walker <dwalker@mvista.com> wrote:
> > > 
> > > > [...] Should we start a known regression list?
> > > 
> > > please resend the bugs that still trigger for you with 2.6.19-rt0.
> > 
> > I'm working with the developers of the 64Studio distro who are 
> > attempting to ship a stable -rt kernel so I have access to lots of 
> > good bug reports.  Oops on boot is by far the most common.  I'll post 
> > details once we've retested with 2.6.19-rt0.
> 
> thanks, please do that. Right now i have no open boot-crash regression 
> left that i can reproduce.


Should we pull in Steve's patch for these, or are you just grabbing
Jeff's tree? I noticed they aren't always commented "shut up gcc"  .

--- linux.orig/arch/i386/kernel/efi.c
+++ linux/arch/i386/kernel/efi.c
@@ -271,7 +271,7 @@ void efi_memmap_walk(efi_freemem_callbac
        struct range {
                unsigned long start;
                unsigned long end;
-       } prev, curr;
+       } prev = { } /* shut up gcc */ , curr = { } /* shut up gcc */ ;
        efi_memory_desc_t *md;
        unsigned long start, end;
        void *p;


  reply	other threads:[~2006-11-17 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 15:35 2.6.19-rc6-rt0, -rt YUM repository Ingo Molnar
2006-11-16 16:31 ` Daniel Walker
2006-11-16 20:16   ` Ingo Molnar
2006-11-16 21:12   ` Esben Nielsen
2006-11-16 21:44     ` Daniel Walker
2006-11-16 22:07       ` Ingo Molnar
2006-11-16 22:37         ` Daniel Walker
2006-11-17  5:55           ` Ingo Molnar
2006-11-17  6:50             ` Ingo Molnar
2006-11-17  6:54               ` Ingo Molnar
2006-11-17  6:59                 ` Ingo Molnar
2006-11-17 15:58         ` Lee Revell
2006-11-17 16:17           ` Ingo Molnar
2006-11-17 17:44             ` Daniel Walker [this message]
2006-11-21  8:22               ` Ingo Molnar
2006-11-17 18:45             ` Lee Revell
2006-11-17 19:13               ` Ingo Molnar
2006-11-17  0:06 ` Sergio Monteiro Basto
2006-11-17  9:22   ` Ingo Molnar
2006-11-20  2:09     ` Sergio Monteiro Basto

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=1163785495.3097.7.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nielsen.esben@googlemail.com \
    --cc=rlrevell@joe-job.com \
    --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