All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: oneukum@suse.com
Cc: stephen@networkplumber.org, netdev@vger.kernel.org, bjorn@mork.no
Subject: Re: [PATCH] usbnet: make sure no NULL pointer is passed through
Date: Thu, 06 Apr 2017 13:19:07 -0700 (PDT)	[thread overview]
Message-ID: <20170406.131907.1888296039502840628.davem@davemloft.net> (raw)
In-Reply-To: <20170405121439.22523-1-oneukum@suse.com>

From: Oliver Neukum <oneukum@suse.com>
Date: Wed,  5 Apr 2017 14:14:39 +0200

> Coverity reports:
 ...
> It is valid to offer commands without a buffer, but then you need a size
> of zero. This should actually be checked.
> 
> Signed-off-by: Oliver Neukum <oneukum@suse.com>

Applied, thanks Oliver.

I had to apply this by hand via my inbox rather than using patchwork
because those coverity report delimiters cause patchwork to chop off
most of your commit message.

Just FYI...

  reply	other threads:[~2017-04-06 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 12:14 [PATCH] usbnet: make sure no NULL pointer is passed through Oliver Neukum
2017-04-06 20:19 ` David Miller [this message]
2017-04-10  9:01   ` Oliver Neukum

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=20170406.131907.1888296039502840628.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bjorn@mork.no \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stephen@networkplumber.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.