All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20240614054534.GA9969@lst.de>

diff --git a/a/1.txt b/N1/1.txt
index 6c954db..0949493 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,3 +4,7 @@ On Thu, Jun 13, 2024 at 09:10:37PM +0000, Gulam Mohamed wrote:
 > Please let us know your comments.
 
 I still think simply setting the rundown state is the better approach..
+
+
+-- 
+Mailing list info: https://lists.linux.it/listinfo/ltp
diff --git a/a/content_digest b/N1/content_digest
index 2d4d1aa..e9a47b4 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,18 +2,18 @@
  "ref\0202406112130.a572f72-oliver.sang@intel.com\0"
  "ref\0IA1PR10MB7240B2686664744DB0D8867F98C12@IA1PR10MB7240.namprd10.prod.outlook.com\0"
  "From\0hch@lst.de <hch@lst.de>\0"
- "Subject\0Re: [PATCH V4 for-6.10/block] loop: Fix a race between loop detach and loop open\0"
+ "Subject\0Re: [LTP] [PATCH V4 for-6.10/block] loop: Fix a race between loop detach and loop open\0"
  "Date\0Fri, 14 Jun 2024 07:45:34 +0200\0"
  "To\0Gulam Mohamed <gulam.mohamed@oracle.com>\0"
- "Cc\0kernel test robot <oliver.sang@intel.com>"
-  oe-lkp@lists.linux.dev <oe-lkp@lists.linux.dev>
+ "Cc\0axboe@kernel.dk <axboe@kernel.dk>"
   lkp@intel.com <lkp@intel.com>
-  linux-block@vger.kernel.org <linux-block@vger.kernel.org>
-  ltp@lists.linux.it <ltp@lists.linux.it>
   linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  linux-block@vger.kernel.org <linux-block@vger.kernel.org>
   yukuai1@huaweicloud.com <yukuai1@huaweicloud.com>
+  kernel test robot <oliver.sang@intel.com>
+  oe-lkp@lists.linux.dev <oe-lkp@lists.linux.dev>
   hch@lst.de <hch@lst.de>
- " axboe@kernel.dk <axboe@kernel.dk>\0"
+ " ltp@lists.linux.it <ltp@lists.linux.it>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Jun 13, 2024 at 09:10:37PM +0000, Gulam Mohamed wrote:\n"
@@ -21,6 +21,10 @@
  "> The tst_detach_device_by_fd() in LTP test case will open the loop device and repeatedly checks for error code ENXIO. As the new approach, as I mentioned above, will defer the detach to last close and the last close happens *only* when the LTP test function tst_detach_device_by_fd() returns, the test will obviously fail. So, Can you please modify the LTP test case to accommodate the new behaviour of kernel code for loop detach?\n"
  "> Please let us know your comments.\n"
  "\n"
- I still think simply setting the rundown state is the better approach..
+ "I still think simply setting the rundown state is the better approach..\n"
+ "\n"
+ "\n"
+ "-- \n"
+ Mailing list info: https://lists.linux.it/listinfo/ltp
 
-24d845d4ad98d79bd3cbcc66352822ee224c08b49d4fe8bb6037985025be59e4
+b51116d4c565589113022140e8dcc6297da07477c612af67f4829f2e4a0a969f

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.