All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>
Cc: "<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC PATCH 0/5] Multiple interfaces support and lots of cmdline parsing
Date: Sat, 13 Jun 2009 10:17:46 +0200	[thread overview]
Message-ID: <4A3360AA.9060600@bfh.ch> (raw)
In-Reply-To: <1244865916.18551.20.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>



David Dillow wrote:
> On Fri, 2009-06-12 at 17:11 +0200, Seewer Philippe wrote:
> 
>> In order to ensure correct ip= lines I've added a lot of cmdline 
>> parseing and some mostly minor rewrites of actual netroot handlers.
>>
>> Thanks for reviewing (or accepting) the stuff,
>> Philippe
> 
> The series broke the NFS and NBD test suites, and I've not looked into
> why yet. It dies on the first test.

That's ... weird? I wasn't able to run the qemu/kvm test locally (don't 
ask, please). But I replicated the test arguments and ran them through 
the scripts. Should work, and nfsroot booted flawlessly Friday afternoon.

What's the die() error message?

> I've started digging in and trying to review some of the changes, but
> I'm just not going to have time before I leave; perhaps I can sneak away
> for a bit next week.

Thanks for looking into it!

> Perhaps a theory of operation/design document as to what the flow is
> expected to be, or what is handled where would help?

Is it really that complex? I'll write down my thoughts and add in a few 
examples.

Regards,
Philippe
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-13  8:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 15:11 [RFC PATCH 0/5] Multiple interfaces support and lots of cmdline parsing Seewer Philippe
     [not found] ` <4A327030.1000803-omB+W0Dpw2o@public.gmane.org>
2009-06-12 20:35   ` Warren Togami
     [not found]     ` <4A32BC07.2040704-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-12 20:49       ` Warren Togami
2009-06-13  4:05   ` David Dillow
     [not found]     ` <1244865916.18551.20.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-13  8:17       ` Seewer Philippe [this message]
     [not found]         ` <4A3360AA.9060600-omB+W0Dpw2o@public.gmane.org>
2009-06-13 12:24           ` David Dillow
     [not found]             ` <1244895898.18551.30.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-13 12:49               ` Seewer Philippe
     [not found]                 ` <4A33A062.7030208-omB+W0Dpw2o@public.gmane.org>
2009-06-15 16:19                   ` Warren Togami
     [not found]                     ` <4A36748E.7060408-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17  6:49                       ` Seewer Philippe
     [not found]                         ` <4A3891F7.8060501-omB+W0Dpw2o@public.gmane.org>
2009-06-17 14:24                           ` Harald Hoyer

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=4A3360AA.9060600@bfh.ch \
    --to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
    --cc=dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.