From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix warnings in compat_ioctl code
Date: Tue, 6 Jul 2021 10:19:15 -0700 [thread overview]
Message-ID: <20210706171915.GA11588@locust> (raw)
In-Reply-To: <YOLGKMyrVNMmGX7g@infradead.org>
On Mon, Jul 05, 2021 at 09:43:20AM +0100, Christoph Hellwig wrote:
> On Fri, Jul 02, 2021 at 08:01:20PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Fix some compiler warnings about unused variables.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
>
> The change looks silly but otherwise ok. What compiler gives these
> stupid warnings?
gcc 10.3, but it doesn't matter because the kbuild robot says this patch
creates even /more/ silly warnings on other weird architectures, so I'm
withdrawing this patch because I DGAF^W have decided that chasing unused
variable warnings is a bad use of anybody's time.
--D
prev parent reply other threads:[~2021-07-06 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 3:01 [PATCH] xfs: fix warnings in compat_ioctl code Darrick J. Wong
2021-07-05 8:43 ` Christoph Hellwig
2021-07-06 17:19 ` Darrick J. Wong [this message]
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=20210706171915.GA11588@locust \
--to=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
/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