LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pnasrat@redhat.com>
To: Doug Maxey <dwm@austin.ibm.com>
Cc: yaboot-devel@ozlabs.org, Linux PowerPC List <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] yaboot: enable boot from iscsi target via ethernet devices on js20.
Date: Mon, 12 Jun 2006 10:46:38 -0400	[thread overview]
Message-ID: <1150123598.30925.9.camel@enki.eridu> (raw)
In-Reply-To: <200606012056.k51KuUOP008931@falcon10.austin.ibm.com>

On Thu, 2006-06-01 at 15:56 -0500, Doug Maxey wrote:
> On Tue, 16 May 2006 15:40:30 CDT, Doug Maxey wrote:

> >>Is the , always guaranteed to be there - eg if I have boot
> >>eth1:iscsi,ISCSIARGS  won't this check fail.
> >
> >Yes, with the above command line this would fail. 
> >
> >My point of reference are the bindings that we cannot yet talk about 
> >here, yet.  The device args would always be followed by a comma.  I suppose 
> >that we could just reference the string "iscsi", but then some wag 
> >would want to create some other property that included "iscsi" as a 
> >substring.  Maybe append a comma?
> 
> Any preferences on this?  

Both are kind of messy

> I have another, more radical solution.  
> 
> Adding a parser that understands the full device path and that can 
> return the elements neatly packaged.  Film at 11. 

This sounds to be the better way to do things - and is probably more
generally useful for other node types. Do you have any ideas on this?

Paul

      reply	other threads:[~2006-06-12 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28  6:05 [PATCH] yaboot: enable boot from iscsi target via ethernet devices on js20 Doug Maxey
2006-05-16 20:20 ` Paul Nasrat
2006-05-16 20:40   ` Doug Maxey
2006-06-01 20:56     ` Doug Maxey
2006-06-12 14:46       ` Paul Nasrat [this message]

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=1150123598.30925.9.camel@enki.eridu \
    --to=pnasrat@redhat.com \
    --cc=dwm@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=yaboot-devel@ozlabs.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