mbox

pull request: batman-adv 2011-01-29

Message ID 201101301036.57928.sven@narfation.org (mailing list archive)
State Not Applicable, archived
Headers

Pull-request

git://git.open-mesh.org/ecsv/linux-merge.git batman-adv/merge-oopsonly

Message

Sven Eckelmann Jan. 30, 2011, 9:36 a.m. UTC 
  On Sunday 30 January 2011 04:08:15 David Miller wrote:
> I'm not taking 13 patches in one big bunch at this point post-merge-window,
> now matter what they are.

Thats why I tried to provide the 6 bug fixes only version without polishing - 
I could also try to reduce it to a 4 critical version (oops/memleak patches 
only without protocol implementation failures).

Or is the problem that I tried to get them in as pull request?

thanks,
	Sven


Here are the oops/memleak patches only:

The following changes since commit aa0adb1a85e159cf57f0e11282bc6c9e3606a5f3:

  batman-adv: Use "__attribute__" shortcut macros (2011-01-16 03:25:19 +0100)

are available in the git repository at:
  git://git.open-mesh.org/ecsv/linux-merge.git batman-adv/merge-oopsonly

Linus Lüssing (1):
      batman-adv: Fix kernel panic when fetching vis data on a vis server

Sven Eckelmann (3):
      batman-adv: Remove vis info on hashing errors
      batman-adv: Remove vis info element in free_info
      batman-adv: Make vis info stack traversal threadsafe

 net/batman-adv/vis.c |   14 ++++++++------
 1 files changed, 8 insertions(+), 6 deletions(-)

Comments

David Miller Jan. 30, 2011, 11:56 a.m. UTC | #1 
From: Sven Eckelmann <sven@narfation.org>
Date: Sun, 30 Jan 2011 10:36:54 +0100

> On Sunday 30 January 2011 04:08:15 David Miller wrote:
>> I'm not taking 13 patches in one big bunch at this point post-merge-window,
>> now matter what they are.
> 
> Thats why I tried to provide the 6 bug fixes only version without polishing - 
> I could also try to reduce it to a 4 critical version (oops/memleak patches 
> only without protocol implementation failures).
> 
> Or is the problem that I tried to get them in as pull request?

Please make a new patch series posting and pull request with only the most
important fixes included.

Once I accept those, you can send me a second patch series and pull
request with the cleanups done on top.  Just mention explicitly in
this second pull request that there is a dependency upon the initial
bug fixes.  In this way I will know to pull net-2.6 into net-next-2.6
first, and then pull from your tree into net-next-2.6

Thanks.