FS/XFS testing framework
 help / color / mirror / Atom feed
From: An Long <lan@suse.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] generic/746: install two necessary files
Date: Thu, 10 Oct 2024 11:46:54 +0800	[thread overview]
Message-ID: <facac6fce8974ec31e8bfd0fd9d9484652fc858a.camel@suse.com> (raw)
In-Reply-To: <20241009163800.GM21840@frogsfrogsfrogs>

On Wed, 2024-10-09 at 09:38 -0700, Darrick J. Wong wrote:
> On Wed, Oct 09, 2024 at 11:56:16PM +0800, An Long wrote:
> > parse-dev-tree.awk and parse-extent-tree.awk are used by
> > generic/746.
> > We need to make sure them are installed, otherwise generic/746 will
> > have problems if fstests is installed via "make install".
> > ---
> 
> Needs a SoB tag.
Added. I used -S instead of -s. Sorry for mistake.
> 
> --D
> 
> >  src/Makefile | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/src/Makefile b/src/Makefile
> > index 3097c29e..a0396332 100644
> > --- a/src/Makefile
> > +++ b/src/Makefile
> > @@ -38,7 +38,7 @@ LINUX_TARGETS = xfsctl bstat t_mtab getdevicesize
> > preallo_rw_pattern_reader \
> > 
> >  EXTRA_EXECS = dmerror fill2attr fill2fs fill2fs_check scaleread.sh
> > \
> >               btrfs_crc32c_forged_name.py popdir.pl popattr.py \
> > -             soak_duration.awk
> > +             soak_duration.awk parse-dev-tree.awk parse-extent-
> > tree.awk
> > 
> >  SUBDIRS = log-writes perf
> > 
> > -- 
> > 2.43.0
> > 
> > 

-- 
An Long <lan@suse.com>
SUSE QE LSG, QE 2, Beijing

      reply	other threads:[~2024-10-10  3:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 15:56 [PATCH v2] generic/746: install two necessary files An Long
2024-10-09 16:38 ` Darrick J. Wong
2024-10-10  3:46   ` An Long [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=facac6fce8974ec31e8bfd0fd9d9484652fc858a.camel@suse.com \
    --to=lan@suse.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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