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,
helpdesk@kernel.org
Subject: Re: linux-next: Tree for Sep 12
Date: Sat, 13 Sep 2014 11:59:50 +1000 [thread overview]
Message-ID: <20140913115950.0331951e@canb.auug.org.au> (raw)
In-Reply-To: <54132FC7.1080004@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Hi Randy,
On Fri, 12 Sep 2014 10:39:19 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 09/12/14 00:38, Stephen Rothwell wrote:
> >
> > Changes since 20140911:
> >
> ---------------------------------------------------------------------
> >
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > (patches at http://www.kernel.org/pub/linux/kernel/next/ ).
>
> No patch tarball?
Hmm, sorry I didn't notice this:
Pushing patch to kernel.org ...
patch-v3.17-rc4-next-20140912 (1/1)
100 % 2,494.2 KiB / 15.7 MiB = 0.155 1.9 MiB/s 0:08
2554072 [==================================================] 100%
Compressing: .gz: 100% .xz: 100%
Calculating sha256 for /pub/linux/kernel/next/patch-v3.17-rc4-next-20140912.gz ... logged.
Cannot open lock file
Helpdesk folks: is this expected? This is a put of
patch-v3.17-rc4-next-20140912.xz using kup.
Randy: I will try to reupload the patch
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-13 1:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-7062@linuxfoundation.org>
2014-09-12 7:38 ` linux-next: Tree for Sep 12 Stephen Rothwell
2014-09-12 17:39 ` Randy Dunlap
2014-09-13 1:59 ` Stephen Rothwell [this message]
[not found] ` <rt-3.8.13-21049-1410573601-1407.7062-3-0@linuxfoundation.org>
[not found] ` <20140913120848.243db589@canb.auug.org.au>
2014-09-13 2:08 ` [Kernel.org Helpdesk #7062] AutoReply: " sfr@canb.auug.org.au via RT
2014-09-13 2:09 ` Stephen Rothwell
2023-09-12 5:26 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 10:09 Stephen Rothwell
2018-09-12 4:39 Stephen Rothwell
2017-09-12 4:16 Stephen Rothwell
2017-09-12 13:18 ` Sergey Senozhatsky
2017-09-14 16:48 ` Andy Lutomirski
2017-09-14 22:31 ` Sergey Senozhatsky
2016-09-12 5:42 Stephen Rothwell
2015-09-12 5:09 Stephen Rothwell
2013-09-12 4:34 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=20140913115950.0331951e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=helpdesk@kernel.org \
--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).