netdev - Re: [RFC PATCH net-next 0/9] tipc: misc updates for 3.7

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]

Message-Id: <20120820.022743.465143033806832968.davem@davemloft.net>
Date:	Mon, 20 Aug 2012 02:27:43 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	paul.gortmaker@...driver.com
Cc:	netdev@...r.kernel.org, jon.maloy@...csson.com,
	ying.xue@...driver.com
Subject: Re: [RFC PATCH net-next 0/9] tipc: misc updates for 3.7

From: Paul Gortmaker <paul.gortmaker@...driver.com>
Date: Thu, 16 Aug 2012 18:09:05 -0400

> This series gets some more largely trivial things out of
> the way.  Most interesting are:
> 
> 1) fix lockdep splat from bearer init by pushing the setup
>    off to schedule_work.
> 
> 2) simplification of configuration by removal of a couple of
>    tuning knobs which used to have low default values.
> 
> The remainder are largely innocuous, I think.  I did wonder
> if there was an alternate/better way to handle the splat though.
> 
> I've done my own local testing of this series on today's net-next
> commit 2ea214929d601 ("Merge branch 'for-davem' ... wireless-next")
> 
> I'll wait a couple of days to allow for any possible feedback and
> change requests, and then send a pull request after that.

All applied, thanks Paul.

It's less useful for you to build the GIT tree "later", at least for
me.

If the patches are good and there is no feedback asking for changes,
I want to be able to just pull them into my tree immediately as I
did here.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html