From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Nitin Gupta <nitingupta910@gmail.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Konrad Wilk <konrad.wilk@oracle.com>
Subject: Re: linux-next: Tree for Apr 19 (zcache)
Date: Thu, 19 Apr 2012 18:49:40 -0500 [thread overview]
Message-ID: <4F90A494.1080906@linux.vnet.ibm.com> (raw)
In-Reply-To: <0b74f96b-8450-4dfb-8798-36edd0e06a64@default>
On 04/19/2012 05:36 PM, Dan Magenheimer wrote:
>> From: Randy Dunlap [mailto:rdunlap@xenotime.net]
>>
>> Full randconfig file is attached.
Lost the attached randconfig file. Please forward.
Seth
next prev parent reply other threads:[~2012-04-19 23:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 6:46 linux-next: Tree for Apr 19 Stephen Rothwell
2012-04-19 22:26 ` linux-next: Tree for Apr 19 (media/video/mt9m032.c) Randy Dunlap
2012-04-19 23:20 ` Mauro Carvalho Chehab
2012-04-19 22:30 ` linux-next: Tree for Apr 19 (zcache) Randy Dunlap
2012-04-19 22:36 ` Dan Magenheimer
2012-04-19 23:49 ` Seth Jennings [this message]
2012-04-20 4:36 ` Seth Jennings
2012-04-20 16:37 ` Konrad Rzeszutek Wilk
2012-04-20 19:06 ` Seth Jennings
2012-04-24 1:06 ` Konrad Rzeszutek Wilk
2012-04-19 23:15 ` [PATCH -next] nfsd: fix nfs4recover.f printk format warning Randy Dunlap
[not found] ` <4F909C78.7000008-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-04-30 19:25 ` [PATCH resend] nfsd: fix nfs4recover.c " Randy Dunlap
[not found] ` <4F9EE72B.1020401-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-04-30 21:41 ` J. Bruce Fields
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=4F90A494.1080906@linux.vnet.ibm.com \
--to=sjenning@linux.vnet.ibm.com \
--cc=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nitingupta910@gmail.com \
--cc=rdunlap@xenotime.net \
--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;
as well as URLs for NNTP newsgroup(s).