From: keith.busch@intel.com (Keith Busch)
Subject: Questions on Interruption handling
Date: Tue, 20 Jan 2015 22:35:47 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1501202220340.15481@localhost.lm.intel.com> (raw)
In-Reply-To: <CAMjVwgRcrWqNO4hdgnTPG2VbASCz5b_y3r6cX2oGuiA2SFcSuA@mail.gmail.com>
The ECN request was sent 24 October, which was after the 1.2 revision
was under review for ratification.
On Tue, 20 Jan 2015, Angelo Brito wrote:
> Hi all,
>
> So I just checked that a new version of the Specification 1.2 was
> released in November and no modifications were done for this issue.
>
> Do you guys have any news?
>
>
> Regards,
> Angelo Silva Brito.
next prev parent reply other threads:[~2015-01-20 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 17:43 Questions on Interruption handling Angelo Brito
2014-10-22 18:10 ` Keith Busch
2014-10-23 13:30 ` Angelo Brito
2014-10-23 14:26 ` Angelo Brito
2014-10-23 16:53 ` Matthew Wilcox
2014-10-24 16:51 ` Angelo Brito
2014-10-24 17:49 ` Matthew Wilcox
2014-10-24 17:59 ` Angelo Brito
2015-01-20 19:13 ` Angelo Brito
2015-01-20 22:35 ` Keith Busch [this message]
2015-01-21 0:08 ` Angelo Brito
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=alpine.LNX.2.00.1501202220340.15481@localhost.lm.intel.com \
--to=keith.busch@intel.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