Am 16.04.2015 um 15:20 schrieb Paolo Bonzini:
On 16/04/2015 14:58, Peter Lieven wrote:
On 16/04/2015 14:18, Peter Lieven wrote:
We need this to support SCSI_STATUS_TASK_SET_FULL.
Any reason apart from the missing constant?
No, but I wanted to avoid starting checking for constants that were
On 16/04/2015 14:18, Peter Lieven wrote:
We need this to support SCSI_STATUS_TASK_SET_FULL.
Any reason apart from the missing constant?
Paolo
Signed-off-by: Peter Lieven p...@kamp.de
---
configure | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/configure
Am 16.04.2015 um 14:33 schrieb Paolo Bonzini:
On 16/04/2015 14:18, Peter Lieven wrote:
We need this to support SCSI_STATUS_TASK_SET_FULL.
Any reason apart from the missing constant?
No, but I wanted to avoid starting checking for constants that were added
shortly after this.
You can't
We need this to support SCSI_STATUS_TASK_SET_FULL.
Signed-off-by: Peter Lieven p...@kamp.de
---
configure | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
index 6969f6f..f73b8d0 100755
--- a/configure
+++ b/configure
@@ -3630,15 +3630,15 @@ if
On 16/04/2015 14:58, Peter Lieven wrote:
On 16/04/2015 14:18, Peter Lieven wrote:
We need this to support SCSI_STATUS_TASK_SET_FULL.
Any reason apart from the missing constant?
No, but I wanted to avoid starting checking for constants that were
added shortly after this.
You can't check