public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net, netdev@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] net: writes past the end of the struct
Date: Wed, 11 Jul 2012 08:37:40 +0000	[thread overview]
Message-ID: <20120711083740.GC6056@mwanda> (raw)
In-Reply-To: <20120711.012745.2202204429130083377.davem@davemloft.net>

On Wed, Jul 11, 2012 at 01:27:45AM -0700, David Miller wrote:
> I asked him to fix some things, he did too much casting, but he never
> respun his patch set.  I definitely prefer this gets fixed his way.
> 

Oooo.  That's a clever trick.  Nice.

regards,
dan carpenter

      reply	other threads:[~2012-07-11  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  6:32 [patch -next] net: writes past the end of the struct Dan Carpenter
2012-07-11  8:27 ` David Miller
2012-07-11  8:37   ` Dan Carpenter [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=20120711083740.GC6056@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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