From: Benny Halevy <bhalevy@panasas.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/7] misc fixes and cleanup
Date: Fri, 01 Oct 2010 18:30:40 +0200 [thread overview]
Message-ID: <4CA60CB0.20706@panasas.com> (raw)
In-Reply-To: <1285948971-2048-1-git-send-email-iisaman@netapp.com>
Thanks. I'm merging all 7 and rebasing
so we can have a new tree before I fly out tomorrow morning.
Benny
On 2010-10-01 18:02, Fred Isaman wrote:
> The first 3 do some cleanup preparing for the hopefully final devinfo submission.
>
> The last 3 fix some use of freed memory problems using the synch error handler (that
> were never being triggered because the asynch error handler got there first, at least
> until the LAYOUTGET code got restructured.)
>
> Fred
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-01 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 16:02 [PATCH 0/7] misc fixes and cleanup Fred Isaman
2010-10-01 16:02 ` [PATCH 1/7] SQUASHME: pnfs-devinfo-submit: misc small fixes Fred Isaman
2010-10-01 16:02 ` [PATCH 2/7] SQUASHME: pnfs_submit: remove inlines from *.c files Fred Isaman
2010-10-01 16:02 ` [PATCH 3/7] SQUASHME: pnfs-devinfo-submit: fix comments in pnfs_layout*_release Fred Isaman
2010-10-01 16:02 ` [PATCH 4/7] nfs: change end of line commas to semicolons Fred Isaman
2010-10-01 16:02 ` [PATCH 5/7] SQUASHME: pnfs-devinfo-submit: Use only asynch error handler for LAYOUTGET Fred Isaman
2010-10-01 16:02 ` [PATCH 6/7] SQUASHME: pnfs_submit: Only use asynch error handler for LAYOUTCOMMIT Fred Isaman
2010-10-01 16:02 ` [PATCH 7/7] SQUASHME: pnfs_submit: only use asynch error handler for LAYOUTRETURN Fred Isaman
2010-10-01 16:30 ` Benny Halevy [this message]
2010-10-01 17:00 ` [PATCH 0/7] misc fixes and cleanup Benny Halevy
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=4CA60CB0.20706@panasas.com \
--to=bhalevy@panasas.com \
--cc=iisaman@netapp.com \
--cc=linux-nfs@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