public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: akpm@linux-foundation.org, hca@linux.ibm.com, gor@linux.ibm.com,
	 agordeev@linux.ibm.com
Cc: borntraeger@linux.ibm.com, svens@linux.ibm.com,
	 linux-s390@vger.kernel.org, patches@lists.linux.dev,
	 Nathan Chancellor <nathan@kernel.org>,
	sth@linux.ibm.com,  hoeppner@linux.ibm.com
Subject: [PATCH 0/2] s390: A couple of fixes for -Wmissing-prototypes
Date: Thu, 30 Nov 2023 17:22:31 -0700	[thread overview]
Message-ID: <20231130-s390-missing-prototypes-v1-0-799d3cf07fb7@kernel.org> (raw)

Hi all,

This series resolves a couple of -Wmissing-prototypes that I see in my
builds of -next, even though the issues appear to be latent. The patch
to enable -Wmissing-prototypes is in Andrew's tree, so these should
likely go there as well with acks from the s390 maintainers.

---
Nathan Chancellor (2):
      s390/dasd: Remove dasd_stats_generic_show()
      s390/traps: Only define is_valid_bugaddr() under CONFIG_GENERIC_BUG

 arch/s390/kernel/traps.c  | 2 ++
 drivers/s390/block/dasd.c | 6 ------
 2 files changed, 2 insertions(+), 6 deletions(-)
---
base-commit: 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab
change-id: 20231130-s390-missing-prototypes-7d95aae2cdcb

Best regards,
-- 
Nathan Chancellor <nathan@kernel.org>


             reply	other threads:[~2023-12-01  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  0:22 Nathan Chancellor [this message]
2023-12-01  0:22 ` [PATCH 1/2] s390/dasd: Remove dasd_stats_generic_show() Nathan Chancellor
2023-12-04  7:41   ` Alexander Gordeev
2023-12-04 13:13   ` Stefan Haberland
2023-12-01  0:22 ` [PATCH 2/2] s390/traps: Only define is_valid_bugaddr() under CONFIG_GENERIC_BUG Nathan Chancellor
2023-12-04  9:06   ` Alexander Gordeev
2023-12-04 16:38     ` Nathan Chancellor
2023-12-05 12:59   ` Alexander Gordeev

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=20231130-s390-missing-prototypes-v1-0-799d3cf07fb7@kernel.org \
    --to=nathan@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=sth@linux.ibm.com \
    --cc=svens@linux.ibm.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox