mm/memory-failure: remove confusing initialization to count
authorMiaohe Lin <linmiaohe@huawei.com>
Wed, 12 Jun 2024 07:18:28 +0000 (15:18 +0800)
committerAndrew Morton <akpm@linux-foundation.org>
Thu, 4 Jul 2024 02:30:11 +0000 (19:30 -0700)
It's meaningless and confusing to init local variable count to 1.  Remove
it.  No functional change intended.

Link: https://lkml.kernel.org/r/20240612071835.157004-7-linmiaohe@huawei.com
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Cc: Borislav Petkov (AMD) <bp@alien8.de>
Cc: David Hildenbrand <david@redhat.com>
Cc: kernel test robot <lkp@intel.com>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>
Cc: Tony Luck <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
mm/memory-failure.c

index ec482524158e882b17beff49e4af2317d304ad89..339752d768d8fd9cb05276eb1a2bc0ea5b8077ca 100644 (file)
@@ -2542,7 +2542,7 @@ int unpoison_memory(unsigned long pfn)
        struct folio *folio;
        struct page *p;
        int ret = -EBUSY, ghp;
-       unsigned long count = 1;
+       unsigned long count;
        bool huge = false;
        static DEFINE_RATELIMIT_STATE(unpoison_rs, DEFAULT_RATELIMIT_INTERVAL,
                                        DEFAULT_RATELIMIT_BURST);