From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/4] JBD2 cleanups
Date: Thu, 7 Jan 2016 15:41:51 +0100 [thread overview]
Message-ID: <1452177715-9671-1-git-send-email-jack@suse.cz> (raw)
Hi!
here are some JBD2 cleanups that have accumulated in my tree when doing
other stuff. I think they are reasonable ones but opinions may differ...
Honza
next reply other threads:[~2016-01-07 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 14:41 Jan Kara [this message]
2016-01-07 14:41 ` [PATCH 1/4] jbd2: Remove some unnecessary arguments of jbd2_journal_write_revoke_records Jan Kara
2016-02-23 4:09 ` Theodore Ts'o
2016-01-07 14:41 ` [PATCH 2/4] jbd2: Factor out common descriptor block initialization Jan Kara
2016-02-23 4:18 ` Theodore Ts'o
2016-01-07 14:41 ` [PATCH 3/4] jbd2: Unify revoke and tag block checksum handling Jan Kara
2016-01-07 17:16 ` Darrick J. Wong
2016-01-12 12:41 ` Jan Kara
2016-01-13 1:25 ` Darrick J. Wong
2016-02-23 4:27 ` Theodore Ts'o
2016-01-07 14:41 ` [PATCH 4/4] jbd2: Save some atomic ops in __JI_COMMIT_RUNNING handling Jan Kara
2016-02-23 4:27 ` 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=1452177715-9671-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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).