public inbox for b.a.t.m.a.n@lists.open-mesh.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.] RFC: Removing one indirection layer for patches
Date: Wed, 5 Dec 2012 12:24:35 +0100	[thread overview]
Message-ID: <20121205112435.GE26922@lunn.ch> (raw)
In-Reply-To: <20121205110642.GD27828@ritirata.org>

> I think the major advantage here is that, whenever a person sends a
> patch which is not going to work on older kernels, he must also send
> a patch for compat.h/c.

Hi Antonio

This is where you are fighting again the kernel process. The kernel
process does not care about older kernels, expect for patches flowing
into stable as bug fixes. So anybody from outside of BATMAN will not
supply such compat.[ch] changes.

Maybe its also time to evaluate the value of older kernels with newest
BATMAN? Is the pain worth the gain? 

	Andrew

  reply	other threads:[~2012-12-05 11:24 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 [this message]
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
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=20121205112435.GE26922@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox