linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: linux-can@vger.kernel.org
Subject: [PATCH 0/4] can: gw: Netlink related fixes
Date: Thu,  5 Jul 2012 14:19:54 +0200	[thread overview]
Message-ID: <cover.1341489914.git.tgraf@suug.ch> (raw)

Hi

These patches fix some Netlink quirks in the CAN gateway code.
Unfortunately I do not own any CAN hardware so this is compile
tested only. I'm fairly confident though as the changes are
mostly straight forward. I would appreciate if someone could
run them through a test suite or something though.


Thomas Graf (4):
  can: Don't bump nlmsg_len manually
  can: Use nla_policy to validate netlink attributes
  can: Properly fill the netlink header when responding to RTM_GETROUTE
  can: Remove pointless casts

 net/can/gw.c |   90 +++++++++++++++++++++------------------------------------
 1 files changed, 33 insertions(+), 57 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2012-07-05 12:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05 12:19 Thomas Graf [this message]
2012-07-05 12:19 ` [PATCH 1/4] can: Don't bump nlmsg_len manually Thomas Graf
2012-07-05 12:19 ` [PATCH 2/4] can: Use nla_policy to validate netlink attributes Thomas Graf
2012-07-05 12:19 ` [PATCH 3/4] can: Properly fill the netlink header when responding to RTM_GETROUTE Thomas Graf
2012-07-06 20:39   ` Oliver Hartkopp
2012-07-09  9:43     ` Thomas Graf
2012-07-09 16:28       ` Oliver Hartkopp
2012-07-07  9:18   ` Oliver Hartkopp
2012-07-10 15:29     ` Marc Kleine-Budde
2012-07-10 18:48       ` Oliver Hartkopp
2012-07-05 12:19 ` [PATCH 4/4] can: Remove pointless casts Thomas Graf
2012-07-05 16:16 ` [PATCH 0/4] can: gw: Netlink related fixes Oliver Hartkopp
2012-07-10 20:55 ` Marc Kleine-Budde

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=cover.1341489914.git.tgraf@suug.ch \
    --to=tgraf@suug.ch \
    --cc=linux-can@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).