From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 9
Date: Sat, 10 Aug 2013 09:46:42 +1000 [thread overview]
Message-ID: <20130810094642.c06a8f469f8601895c0f569f@canb.auug.org.au> (raw)
In-Reply-To: <52051E90.3090507@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Hi Randy,
On Fri, 09 Aug 2013 09:53:36 -0700 Randy Dunlap
<rdunlap@infradead.org> wrote:
>
> and if you are not using git but are using tarballs instead,
> where is the patch file?
Yeah, sorry I did not notice the error from kup. It should be there now.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-09 23:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 6:15 linux-next: Tree for Aug 9 Stephen Rothwell
2013-08-09 16:53 ` Randy Dunlap
2013-08-09 23:46 ` Stephen Rothwell [this message]
2013-08-10 22:15 ` linux-next: Tree for Aug 9 (staging/ozwpan) Randy Dunlap
2013-08-10 23:15 ` Randy Dunlap
2013-08-11 9:04 ` Gujare, Rupesh
2013-08-12 6:22 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 6:02 linux-next: Tree for Aug 9 Stephen Rothwell
2022-08-09 2:26 Stephen Rothwell
2021-08-09 11:39 Stephen Rothwell
2019-08-09 8:03 Stephen Rothwell
2019-08-10 16:23 ` Anders Roxell
2019-08-10 17:42 ` Christoph Hellwig
2018-08-09 8:06 Stephen Rothwell
2017-08-09 7:05 Stephen Rothwell
2016-08-09 3:52 Stephen Rothwell
2012-08-09 3:13 Stephen Rothwell
2011-08-09 3:57 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=20130810094642.c06a8f469f8601895c0f569f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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).