From: David Miller <davem@davemloft.net>
To: lucasb@mojatatu.com
Cc: netdev@vger.kernel.org, xiyou.wangcong@gmail.com,
jiri@resnulli.us, kernel@mojatatu.com
Subject: Re: [PATCH net 0/2] Prevent uncaught exceptions in tdc
Date: Sat, 17 Nov 2018 21:55:11 -0800 (PST) [thread overview]
Message-ID: <20181117.215511.1306664416132884569.davem@davemloft.net> (raw)
In-Reply-To: <1542407876-31310-1-git-send-email-lucasb@mojatatu.com>
From: Lucas Bates <lucasb@mojatatu.com>
Date: Fri, 16 Nov 2018 17:37:54 -0500
> This patch series addresses two potential bugs in tdc that can
> cause exceptions to be raised in certain circumstances. These
> exceptions are generally not handled, so instead we will prevent
> them from being raised.
Series applied.
prev parent reply other threads:[~2018-11-18 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 22:37 [PATCH net 0/2] Prevent uncaught exceptions in tdc Lucas Bates
2018-11-16 22:37 ` [PATCH net 1/2] tc-testing: tdc.py: ignore errors when decoding stdout/stderr Lucas Bates
2018-11-16 22:37 ` [PATCH net 2/2] tc-testing: tdc.py: Guard against lack of returncode in executed command Lucas Bates
2018-11-18 5:55 ` David Miller [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=20181117.215511.1306664416132884569.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=lucasb@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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