From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org,
Artem Bityutskiy <dedekind@infradead.org>
Subject: Merged "Sort out loose ends after the O_SYNC series"
Date: Tue, 27 Oct 2009 11:34:33 +0100 [thread overview]
Message-ID: <20091027103433.GC4285@duck.suse.cz> (raw)
Hi,
I've just merged your series $SUBJECT into my tree and will push it to
Linus in the next merge window (mainly because of the dependency on the
O_DSYNC patch).
Andrew, because the series depends on the patch implementing O_DSYNC
semantics, I've take what you have in mmotm (including the style cleanup)
and put it in my tree as well. I'll merge it with the series.
Artem, I have merged the UBIFS patch as well because it depends on the
O_DSYNC patch so there's probably not an easy way for you to carry it.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next reply other threads:[~2009-10-27 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 10:34 Jan Kara [this message]
2009-10-27 12:01 ` Merged "Sort out loose ends after the O_SYNC series" Artem Bityutskiy
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=20091027103433.GC4285@duck.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dedekind@infradead.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).