All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, linux-pci@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Bryan Veal <bryan.e.veal@intel.com>,
	Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCHv8] x86/PCI: Initial commit for new VMD device driver
Date: Tue, 12 Jan 2016 13:42:28 -0600	[thread overview]
Message-ID: <20160112194228.GA28453@localhost> (raw)
In-Reply-To: <20160112180829.GB28857@localhost.localdomain>

On Tue, Jan 12, 2016 at 06:08:29PM +0000, Keith Busch wrote:
> On Wed, Jan 13, 2016 at 01:40:33AM +0800, kbuild test robot wrote:
> > [auto build test ERROR on tip/x86/core]
> 
> Looks a reason to repost the entire series, or maybe I should have
> replied to the existing thread with the dependencies.

Reposting the series as a whole makes my life much easier.  I select
all the patches in a series and apply them as a group, and that's
much harder if individual patches in the series get superceded.

> > url:    https://github.com/0day-ci/linux/commits/Keith-Busch/x86-PCI-Initial-commit-for-new-VMD-device-driver/20160113-003207
> > config: x86_64-allmodconfig (attached as .config)
> > reproduce:
> >         # save the attached .config to linux build tree
> >         make ARCH=x86_64 
> > 
> > All errors (new ones prefixed by >>):
> > 
> > >> arch/x86/pci/vmd.c:85:20: error: field 'dma_domain' has incomplete type
> >      struct dma_domain dma_domain;

      reply	other threads:[~2016-01-12 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 16:28 [PATCHv8] Driver for new "VMD" device Keith Busch
2016-01-12 16:28 ` [PATCHv8] x86/PCI: Initial commit for new VMD device driver Keith Busch
2016-01-12 17:40   ` kbuild test robot
2016-01-12 18:08     ` Keith Busch
2016-01-12 19:42       ` Bjorn Helgaas [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=20160112194228.GA28453@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=bryan.e.veal@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=jonathan.derrick@intel.com \
    --cc=kbuild-all@01.org \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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.