From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH] DRBD 8.0; Make sure barrier is sent after last data block in epoch
Date: Tue, 29 Jan 2008 14:37:05 +0100 [thread overview]
Message-ID: <200801291437.06285.philipp.reisner@linbit.com> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767107E8A3F8@EXNA.corp.stratus.com>
Hi Simon,
Back from travelling...
I have applied the two patches you sent Yesterday.
0001-Make-sure-barrier-is-sent-AFTER-last-data-block-in-e.patch
0002-Make-sure-we-dont-set-CREATE_BARRIER-flag-when-conne.patch
BTW, I did white space changes to them.
Since we propagate changes from 8.0 to 8.2, and in 8.2 we try
follow the Linux coding style hard, it makes things easier
for us when the patches follow the Linux coding style in the
first place.
From the other patch bomb I still intend to merge
0010-Ensure-that-state-updates-cannot-be-done-out-of-orde.patch
Regarding the other patches from patch bomb #1, I wanted to
write an summay, which patches where accepted, which are not
yet applied for what reasons. ... But then I went to the
"Open Source Meets Business" Conference and now I can not
remember...
Simon, from your point of view, what patches to we missed from
patch bomb #1 ?
-Phil
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
next prev parent reply other threads:[~2008-01-29 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 15:48 [Drbd-dev] [PATCH] DRBD 8.0; Make sure barrier is sent after last data block in epoch Graham, Simon
2008-01-29 13:37 ` Philipp Reisner [this message]
2008-01-29 19:40 ` Graham, Simon
2008-02-12 23:55 ` [Drbd-dev] Stuck in WFBitMapS again Montrose, Ernest
2008-02-18 13:05 ` Philipp Reisner
2008-03-31 14:43 ` Philipp Reisner
2008-03-31 17:12 ` Montrose, Ernest
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=200801291437.06285.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.linbit.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.