From: Jan Kara <jack@suse.cz>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3 RESEND] BDI handling fixes
Date: Mon, 20 Sep 2010 23:27:38 +0200 [thread overview]
Message-ID: <20100920212738.GA14020@quack.suse.cz> (raw)
In-Reply-To: <4C9798D1.9060009@fusionio.com>
On Mon 20-09-10 19:24:33, Jens Axboe wrote:
> On 2010-09-20 19:23, Jens Axboe wrote:
> > On 2010-09-20 17:44, Jan Kara wrote:
> >> Hi,
> >>
> >> I resend this series because I've messed up Jens' address in the original
> >> posting. Jens, would you please include these fixes in your tree? Thanks.
> >> The series of these three patches fixes the warning in __mark_inode_dirty()
> >> which happens when I do e.g. touch /dev/zero.
> >
> > Thanks, I'll commit for .37 and tag the for stable.
>
> Actually, I think they are fine for .36 directly. Agree?
Yes, I think they should be OK for .36.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2010-09-20 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 15:44 [PATCH 0/3 RESEND] BDI handling fixes Jan Kara
2010-09-20 15:44 ` [PATCH 1/3] bdi: Initialize noop_backing_dev_info properly Jan Kara
2010-09-20 15:44 ` [PATCH 2/3] char: Mark /dev/zero and /dev/kmem as not capable of writeback Jan Kara
2010-09-20 15:44 ` [PATCH 3/3] bdi: Fix warnings in __mark_inode_dirty for /dev/zero and friends Jan Kara
2010-09-20 17:23 ` [PATCH 0/3 RESEND] BDI handling fixes Jens Axboe
2010-09-20 17:24 ` Jens Axboe
2010-09-20 21:27 ` Jan Kara [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=20100920212738.GA14020@quack.suse.cz \
--to=jack@suse.cz \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).