From: Randy Dunlap <rdunlap@infradead.org> To: linux-kernel@vger.kernel.org Cc: Randy Dunlap <rdunlap@infradead.org>, Mikulas Patocka <mpatocka@redhat.com>, Alasdair Kergon <agk@redhat.com>, Mike Snitzer <snitzer@redhat.com>, dm-devel@redhat.com, Heiko Carstens <hca@linux.ibm.com>, Vasily Gorbik <gor@linux.ibm.com>, Christian Borntraeger <borntraeger@de.ibm.com>, linux-s390@vger.kernel.org Subject: [PATCH] md: dm-writeback: add __noreturn to BUG-ging function Date: Fri, 13 Nov 2020 14:52:28 -0800 [thread overview] Message-ID: <20201113225228.20563-1-rdunlap@infradead.org> (raw) Building on arch/s390/ flags this as an error, so add the __noreturn attribute modifier to prevent the build error. cc1: some warnings being treated as errors ../drivers/md/dm-writecache.c: In function 'persistent_memory_claim': ../drivers/md/dm-writecache.c:323:1: error: no return statement in function returning non-void [-Werror=return-type] Fixes: 48debafe4f2f ("dm: add writecache target") Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Mikulas Patocka <mpatocka@redhat.com> Cc: Alasdair Kergon <agk@redhat.com> Cc: Mike Snitzer <snitzer@redhat.com> Cc: dm-devel@redhat.com Cc: Heiko Carstens <hca@linux.ibm.com> Cc: Vasily Gorbik <gor@linux.ibm.com> Cc: Christian Borntraeger <borntraeger@de.ibm.com> Cc: linux-s390@vger.kernel.org --- drivers/md/dm-writecache.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20201113.orig/drivers/md/dm-writecache.c +++ linux-next-20201113/drivers/md/dm-writecache.c @@ -317,7 +317,7 @@ err1: return r; } #else -static int persistent_memory_claim(struct dm_writecache *wc) +static int __noreturn persistent_memory_claim(struct dm_writecache *wc) { BUG(); }
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org> To: linux-kernel@vger.kernel.org Cc: linux-s390@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>, Mike Snitzer <snitzer@redhat.com>, Heiko Carstens <hca@linux.ibm.com>, Randy Dunlap <rdunlap@infradead.org>, Christian Borntraeger <borntraeger@de.ibm.com>, dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>, Alasdair Kergon <agk@redhat.com> Subject: [dm-devel] [PATCH] md: dm-writeback: add __noreturn to BUG-ging function Date: Fri, 13 Nov 2020 14:52:28 -0800 [thread overview] Message-ID: <20201113225228.20563-1-rdunlap@infradead.org> (raw) Building on arch/s390/ flags this as an error, so add the __noreturn attribute modifier to prevent the build error. cc1: some warnings being treated as errors ../drivers/md/dm-writecache.c: In function 'persistent_memory_claim': ../drivers/md/dm-writecache.c:323:1: error: no return statement in function returning non-void [-Werror=return-type] Fixes: 48debafe4f2f ("dm: add writecache target") Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Mikulas Patocka <mpatocka@redhat.com> Cc: Alasdair Kergon <agk@redhat.com> Cc: Mike Snitzer <snitzer@redhat.com> Cc: dm-devel@redhat.com Cc: Heiko Carstens <hca@linux.ibm.com> Cc: Vasily Gorbik <gor@linux.ibm.com> Cc: Christian Borntraeger <borntraeger@de.ibm.com> Cc: linux-s390@vger.kernel.org --- drivers/md/dm-writecache.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20201113.orig/drivers/md/dm-writecache.c +++ linux-next-20201113/drivers/md/dm-writecache.c @@ -317,7 +317,7 @@ err1: return r; } #else -static int persistent_memory_claim(struct dm_writecache *wc) +static int __noreturn persistent_memory_claim(struct dm_writecache *wc) { BUG(); } -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2020-11-13 22:52 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-13 22:52 Randy Dunlap [this message] 2020-11-13 22:52 ` [dm-devel] [PATCH] md: dm-writeback: add __noreturn to BUG-ging function Randy Dunlap 2020-11-16 7:30 ` Christian Borntraeger 2020-11-16 7:30 ` [dm-devel] " Christian Borntraeger 2020-11-16 23:00 ` Randy Dunlap 2020-11-16 23:00 ` [dm-devel] " Randy Dunlap 2020-11-17 16:31 ` Mike Snitzer 2020-11-17 16:31 ` [dm-devel] " Mike Snitzer 2020-11-18 15:49 ` Mike Snitzer 2020-11-18 15:49 ` [dm-devel] " Mike Snitzer 2020-11-18 16:07 ` Mike Snitzer 2020-11-18 16:07 ` [dm-devel] " Mike Snitzer 2020-11-18 16:35 ` Christian Borntraeger 2020-11-18 16:35 ` [dm-devel] " Christian Borntraeger 2020-11-18 16:38 ` Randy Dunlap 2020-11-18 16:38 ` [dm-devel] " Randy Dunlap 2020-11-18 21:24 ` Mikulas Patocka 2020-11-18 21:24 ` [dm-devel] " Mikulas Patocka 2020-11-20 14:08 ` Mike Snitzer 2020-11-20 14:08 ` [dm-devel] " Mike Snitzer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201113225228.20563-1-rdunlap@infradead.org \ --to=rdunlap@infradead.org \ --cc=agk@redhat.com \ --cc=borntraeger@de.ibm.com \ --cc=dm-devel@redhat.com \ --cc=gor@linux.ibm.com \ --cc=hca@linux.ibm.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-s390@vger.kernel.org \ --cc=mpatocka@redhat.com \ --cc=snitzer@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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.