linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: dsterba@suse.cz, YueHaibing <yuehaibing@huawei.com>,
	gregkh@linuxfoundation.org, jikos@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 -next] tty: ipwireless: Fix potential NULL pointer dereference
Date: Thu, 31 Jan 2019 13:34:16 +0100	[thread overview]
Message-ID: <252a300b-b665-84c8-7630-6e6753c0c31f@suse.cz> (raw)
In-Reply-To: <20190131123253.GC2900@suse.cz>

On 31. 01. 19, 13:32, David Sterba wrote:
> This should be mentioned in the changelog though, it's not obvious at
> all why just returning after a failure is ok and that the packet will be
> resent.

Agreed.

thanks,
-- 
js
suse labs

      reply	other threads:[~2019-01-31 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 10:30 [PATCH v2 -next] tty: ipwireless: Fix potential NULL pointer dereference YueHaibing
2019-01-30 15:58 ` Jiri Slaby
2019-01-31 12:32   ` David Sterba
2019-01-31 12:34     ` Jiri Slaby [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=252a300b-b665-84c8-7630-6e6753c0c31f@suse.cz \
    --to=jslaby@suse.cz \
    --cc=dsterba@suse.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuehaibing@huawei.com \
    /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).