lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 28 Apr 2010 21:33:40 +0800
From:	Mark Rankilor <reodge@...il.com>
To:	Sven Eckelmann <sven.eckelmann@....de>
Cc:	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 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? 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.

Regards,
Mark
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ