From: Jens Axboe <axboe@kernel.dk>
To: Srinivas Eeda <srinivas.eeda@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 1/1] writeback fix bdi thread race in mark_inode_dirty
Date: Mon, 22 Jul 2013 12:12:58 -0600 [thread overview]
Message-ID: <20130722181258.GY32755@kernel.dk> (raw)
In-Reply-To: <51ED66A7.3020100@oracle.com>
On Mon, Jul 22 2013, Srinivas Eeda wrote:
> Hi Jens,
>
> Thanks!
>
> I am new to submitting patches to linux-fsdevel. Is there a mailing list I
> should submit this patch or someone will pick this patch for mainline and
> stable branch?
No that's fine. What is needed is a stable@kernel.org CC, but that can
easily be added after the fact.
--
Jens Axboe
prev parent reply other threads:[~2013-07-22 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 18:05 [PATCH 1/1] writeback fix bdi thread race in mark_inode_dirty Srinivas Eeda
2013-07-22 13:32 ` Jan Kara
2013-07-22 15:41 ` Jens Axboe
2013-07-22 17:06 ` Srinivas Eeda
2013-07-22 18:12 ` Jens Axboe [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=20130722181258.GY32755@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=srinivas.eeda@oracle.com \
/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).