public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Trond Myklebust <trond.myklebust@fys•uio.no>
Cc: linux-next@vger•kernel.org, Ian Dall <ian@beware•dropbear.id.au>
Subject: Re: linux-next: nfs tree build failure
Date: Fri, 13 Mar 2009 09:07:58 +1100	[thread overview]
Message-ID: <20090313090759.e6507916.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1236884072.7179.37.camel@heimdal.trondhjem.org>

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

Hi Trond,

On Thu, 12 Mar 2009 14:54:32 -0400 Trond Myklebust <trond.myklebust@fys•uio.no> wrote:
>
> Should be fixed in today's tree. I appended the following patch:
> -----------------------------------------------------------------
> From: Trond Myklebust <Trond.Myklebust@netapp•com>
> Subject: NFS: Fix the fix to Bugzilla #11061, when IPv6 isn't defined...

Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

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

  reply	other threads:[~2009-03-12 22:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  0:26 linux-next: nfs tree build failure Stephen Rothwell
2009-03-12 18:54 ` Trond Myklebust
2009-03-12 22:07   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-16 10:55 Stephen Rothwell
2009-03-16 12:19 ` Trond Myklebust
2009-03-16 23:04   ` Stephen Rothwell
2009-12-04  0:36 Stephen Rothwell
2009-12-07  8:23 Stephen Rothwell
2009-12-07 22:32 ` Trond Myklebust
2009-12-07 22:53   ` Stephen Rothwell
2010-02-01  7:38 Stephen Rothwell
2010-02-01 14:15 ` Trond Myklebust
2010-02-01 23:24   ` 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=20090313090759.e6507916.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=ian@beware$(echo .)dropbear.id.au \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=trond.myklebust@fys$(echo .)uio.no \
    /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