From: Sachin Sant <sachinp@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for April 21
Date: Tue, 21 Apr 2009 10:21:38 +0530 [thread overview]
Message-ID: <49ED50DA.3020602@in.ibm.com> (raw)
In-Reply-To: <20090421141944.4c3f5a7a.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20090420:
Hi Stephen,
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/ doesn't seem
to have today's next patch. Can you please upload the patch tarball ?
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-04-21 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 4:19 linux-next: Tree for April 21 Stephen Rothwell
2009-04-21 4:51 ` Sachin Sant [this message]
2009-04-21 5:00 ` Stephen Rothwell
2009-04-21 5:41 ` Sachin Sant
-- strict thread matches above, loose matches on Subject: below --
2011-04-21 3:20 Stephen Rothwell
2008-04-21 10:52 Stephen Rothwell
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=49ED50DA.3020602@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).