linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: kernel test robot <lkp@intel.com>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	oe-kbuild-all@lists.linux.dev, linux-hardening@vger.kernel.org,
	ethan@ethancedwards.com
Subject: Re: [PATCH 3/3] ext4: refactor the inline directory conversion and new directory codepaths
Date: Mon, 21 Jul 2025 16:15:59 -0700	[thread overview]
Message-ID: <20250721231559.GA85006@quark> (raw)
In-Reply-To: <202507130429.rPIzofCD-lkp@intel.com>

Hi Ted,

On Sun, Jul 13, 2025 at 05:12:55AM +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
> 
>    fs/ext4/namei.c: In function 'ext4_init_new_dir':
> >> fs/ext4/namei.c:2968:34: warning: variable 'de' set but not used [-Wunused-but-set-variable]
>     2968 |         struct ext4_dir_entry_2 *de;
>          |                                  ^~

This warning is present in ext4/dev now.

- Eric

  reply	other threads:[~2025-07-21 23:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-12 18:12 [PATCH 1/3] ext4: replace strcmp with direct comparison for '.' and '..' Theodore Ts'o
2025-07-12 18:12 ` [PATCH 2/3] ext4: use memcpy() instead of strcpy() Theodore Ts'o
2025-07-30 15:02   ` Andy Shevchenko
2025-07-12 18:12 ` [PATCH 3/3] ext4: refactor the inline directory conversion and new directory codepaths Theodore Ts'o
2025-07-12 21:12   ` kernel test robot
2025-07-21 23:15     ` Eric Biggers [this message]
2025-07-30 15:01       ` Andy Shevchenko
2025-07-19 21:45 ` [PATCH 1/3] ext4: replace strcmp with direct comparison for '.' and '..' Theodore Ts'o

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=20250721231559.GA85006@quark \
    --to=ebiggers@kernel.org \
    --cc=ethan@ethancedwards.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).