All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] NET: ipv6, fix potential null dereference
Date: Sun, 10 Jan 2010 12:37:08 +0100	[thread overview]
Message-ID: <4B49BBE4.2010502@gmail.com> (raw)
In-Reply-To: <4B49B463.3010502@gmail.com>

On 01/10/2010 12:05 PM, Jiri Slaby wrote:
> And until people start to look at the reports for their stuff
> themselves, they will get bogus fixes from others. And they have to nack
> them, indeed.

Plus people sending such patches should plug in their brain. The tty
case is clearly bogus.

  reply	other threads:[~2010-01-10 11:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 10:35 [PATCH 1/1] NET: ipv6, fix potential null dereference Alexey Dobriyan
2010-01-10 10:38 ` Jiri Slaby
2010-01-10 10:47   ` Alexey Dobriyan
2010-01-10 11:05     ` Jiri Slaby
2010-01-10 11:37       ` Jiri Slaby [this message]
2010-01-10 10:43 ` [PATCH 1/1] NET: ipv6, remove unnecessary check Jiri Slaby
2010-01-10 21:28   ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2010-01-10  9:06 [PATCH 1/1] NET: ipv6, fix potential null dereference Jiri Slaby

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=4B49BBE4.2010502@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=adobriyan@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.