All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lucas Stach <l.stach@pengutronix.de>,
	Richard Zhu <Richard.Zhu@freescale.com>,
	Marek Kordik <kordikmarek@gmail.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Andreas Hartmann <andihartmann@freenet.de>,
	Alexey Voronkov <zermond@gmail.com>,
	David Airlie <airlied@linux.ie>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [GIT PULL] PCI fixes for v3.19
Date: Fri, 30 Jan 2015 10:01:33 -0800	[thread overview]
Message-ID: <CA+8MBbLprQgbOo_aTaafHzEVcOPR3vp2gxFPDTX3YYS2Ywh6zg@mail.gmail.com> (raw)
In-Reply-To: <CAErSpo5CmVTw1-jQ2cwZS27nWH6zEyO5yqaedPN8jeRiU=JUfQ@mail.gmail.com>

On Fri, Jan 30, 2015 at 8:56 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> Tony, does the system work as it did before?  Is the only problem that
> now we have more warnings than we did before?

Yup - things seem to be working. Just have a bunch of new console messages.

It seems that at least some of them are valid - the BIOS isn't describing some
things that it should.  I don't think we need to re-apply code that
used to paper
over this problem. I can just add these to the list of "harmless" messages to
ignore when running new kernels on this old machine.

Or did I misunderstand some part of this thread?

-Tony

  reply	other threads:[~2015-01-30 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 20:31 [GIT PULL] PCI fixes for v3.19 Bjorn Helgaas
2015-01-26 19:58 ` Tony Luck
2015-01-26 21:02   ` Bjorn Helgaas
2015-01-26 21:24     ` Tony Luck
2015-01-26 23:53       ` Bjorn Helgaas
2015-01-27  3:55         ` Yinghai Lu
2015-01-27 14:03           ` Bjorn Helgaas
2015-01-27 23:27             ` Tony Luck
2015-01-27  3:43       ` Yinghai Lu
2015-01-27 23:24         ` Tony Luck
2015-01-28  0:54           ` Yinghai Lu
2015-01-30 16:56             ` Bjorn Helgaas
2015-01-30 18:01               ` Tony Luck [this message]
2015-01-30 18:18                 ` Bjorn Helgaas
2015-01-30 21:49               ` Yinghai Lu
2015-01-30 22:12                 ` Bjorn Helgaas
     [not found] <20150204191831.GA13785@google.com>
2015-02-11 16:48 ` Bjorn Helgaas

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=CA+8MBbLprQgbOo_aTaafHzEVcOPR3vp2gxFPDTX3YYS2Ywh6zg@mail.gmail.com \
    --to=tony.luck@gmail.com \
    --cc=Richard.Zhu@freescale.com \
    --cc=airlied@linux.ie \
    --cc=alex.williamson@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=andihartmann@freenet.de \
    --cc=bhelgaas@google.com \
    --cc=kordikmarek@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.org \
    --cc=zermond@gmail.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.