From: Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>
To: Dan Magenheimer <dan.magenheimer@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Sasha Levin <levinsasha928@gmail•com>,
linux-next@vger•kernel.org
Subject: Re: frontswap.v16 now in Linus tree, please stop pulling frontswap for linux-next
Date: Sat, 9 Jun 2012 10:36:45 -0400 [thread overview]
Message-ID: <20120609143645.GA23881@phenom.dumpdata.com> (raw)
In-Reply-To: <b4f9b288-da94-4e54-b5dd-7d8b0b4e5d68@default>
On Fri, Jun 08, 2012 at 03:04:05PM -0700, Dan Magenheimer wrote:
> Hi Stephen --
>
> Don't know if Konrad is on vacation today or if this is already
> resolved but, if not, please stop pulling frontswap.v14 (tmem branch)
> from Konrad as frontswap.v16 is now in Linus' tree as of
> Monday, shortly after -rc1.
Ah, thanks for notice. I've reset the linux-next to v3.5-rc2. Thanks!
prev parent reply other threads:[~2012-06-09 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 22:04 frontswap.v16 now in Linus tree, please stop pulling frontswap for linux-next Dan Magenheimer
2012-06-09 14:36 ` 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=20120609143645.GA23881@phenom.dumpdata.com \
--to=konrad.wilk@oracle$(echo .)com \
--cc=dan.magenheimer@oracle$(echo .)com \
--cc=levinsasha928@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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