All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bjorn Helgaas <bhelgaas@google.com>, Michal Marek <mmarek@suse.cz>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [GIT PULL] PCI updates for v3.11
Date: Fri, 2 Aug 2013 14:24:07 -0700	[thread overview]
Message-ID: <CA+55aFyf_TsUewZ=Fbf418=3-rOTOBmkQDskVY5FN9SbVyV9qg@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFzSG8ny=79_MFik5xP99c7eb-LMKh0JzTKpbiEB8Wt=5Q@mail.gmail.com>

On Fri, Aug 2, 2013 at 1:28 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Michal? I haven't pushed things out yet (and that allmodconfig build
> from scratch will take 20 min or so), but you can recreate my tree by
> pulling that pci thing locally from:

Yeah, it looks like if you start with an allmodconfig build from
before that pull, and then re-do "make allmodconfig" after the pull
without cleaning the build tree you get that warning.

[ Music from "Jaws" ]

Scary.

             Linus

  reply	other threads:[~2013-08-02 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 18:17 [GIT PULL] PCI updates for v3.11 Bjorn Helgaas
2013-08-02 20:28 ` Linus Torvalds
2013-08-02 21:24   ` Linus Torvalds [this message]
2013-08-05  8:39   ` Warnings from silentoldconfig (Re: [GIT PULL] PCI updates for v3.11) Michal Marek
2013-08-05  9:26     ` Yann E. MORIN
2013-08-05 22:58     ` Yann E. MORIN
2013-08-06  8:20       ` Michal Marek

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+55aFyf_TsUewZ=Fbf418=3-rOTOBmkQDskVY5FN9SbVyV9qg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=thomas.petazzoni@free-electrons.com \
    --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 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.