From: David Miller <davem@davemloft.net>
To: randy.dunlap@oracle.com
Cc: geert@linux-m68k.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: linux-next: Tree for March 10 (crypto & NLATTR)
Date: Tue, 10 Mar 2009 13:17:00 -0700 (PDT) [thread overview]
Message-ID: <20090310.131700.40129006.davem@davemloft.net> (raw)
In-Reply-To: <49B6C8BF.8010105@oracle.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
Date: Tue, 10 Mar 2009 13:08:31 -0700
> I'll have to let David or Herbert answer that. From my quick look
> at the code, I don't see much use for nlattr.c when CONFIG_NET
> is not enabled.
We want to use the netlink attribute parsers even in non-networking
code, that's what he's trying to do here.
next prev parent reply other threads:[~2009-03-10 20:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 8:55 linux-next: Tree for March 10 Stephen Rothwell
2009-03-10 9:33 ` Wim Van Sebroeck
2009-03-10 11:07 ` Stephen Rothwell
2009-03-10 14:12 ` Next 10: Badness at mm/allocpercpu.c:123 Sachin P. Sant
2009-03-11 4:16 ` Sachin P. Sant
2009-03-11 5:53 ` [GIT PATCH tj-percpu] percpu: fix spurious alignment WARN in legacy SMP percpu allocator Tejun Heo
2009-03-11 5:54 ` [RESEND GIT " Tejun Heo
2009-03-11 6:48 ` Sachin P. Sant
2009-03-11 9:31 ` Ingo Molnar
2009-03-11 8:50 ` Next 10: Badness at mm/allocpercpu.c:123 AA
2009-03-11 8:53 ` where should I map 0x8000,0000 ~ 0xfc00,0000 to ? AA
2009-03-10 18:57 ` linux-next: Tree for March 10 (crypto & NLATTR) Randy Dunlap
2009-03-10 19:56 ` Geert Uytterhoeven
2009-03-10 20:08 ` Randy Dunlap
2009-03-10 20:17 ` David Miller [this message]
2009-03-11 1:07 ` Herbert Xu
2009-03-11 12:25 ` Geert Uytterhoeven
2009-03-11 16:55 ` Randy Dunlap
2009-03-10 18:59 ` [PATCH -next] staging/p9auth: fix dependency/build error Randy Dunlap
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=20090310.131700.40129006.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).