public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Steven Noonan <steven@uplinklabs.net>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Mikael Pettersson <mikpe@it.uu.se>,
	linux-kernel@vger.kernel.org,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hugh@veritas.com>
Subject: Re: drivers/pci/probe.c compile warnings on -tip
Date: Mon, 6 Oct 2008 08:21:06 +0200	[thread overview]
Message-ID: <20081006062106.GC14945@elte.hu> (raw)
In-Reply-To: <86802c440810051106l6d58076cnb4a29ddd282e4ac@mail.gmail.com>


* Yinghai Lu <yinghai@kernel.org> wrote:

> On Sun, Oct 5, 2008 at 3:18 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Steven Noonan <steven@uplinklabs.net> wrote:
> >
> >> > AFAICT, these are fixed in Linus' tree, maybe the x86 tree needs an
> >> > update?
> >> >
> >>
> >> Hey Ingo, these warnings are still showing up on the latest -tip. Any
> >> idea why?
> >
> > yes, they got reintroduced via:
> >
> > | From ca81beb4a340ee690803fcb1498f863d0e68843f Mon Sep 17 00:00:00 2001
> > | From: Yinghai Lu <yhlu.kernel@gmail.com>
> > | Date: Thu, 4 Sep 2008 20:57:15 +0200
> > | Subject: [PATCH] pci: fix BAR print out
> >
> > which spread into a few topic branches:
> >
> > # irq/sparseirq: ca81beb: pci: fix BAR print out
> > # irq/sparseirq: f430d990: Merge branch 'linus' into irq/sparseirq
> > # timers/hpet-percpu: ca81beb: pci: fix BAR print out
> > # x86/uv: ca81beb: pci: fix BAR print out
> > # x86/uv: f430d990: Merge branch 'linus' into irq/sparseirq
> >
> > i suspect f430d990 is where the in-linus fix collided with the
> > in-irq/sparseirq fix. I'm inclined to revert it. Yinghai?
> >
> 
> please. it should be reverted from irq/sparseirq etc branch...because
> updated one is already in linus tree.

ok, reverted it in irq/sparseirq and propagated that to the 
sparseirq-derived topic trees as well.

	Ingo

      reply	other threads:[~2008-10-06  6:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01  8:02 drivers/pci/probe.c compile warnings on -tip Steven Noonan
2008-10-01 10:47 ` Mikael Pettersson
2008-10-01 15:51   ` Jesse Barnes
2008-10-05  3:55     ` Steven Noonan
2008-10-05 10:18       ` Ingo Molnar
2008-10-05 18:06         ` Yinghai Lu
2008-10-06  6:21           ` Ingo Molnar [this message]

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=20081006062106.GC14945@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=hugh@veritas.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=steven@uplinklabs.net \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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