From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Sending patches for GFS2
Date: Thu, 20 Sep 2018 14:57:54 +0100 [thread overview]
Message-ID: <13dafeca-35ef-c39b-73b8-e76541b1148c@redhat.com> (raw)
In-Reply-To: <d52ce4b4a9fe40a89e78c883188d1b26@AMSPEX02CL02.citrite.net>
Hi,
On 20/09/18 14:53, Mark Syms wrote:
>
> We have a couple of patches for GFS2 which address some performance
> issues we?ve observed in our testing. What branch would you like the
> patches to be based on top off (we have a custom patched build so
> they?ll need to be realigned first).
>
> Thanks,
>
> ??????????????? Mark.
>
The best thing is to base them off the latest upstream Linus kernel or
from the gfs2 development tree. They are pretty similar and we can fix
up any conflicts in due course, but it probably won't be necessary to do
any additional changes,
Steve.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20180920/925e5bca/attachment.htm>
prev parent reply other threads:[~2018-09-20 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 13:53 [Cluster-devel] Sending patches for GFS2 Mark Syms
2018-09-20 13:57 ` Steven Whitehouse [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=13dafeca-35ef-c39b-73b8-e76541b1148c@redhat.com \
--to=swhiteho@redhat.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).