All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Randy Dunlap <rdunlap@xenotime.net>, dan.magenheimer@oracle.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	xen-devel@lists.xensource.com
Subject: Re: linux-next: Tree for July 22 (xen)
Date: Fri, 22 Jul 2011 13:48:33 -0400	[thread overview]
Message-ID: <20110722174833.GB7698@dumpdata.com> (raw)
In-Reply-To: <20110722173548.GA7698@dumpdata.com>

On Fri, Jul 22, 2011 at 01:35:48PM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Jul 22, 2011 at 09:22:45AM -0700, Randy Dunlap wrote:
> > On Fri, 22 Jul 2011 16:42:37 +1000 Stephen Rothwell wrote:
> > 
> > > Hi all,
> 
> Hey Randy,
> 
> This only shows up on xen but not xen-two?

n/m. I can reproduce it. Thanks for spotting it, looks like it is missing
an #include there.

      reply	other threads:[~2011-07-22 17:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22  6:42 linux-next: Tree for July 22 Stephen Rothwell
2011-07-22 15:53 ` linux-next: Tree for July 22 (uml) Randy Dunlap
2011-07-22 18:55   ` Richard Weinberger
2011-07-22 18:55     ` Richard Weinberger
2011-07-22 20:15     ` Randy Dunlap
2011-07-22 21:39     ` [tip:x86/asm] um: Make rwsem.S depend on CONFIG_RWSEM_XCHGADD_ALGORITHM tip-bot for Richard Weinberger
2011-07-25  6:54     ` linux-next: Tree for July 22 (uml) Jan Beulich
2011-07-25  6:54       ` Jan Beulich
2011-07-22 16:04 ` linux-next: Tree for July 22 (bcma) Randy Dunlap
2011-07-22 20:27   ` [PATCH] bcma: fix 'SSB_PCICORE_BFL_NOPCI' undeclared build breakage John W. Linville
2011-07-22 21:35     ` Rafał Miłecki
2011-07-23  8:16       ` Rafał Miłecki
2011-07-22 16:22 ` linux-next: Tree for July 22 (xen) Randy Dunlap
2011-07-22 17:35   ` Konrad Rzeszutek Wilk
2011-07-22 17:35     ` Konrad Rzeszutek Wilk
2011-07-22 17:48     ` Konrad Rzeszutek Wilk [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=20110722174833.GB7698@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    --cc=xen-devel@lists.xensource.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.