public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Mark Rankilor <reodge@gmail.com>
Cc: Sven Eckelmann <sven.eckelmann@gmx.de>,
	gregkh@suse.de, andrew@lunn.ch, lindner_marek@yahoo.de,
	siwu@hrz.tu-chemnitz.de, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: batman-adv: fixed comments to maintain 80 char limit
Date: Wed, 28 Apr 2010 19:47:48 +0200	[thread overview]
Message-ID: <20100428174748.GE3734@lunn.ch> (raw)
In-Reply-To: <p2p90c96c971004280633t1188db65pd1bbe3679adf4d53@mail.gmail.com>

On Wed, Apr 28, 2010 at 09:33:40PM +0800, Mark Rankilor wrote:
> On 27 April 2010 17:53, Sven Eckelmann <sven.eckelmann@gmx.de> wrote:
> > Your patch doesn't apply anymore. See
> > 1270341625-28764-1-git-send-email-luisbg@ubuntu.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

      parent reply	other threads:[~2010-04-28 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  9:44 [PATCH] Staging: batman-adv: fixed comments to maintain 80 char limit Mark
2010-04-27  9:53 ` Sven Eckelmann
2010-04-28 13:33   ` Mark Rankilor
2010-04-28 14:44     ` Greg KH
2010-04-28 17:47     ` Andrew Lunn [this message]

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=20100428174748.GE3734@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=lindner_marek@yahoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reodge@gmail.com \
    --cc=siwu@hrz.tu-chemnitz.de \
    --cc=sven.eckelmann@gmx.de \
    /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