From: Thomas Graf <tgraf@suug.ch>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@osdl.org>,
Shailabh Nagar <nagar@watson.ibm.com>,
Balbir Singh <balbir@in.ibm.com>, Jay Lan <jlan@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] taskstats: uglify^Woptimize reply assembling
Date: Thu, 2 Nov 2006 11:14:30 +0100 [thread overview]
Message-ID: <20061102101430.GG12964@postel.suug.ch> (raw)
In-Reply-To: <20061101182512.GA444@oleg>
* Oleg Nesterov <oleg@tv-sign.ru> 2006-11-01 21:25
> Thomas, we are doing genlmsg_cancel() before nlmsg_free(), this is
> not necessary. Unless you have evil plans to complicate genetlink
> we can remove a little bit of code, what do you think?
genlmsg_cancel() is only required in error paths for dumping
procedures.
prev parent reply other threads:[~2006-11-02 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 18:25 [PATCH 0/2] taskstats: uglify^Woptimize reply assembling Oleg Nesterov
2006-11-01 20:30 ` Shailabh Nagar
2006-11-02 17:48 ` [PATCH] fix Documentation/accounting/getdelays.c buf size Oleg Nesterov
2006-11-02 5:07 ` [PATCH 0/2] taskstats: uglify^Woptimize reply assembling Balbir Singh
2006-11-02 10:14 ` Thomas Graf [this message]
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=20061102101430.GG12964@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=jlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nagar@watson.ibm.com \
--cc=oleg@tv-sign.ru \
/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