Hi Kevin.
Thanks for your feedback.
Looks like my team's project plans have changed, and there is no need to
pursue this further. We can work with the existing reason string.
Thanks,
Jack
On 01/09/18 02:24, Kevin Wolf wrote:
Am 08.01.2018 um 20:57 hat Jack Schwartz
Am 08.01.2018 um 20:57 hat Jack Schwartz geschrieben:
> Hi Kevin.
>
> On 2017-12-22 05:52, Kevin Wolf wrote:
> > Am 22.12.2017 um 01:11 hat Jack Schwartz geschrieben:
> > > BLOCK_IO_ERROR events currently contain a "reason" string which is
> > > strerror(errno) of the error. This enhancement
Hi Kevin.
On 2017-12-22 05:52, Kevin Wolf wrote:
Am 22.12.2017 um 01:11 hat Jack Schwartz geschrieben:
BLOCK_IO_ERROR events currently contain a "reason" string which is
strerror(errno) of the error. This enhancement provides those events with
the numeric errno value as well, since it is
Am 22.12.2017 um 01:11 hat Jack Schwartz geschrieben:
> BLOCK_IO_ERROR events currently contain a "reason" string which is
> strerror(errno) of the error. This enhancement provides those events with
> the numeric errno value as well, since it is easier to parse for error type
> than a string.
>
On 12/21/2017 06:11 PM, Jack Schwartz wrote:
BLOCK_IO_ERROR events currently contain a "reason" string which is
strerror(errno) of the error. This enhancement provides those events with
the numeric errno value as well, since it is easier to parse for error type
than a string.
NACK. Numeric
BLOCK_IO_ERROR events currently contain a "reason" string which is
strerror(errno) of the error. This enhancement provides those events with
the numeric errno value as well, since it is easier to parse for error type
than a string.
Signed-off-by: Jack Schwartz