All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] vis packet format
Date: Thu, 4 Mar 2010 10:03:55 +0100	[thread overview]
Message-ID: <20100304090355.GB29010@lunn.ch> (raw)
In-Reply-To: <20100303233946.GA24284@Linus-Debian>

On Thu, Mar 04, 2010 at 12:39:46AM +0100, Linus L??ssing wrote:
> Hi,
> 
> Marek and I have been chatting a little about the buggy vis raw
> output yesterday. And there was either the option to sort the
> mixed list on the receiving vis server or on the sender already.
> For the second option there was also the idea of changing the vis
> packet format accordingly to also save some more overhead.

A comment about the mainline development process. Changes which are
clearly bug fixes we should be able to get merged into the -rc kernels
at any time. Changes which look like development work have to wait
until the next merge window.

This vis problem about it showing the wrong interface will be in
-rc1. It would be nice to get it fixed. We are more likely to get such
a fix accepted if it is small and looks like a bug fix. I expect it
will get rejected if it is big and looks like development work.

So can we develop two fixes? Something small and simple for -rc1 and
an optimizing fix which will go into linux-next and then into mainline
during the next merge window?

       Andrew

  parent reply	other threads:[~2010-03-04  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 23:39 [B.A.T.M.A.N.] vis packet format Linus Lüssing
2010-03-04  0:06 ` Linus Lüssing
2010-03-04  9:03 ` Andrew Lunn [this message]
2010-03-04 16:01   ` Linus Lüssing
2010-03-04 16:03     ` Marek Lindner

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=20100304090355.GB29010@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.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.