From: Marc Kleine-Budde <mkl@pengutronix.de>
To: David Miller <davem@davemloft.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: pull-request: can-next 2012-07-11
Date: Wed, 11 Jul 2012 16:05:25 +0200 [thread overview]
Message-ID: <4FFD8825.2060109@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Hello David,
the fourth pull request for upcoming v3.6 net-next consist of a series
of can_gw netlink cleanups done by Thomas Graf.
regards, Marc
--
The following changes since commit 061a5c316b6526dbc729049a16243ec27937cc31:
Merge branch 'davem-next.r8169' of git://violet.fr.zoreil.com/romieu/linux (2012-07-09 16:09:47 -0700)
are available in the git repository at:
git://gitorious.org/linux-can/linux-can-next.git for-davem
for you to fetch changes up to 5d91efa8dd8ced8647798d067f2ac8125194be58:
can: gw: Remove pointless casts (2012-07-10 22:36:17 +0200)
----------------------------------------------------------------
Thomas Graf (4):
can: gw: Don't bump nlmsg_len manually
can: gw: Use nla_policy to validate netlink attributes
can: gw: Properly fill the netlink header when responding to RTM_GETROUTE
can: gw: Remove pointless casts
net/can/gw.c | 90 +++++++++++++++++++++-------------------------------------
1 file changed, 33 insertions(+), 57 deletions(-)
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2012-07-11 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 14:05 Marc Kleine-Budde [this message]
2012-07-12 15:19 ` pull-request: can-next 2012-07-11 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=4FFD8825.2060109@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).