From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: ebiederm@xmission.com, netdev@vger.kernel.org, serge@hallyn.com
Subject: Re: [PATCH net-next] scm: Don't use struct ucred in NETLINK_CB and struct scm_cookie.
Date: Fri, 07 Sep 2012 14:41:51 -0400 (EDT) [thread overview]
Message-ID: <20120907.144151.1366430170552241987.davem@davemloft.net> (raw)
In-Reply-To: <1347030446.2484.771.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 07 Sep 2012 17:07:26 +0200
> Seems fine to me, but I am not sure why you kept NETLINK_CREDS()
> defined/used once.
There are two remaining users, kernel/audit.c and scsi netlink.
next prev parent reply other threads:[~2012-09-07 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 4:20 [PATCH net-next] scm: Don't use struct ucred in NETLINK_CB and struct scm_cookie Eric W. Biederman
2012-09-07 15:07 ` Eric Dumazet
2012-09-07 18:41 ` David Miller [this message]
2012-09-07 21:25 ` Eric W. Biederman
2012-09-07 21:32 ` David Miller
2012-09-07 18:42 ` David Miller
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=20120907.144151.1366430170552241987.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=serge@hallyn.com \
/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