From: Oliver Neukum <oneukum@suse.com>
To: David Miller <davem@davemloft.net>
Cc: bjorn@mork.no, stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH] usbnet: make sure no NULL pointer is passed through
Date: Mon, 10 Apr 2017 11:01:02 +0200 [thread overview]
Message-ID: <1491814862.1496.1.camel@suse.com> (raw)
In-Reply-To: <20170406.131907.1888296039502840628.davem@davemloft.net>
Am Donnerstag, den 06.04.2017, 13:19 -0700 schrieb David Miller:
> 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.
>
Hi,
thanks. That is not good. It seems to me that a Coverity report
should be in the change log. Do you have suggestions how to do
this in a friendly manner?
Regards
Oliver
prev parent reply other threads:[~2017-04-10 9:02 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
2017-04-10 9:01 ` Oliver Neukum [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=1491814862.1496.1.camel@suse.com \
--to=oneukum@suse.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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.