Re: [PATCH 3/3] generic/237: fix filtering for expected failure message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 3/3] generic/237: fix filtering for expected failure message
From: "Theodore Ts'o" <tytso@xxxxxxx>
Date: Mon, 14 Apr 2014 22:08:36 -0400
Cc: Ext4 Developers List <linux-ext4@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20140414001408.GC27694@dastard>
User-agent: Mutt/1.5.23 (2014-03-12)

After looking at this more closely, this patch isn't needed.  It was a
configuration screw up on my end.

					- Ted

_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs

References:
- [PATCH] ext4: add a new spinlock i_raw_lock to protect the ext4's raw inode
  - From: Theodore Ts'o
- [PATCH 3/3] generic/237: fix filtering for expected failure message
  - From: Theodore Ts'o
- Re: [PATCH 3/3] generic/237: fix filtering for expected failure message
  - From: Dave Chinner

Prev by Date: Re: xfs readdir hang on for-next (3.15.0-rc1)
Next by Date: Re: [PATCH] xfs: unmount does not wait for shutdown during unmount
Previous by thread: Re: [PATCH 3/3] generic/237: fix filtering for expected failure message
Next by thread: [PATCH 2/3] generic/022: update expected output after the test was renamed
Index(es):
- Date
- Thread

[Index of Archives] [Linux XFS Devel] [Linux Filesystem Development] [Filesystem Testing] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux