public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mark Rankilor <reodge@gmail.com>
Cc: Sven Eckelmann <sven.eckelmann@gmx.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 07:44:30 -0700	[thread overview]
Message-ID: <20100428144430.GA18945@suse.de> (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? Or is it necessary to work against the batman maint or master
> trees?
> 
> I'd much prefer if I could work against linux-next since if I wanted
> to do some work on another staging driver, then I wouldn't have to go
> and check out their repository.

Please work against linux-next, it is up to the batman developers to
also work against linux-next as well.  That levels the playing field for
everyone involved.

thanks,

greg k-h

  reply	other threads:[~2010-04-28 15:01 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 [this message]
2010-04-28 17:47     ` Andrew Lunn

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=20100428144430.GA18945@suse.de \
    --to=gregkh@suse.de \
    --cc=andrew@lunn.ch \
    --cc=devel@driverdev.osuosl.org \
    --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