From: Adrian Bunk <bunk@stusta.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC: 2.6.16 patch] ocfs2 heartbeat: clean up bio submission code
Date: Mon Mar 26 15:34:50 2007 [thread overview]
Message-ID: <20070326223449.GJ16477@stusta.de> (raw)
In-Reply-To: <20070326115717.GA16201@localhost.localdomain>
On Mon, Mar 26, 2007 at 01:57:17PM +0200, Lars Ellenberg wrote:
>
> uhm, how about
>
> commit b559292e066f6d570cd5aa5dbd41de61dd04bdce
> tree d8221b5f54ad9b8cef694de687013614dccf5966
> parent 925037bcba7691db2403684141a276930ad184f3
> author Philipp Reisner <philipp.reisner@linbit.com> Thu, 11 Jan 2007 10:58:10 +0100
> committer Mark Fasheh <mark.fasheh@oracle.com> Wed, 07 Feb 2007 12:15:58 -0800
>
> [PATCH] ocfs2 heartbeat: clean up bio submission code
>
> pretty please?
It doesn't apply without rejects and seems non-trivial.
I need a patch that:
- applies and
- was runtime tested with 2.6.16.45 and
- got approved by the OCFS2 maintainers as being low-risk.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next parent reply other threads:[~2007-03-26 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070324114213.GC752@stusta.de>
[not found] ` <17927.4509.867938.738430@notabene.brown>
[not found] ` <20070326115717.GA16201@localhost.localdomain>
2007-03-26 15:34 ` Adrian Bunk [this message]
[not found] ` <20070329082752.GA9348@barkeeper1.linbit>
2007-03-29 8:53 ` [Ocfs2-devel] Re: [RFC: 2.6.16 patch] ocfs2 heartbeat: clean up bio submission code Mark Fasheh
2007-03-29 22:11 ` Adrian Bunk
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=20070326223449.GJ16477@stusta.de \
--to=bunk@stusta.de \
--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.