From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] readahead02: estimate max readahead size
Date: Wed, 26 Oct 2016 06:34:27 -0400 (EDT) [thread overview]
Message-ID: <467645198.658917.1477478067720.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161026102613.GA17833@rei.lan>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Wednesday, 26 October, 2016 12:26:14 PM
> Subject: Re: [LTP] [PATCH v2] readahead02: estimate max readahead size
>
> Hi!
> Tested-by: Cyril Hrubis <chrubis@suse.cz>
> Acked-by: Cyril Hrubis <chrubis@suse.cz>
>
> We should also note in the patch changelog that this fixes the test on
> Btrfs, where it wasn't working previously since there is no
> /sys/dev/block/$major:$minor/ for the anonymous block devices that are
> used internaly for subvolumes.
I appended above to changelog and pushed.
Regards,
Jan
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
prev parent reply other threads:[~2016-10-26 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 7:58 [LTP] [PATCH v2] readahead02: estimate max readahead size Jan Stancek
2016-10-26 10:26 ` Cyril Hrubis
2016-10-26 10:34 ` Jan Stancek [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=467645198.658917.1477478067720.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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