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.] RFC: Removing one indirection layer for patches
Date: Wed, 5 Dec 2012 13:05:55 +0100 [thread overview]
Message-ID: <20121205120555.GG27828@ritirata.org> (raw)
In-Reply-To: <20121205113927.GF26922@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
On Wed, Dec 05, 2012 at 12:39:27PM +0100, Andrew Lunn wrote:
> > The biggest different is the "lets install a whole kernel to test this change"
> > methodology ;)
>
> Yes, i generally do that, test a whole kernel, not a module. But...
>
> > Usually (please correct me) batman-adv is developed outside the kernel because
> > it is easier to test stuff and it worked till now. No one of us wants to port
> > the latest OpenWrt to the -rc kernel to test stuff ;)
>
> Do you actually need to port to OpenWrt?
>
> How i work is build a kernel, with everything i need built in. No
> modules. Then tftpboot the kernel, and use the rootfs from the
> disk. Why not do the same with OpenWrt?
>
> > > It seems like the biggest problem is the late feedback from David
> > > S. Miller, et al, about patches. Getting this feedback earlier in the
> > > life of a patchset would easy people lives.
> >
> > Partly, David switches horses relative often. So an early feedback is not as
> > valuable as it sounds.
>
> O.K. I've not paid enough attention to his comments to know this.
>
> > > For Marvell work, we post all our patches to the linux arm kernel
> > > list, where the ARM maintainers will see the patches. All patches go
> > > there, in all stages of their life, from early RFCs, to patches we
> > > want the upstream maintainers to take in a following pull request.
> > > Thus there is the possibility to get early feedback from the upstream
> > > maintainers and avoid most last minutes surprises.
> > >
> > > So maybe it would be good to stop using BATMAN mailing list for
> > > patches and instead use netdev. Or at least CC: netdev.
> >
> > I'll tried it in the netdev_alloc/standard interface patchset but I got only a
> > surprised "where is the pull request?" reply.
>
> Humm, interesting. Is that maybe because BATMAN only ever sends pull
> requests to the list?
I think the main reason for this reply is that David was directly CCed.
I think we got no feedbacks because we are not used to send patches over
netdev "asking" for them.
However, if you look at all the other network "subtrees", everybody just sends
pull requests only. I think patches against "subtrees" are rarely sent to
netdev for feedback.
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-05 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 21:50 [B.A.T.M.A.N.] RFC: Removing one indirection layer for patches Sven Eckelmann
2012-12-04 23:01 ` Antonio Quartulli
2012-12-05 9:45 ` Sven Eckelmann
2012-12-05 10:35 ` Andrew Lunn
2012-12-05 11:06 ` Antonio Quartulli
2012-12-05 11:24 ` Andrew Lunn
2012-12-05 11:32 ` Antonio Quartulli
2012-12-05 11:23 ` Sven Eckelmann
2012-12-05 11:39 ` Andrew Lunn
2012-12-05 12:05 ` Antonio Quartulli [this message]
2012-12-05 13:12 ` Simon Wunderlich
-- strict thread matches above, loose matches on Subject: below --
2012-12-05 17:40 Marek Lindner
2012-12-05 17:50 ` Sven Eckelmann
2012-12-05 18:04 ` Sven Eckelmann
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=20121205120555.GG27828@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