[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100428174748.GE3734@lunn.ch>
Date: Wed, 28 Apr 2010 19:47:48 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Mark Rankilor <reodge@...il.com>
Cc: Sven Eckelmann <sven.eckelmann@....de>, gregkh@...e.de,
andrew@...n.ch, lindner_marek@...oo.de, siwu@....tu-chemnitz.de,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: batman-adv: fixed comments to maintain 80
char limit
On Wed, Apr 28, 2010 at 09:33:40PM +0800, Mark Rankilor wrote:
> On 27 April 2010 17:53, Sven Eckelmann <sven.eckelmann@....de> wrote:
> > Your patch doesn't apply anymore. See
> > 1270341625-28764-1-git-send-email-luisbg@...ntu.com and follow ups [1].
>
> I had a look at the follow ups and saw this one:
>
> https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2010-April/002483.html
>
> So would it be best if I were to submit patches against the linux-next
> tree?
Hi Mark
I agree with Greg here. Patches against linux-next are no problem.
I'm responsible for merging changes in linux-next back into the batman
repo.
Having said that, before deciding to work on something, it probably is
worth looking at the batman repo. There is no point you reproducing
work we have already done, but is just queued up waiting to be sent to
Greg, or is in Gregs backlog of patches to apply.
Basically, i would not bother doing plain checkpatch patches. We are
mostly on top of that and any in linux-next are probably already fixed
in the batman repo.
However if you want to do some work with more meat on it, look for
security problems, memory leaks, race conditions, lockdep etc, such
patches would greatly be appreciated, independent of which repo they
are against.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists