From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 cleanups, bug fixes for Linux kernel 3.1 - final drop
Date: Sun, 21 Aug 2011 22:45:46 -0700 [thread overview]
Message-ID: <4E51ED0A.1080907@oracle.com> (raw)
In-Reply-To: <20110822042330.GC31134@noexit.corp.google.com>
On 08/21/2011 09:23 PM, Joel Becker wrote:
> On Thu, Jul 14, 2011 at 03:50:11PM -0700, Sunil Mushran wrote:
>> Joel,
>>
>> Hopefully this is the final drop before the 3.1 merge window. I had posted most
>> of the patches before. In fact the first 12 are exactly the same. The 13th one
>> is modified and 14,15,16 are new.
> Hey Sunil,
> These changes are now in the 'fixes' branch of ocfs2.git. Sorry
> this took so long. I plan to send the SEEK_HOLE patch along, and if
> Linus wants it out I will take it out.
> My only comment on the series, which is otherwise quite nicely
> put together, is that new mlog()s should be replaced by trace events.
> I'm going to let them in for this time, but please consider updating
> them in another patch.
I don't think I added new mlogs. I removed some and replaced
some with printks. The goal is to replace all with trace events.
prev parent reply other threads:[~2011-08-22 5:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 22:50 [Ocfs2-devel] ocfs2 cleanups, bug fixes for Linux kernel 3.1 - final drop Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 01/16] ocfs2/cluster: Abort heartbeat start on hard-ro devices Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 02/16] ocfs2/cluster: Clean up messages in o2net Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 03/16] ocfs2/dlm: Clean up messages in o2dlm Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 04/16] ocfs2: Clean up messages in stack_o2cb.c Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 05/16] ocfs2/dlm: Cleanup up dlm_finish_local_lockres_recovery() Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 06/16] ocfs2/dlm: Clean up refmap helpers Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 07/16] ocfs2/dlm: Trace insert/remove of resource to/from hash Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 08/16] ocfs2/dlm: Cleanup dlm_wait_for_node_death() and dlm_wait_for_node_recovery() Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 09/16] ocfs2/dlm: Take inflight reference count for remotely mastered resources too Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 10/16] ocfs2/dlm: dlmlock_remote() needs to account for remastery Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 11/16] ocfs2/cluster: Fix output in file elapsed_time_in_ms Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 12/16] ocfs2/cluster: Add new function o2net_fill_node_map() Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 13/16] ocfs2/cluster: Cluster up now includes network connections too Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 14/16] ocfs2: Clean up messages in the fs Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 15/16] ocfs2: Add comment about orphan scanning Sunil Mushran
2011-07-14 22:50 ` [Ocfs2-devel] [PATCH 16/16] ocfs2: Fix ocfs2_page_mkwrite() Sunil Mushran
2011-08-22 4:23 ` [Ocfs2-devel] ocfs2 cleanups, bug fixes for Linux kernel 3.1 - final drop Joel Becker
2011-08-22 5:45 ` Sunil Mushran [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=4E51ED0A.1080907@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.