public inbox for
 help / color / mirror / Atom feed
From: "\"Ilija Kocho [Илија Кочо]\"" <>
To: "Michael Jones" <>,
	"Lambrecht Jürgen" <>
Cc: "" <>
Subject: Re: [PATCH] The DHCPREQUEST message should contain the same 'xid' as the DHCPOFFER message
Date: Sat, 15 Feb 2014 00:03:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12.02.2014 15:32, Michael Jones wrote:
> Jurgen,
> I typically put these in bugzilla with an explanation. That is where people look for patches before they are part of the source tree. As far as I can tell, it is the only way patches become part of the code base.

Indeed, Bugzilla is the preferred place for patch submission. Besides
discussion/collaboration forum, Bugzilla provides searchable database.
Patches and contributions is still available for but is depreciated.
Ref: . eCos Bugzilla shall
also forward the bug to patches mailing list if you select /Patches and
contributions/ component.


> Mike
> On Feb 12, 2014, at 6:08 AM, Lambrecht Jürgen <> wrote:
>> Hi,
>> I found a bug and fixed it, so I don't know if I need to use bugzilla 
>> for that?
>> In attach the patch.
>> file: net/common/current/src/dhcp_prot.c
>> According to RFC 2131 ( "The 
>> DHCPREQUEST message contains the same 'xid' as the DHCPOFFER message."
>> So in a DHCP DORA cycle (Discover-Offer-Request-Acknowledge) the same 
>> transaction ID should be used ('xid' in C code).
>> We never had problems with that, but now we have a strict customer..
>> Kind regards,
>> Jürgen
>> -- 
>> Jürgen Lambrecht
>> R&D Associate
>> Mobile: +32 499 644 531
>> Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
>> Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
>> Company number 0825.539.581 - RPR Kortrijk
>> <dhcp_prot.patch>

      reply	other threads:[~2014-02-15  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 13:08 Lambrecht Jürgen
2014-02-12 14:32 ` Michael Jones
2014-02-15  0:03   ` "Ilija Kocho [Илија Кочо]" [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).