All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Victor Lowther <victor.lowther@gmail.com>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] Allow nonstandard ports when specifying network protocols.
Date: Fri, 12 Dec 2014 17:20:47 +0300	[thread overview]
Message-ID: <20141212172047.667d4f86@opensuse.site> (raw)
In-Reply-To: <CAMy6mNJGQufnLox=seMPZFNs5p2b1OqdGZpx4EsvGhKNRkiAZw@mail.gmail.com>

В Fri, 12 Dec 2014 07:01:31 -0600
Victor Lowther <victor.lowther@gmail.com> пишет:

> On Fri, Dec 12, 2014 at 5:54 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> > В Thu, 11 Dec 2014 13:58:04 -0600
> > Victor Lowther <victor.lowther@gmail.com> пишет:
> >
> >> There are usecases for running TFTP and HTTP on nonstandard ports.  This
> >> patch allows you to specify nonstandard ports with the following syntax:
> 
> [ snip ]
> 
> > No, that's wrong. grub_net_open_real should not have any hardcoded
> > dependencies on supported protocols. "pxe" and "pxe:" are just for
> > compatibility with legacy configuration. Any new code should rely on
> > protocol modules registration.
> 
> Er, it seemed like the natural place based on it being the only place where
> the parsing happens.
> 
> Where should I put it then?
> 

In the same function after we got server name. Just check whether it
has extra ',' and parse accordingly.

> > Do not overcomplicate things. You just need to add additional server
> > name parsing after protocol was extracted.
> 
> My familiarity with the grub codebase started on Tuesday -- I have no idea
> what is overcomplicated and what is not.
> 
> > And please also update documentation to indicate new syntax.
> 
> Where are the docs?  Nothing jumped out at me when grepping through the
> codebase.

docs/grub.texi. It is mentioned in 13.1 How to specify devices. Yes,
documentation needs some love.


      reply	other threads:[~2014-12-12 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 19:58 [PATCH] Allow nonstandard ports when specifying network protocols Victor Lowther
2014-12-12 11:54 ` Andrei Borzenkov
2014-12-12 13:01   ` Victor Lowther
2014-12-12 14:20     ` Andrei Borzenkov [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=20141212172047.667d4f86@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=victor.lowther@gmail.com \
    /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.