public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <rdunlap@xenotime•net>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for May 21
Date: Tue, 22 May 2012 01:41:36 +1000	[thread overview]
Message-ID: <20120522014136.f2b26f8eddab621e8dcf8e22@canb.auug.org.au> (raw)
In-Reply-To: <4FBA5ABD.2070003@xenotime.net>

[-- Attachment #1: Type: text/plain, Size: 288 bytes --]

Hi Randy,

On Mon, 21 May 2012 08:09:49 -0700 Randy Dunlap <rdunlap@xenotime•net> wrote:
>
> no linux-next 20120521 patch file  :(

It was uploaded (it is scripted) so the mirroring must be broken, I guess.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-05-21 15:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  9:05 linux-next: Tree for May 21 Stephen Rothwell
2012-05-21 15:09 ` Randy Dunlap
2012-05-21 15:41   ` Stephen Rothwell [this message]
2012-05-21 15:44     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2026-05-21 12:08 Mark Brown
2025-05-21 11:20 Stephen Rothwell
2024-05-21  2:54 Stephen Rothwell
2021-05-21  6:44 Stephen Rothwell
2020-05-21 14:12 Stephen Rothwell
2020-05-21 15:09 ` Daniel Thompson
2019-05-21  5:14 Stephen Rothwell
2019-05-21  5:48 ` Masahiro Yamada
2019-05-21  6:18   ` Stephen Rothwell
2015-05-21  8:57 Stephen Rothwell
2014-05-21  7:50 Stephen Rothwell
2014-05-22 10:45 ` Michael Kerrisk
2014-05-22 22:06   ` Stephen Rothwell
2014-05-23  4:22     ` Michael Kerrisk (man-pages)
2013-05-21  5:03 Stephen Rothwell
2010-05-21  6:51 Stephen Rothwell
2009-05-21  8:14 Stephen Rothwell
2008-05-21  5:59 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=20120522014136.f2b26f8eddab621e8dcf8e22@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@xenotime$(echo .)net \
    /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