From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: RE: linux-next: Tree for June 6 (frontswap)
Date: Wed, 8 Jun 2011 17:12:06 -0700 (PDT) [thread overview]
Message-ID: <080e1123-ea5d-4ea7-8d76-3f748937c020@default> (raw)
In-Reply-To: <d0e92f96-df09-4ac2-ad5e-53cdd92aba94@default>
> From: Dan Magenheimer
> Sent: Wednesday, June 08, 2011 11:02 AM
> To: Randy Dunlap
> Cc: Stephen Rothwell; linux-next@vger.kernel.org; LKML
> Subject: RE: linux-next: Tree for June 6 (frontswap)
>
> > From: Randy Dunlap
> > Sent: Wednesday, June 08, 2011 10:29 AM
> > To: Dan Magenheimer
> > Cc: Stephen Rothwell; linux-next@vger.kernel.org; LKML
> > Subject: Re: linux-next: Tree for June 6 (frontswap)
> >
> > On Mon, 6 Jun 2011 13:23:09 -0700 (PDT) Dan Magenheimer wrote:
> >
> > > > Does frontswap need to depend on SWAP?
> > >
> > > Indeed you are correct! Thanks for catching that!
> >
> > Please fix the tree in linux-next so that this build error does not
> > continue.
>
> Sorry, I thought it was just an observation, didn't know
> it was breaking your build, so didn't know there was a rush.
> I am away from my machines for the rest of the day, but will
> get it fixed and resubmitted first thing tomorrow (US time).
Got back early. Should be fixed now, hope it is in time
for the next linux-next merge. And sorry for the noise!
next prev parent reply other threads:[~2011-06-09 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 3:20 linux-next: Tree for June 6 Stephen Rothwell
2011-06-06 19:55 ` linux-next: Tree for June 6 (sctp) Randy Dunlap
2011-06-06 20:06 ` David Miller
2011-06-06 20:06 ` linux-next: Tree for June 6 (frontswap) Randy Dunlap
2011-06-06 20:23 ` Dan Magenheimer
2011-06-08 16:28 ` Randy Dunlap
2011-06-08 17:01 ` Dan Magenheimer
2011-06-09 0:12 ` Dan Magenheimer [this message]
2011-06-09 1:04 ` Stephen Rothwell
2011-06-07 9:48 ` linux-next: Tree for June 6 Catalin Marinas
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=080e1123-ea5d-4ea7-8d76-3f748937c020@default \
--to=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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