public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <ordex@autistici.org>
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.] Implement DAT for IPv6
Date: Fri, 8 Mar 2013 11:14:02 +0100	[thread overview]
Message-ID: <20130308101402.GM1400@ritirata.org> (raw)
In-Reply-To: <CAP5XTDM1qdoUM8bhvL1xbWEvurA38SxN2ET4=uQ+vgQ_p_orvg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

On Fri, Mar 08, 2013 at 12:11:42PM +0200, Mihail Costea wrote:
> On 8 March 2013 11:33, Antonio Quartulli <ordex@autistici.org> wrote:
> > On Fri, Mar 08, 2013 at 11:22:37AM +0200, Mihail Costea wrote:
> >> Hi,
> >>
> >> I have created a patch for this, just that is quite big (~ 450 lines
> >> the whole patch, with signature, etc). It doesn't contain complex
> >> changes, just small changes from __be32 to (unsigned char *), a new
> >> parameter to functions in order to give the IP type and added
> >> comments.
> >>
> >> I've tested it with the snooping mechanism I added for IPv6 and it
> >> works ok (the snooping mechanism is not in this patch).
> >>
> >> What I wanted to ask is: it's ok to send a patch this big to the mailing list?
> >> I don't see how I could split it more because all I did is changed
> >> most of functions signatures and edit the code to support this
> >> changes.
> >
> >
> > The common rule is "one change per patch" meaning that if you can logically
> > split it (e.g. 1) add this 2) use this there and there 3) improve that) it would
> > be better to send more than one patch in one patchset.
> > Remember that each and every patch must compile.
> 
> I think I could split it into 2-3 parts logically:
> 1. Add the enum for IP types and add generic functions for comparing,
> calculating hash
> 2. Add generic debug message
> 3. Modify batadv_dat_entry  and all other functions to support both IPv4/IPv6
> 
> Some functions from 1./2. might not be used from start, but only
> later, when 3. is done.

Well, looking at the code it is easier to judge :)
Feel free to send your RFC/PATCH to the ml.

Cheers,

-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-08 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 10:59 [B.A.T.M.A.N.] Implement DAT for IPv6 Mihail Costea
2013-03-01 11:08 ` Antonio Quartulli
2013-03-01 11:38   ` Mihail Costea
2013-03-01 11:43     ` Antonio Quartulli
2013-03-01 11:56       ` Mihail Costea
2013-03-08  9:22         ` Mihail Costea
2013-03-08  9:33           ` Antonio Quartulli
2013-03-08 10:11             ` Mihail Costea
2013-03-08 10:14               ` Antonio Quartulli [this message]
2013-03-01 11:11 ` Antonio Quartulli
2013-03-01 11:41   ` Mihail Costea
2013-03-01 11:48     ` Antonio Quartulli

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=20130308101402.GM1400@ritirata.org \
    --to=ordex@autistici.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox