From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, tgraf@redhat.com
Subject: Re: [PATCH] genetlink: introduce pre/post methods
Date: Wed, 18 Feb 2009 17:33:34 -0800 (PST) [thread overview]
Message-ID: <20090218.173334.110224475.davem@davemloft.net> (raw)
In-Reply-To: <1234515865.4204.16.camel@johannes.local>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri, 13 Feb 2009 10:04:25 +0100
> Sometimes doit/dumpit callbacks for a given family consist
> of quite a bit of boilerplate code, for example locking or
> generic sanity checks on messages.
>
> These methods allow writing the boilerplate code just once
> instead of copying it into all handlers.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
I'm fine with this:
Acked-by: David S. Miller <davem@davemloft.net>
Feel free to toss it into the wireless tree.
prev parent reply other threads:[~2009-02-19 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 9:04 [PATCH] genetlink: introduce pre/post methods Johannes Berg
2009-02-19 1:33 ` David Miller [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=20090218.173334.110224475.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@redhat.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