From: Greg KH <greg@kroah.com>
To: Martin Brandenburg <martin@omnibond.com>
Cc: hubcap@omnibond.com, stable@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] orangefs fixes for stable
Date: Wed, 12 Apr 2017 15:01:30 +0200 [thread overview]
Message-ID: <20170412130130.GB10858@kroah.com> (raw)
In-Reply-To: <20170411164128.8401-1-martin@omnibond.com>
On Tue, Apr 11, 2017 at 12:41:25PM -0400, Martin Brandenburg wrote:
> Here are some patches for 4.9 and 4.10 which we missed before.
>
> I've just looked through the changes to OrangeFS since 4.9 was released.
> These are the only fixes which seem to qualify.
>
> Colin's patch is already in 4.10 and only needs to be applied to 4.9.
> Mike's patches should be applied to 4.9 and 4.10.
>
> (Is there a better way to submit these? Should I just submit separately
> for the two stable trees?)
This worked just fine. Or you can just give me a list of git commit ids
as none of these needed to be modified from what was in Linus's tree
from what I could tell.
thanks,
greg k-h
prev parent reply other threads:[~2017-04-12 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 16:41 [PATCH 0/3] orangefs fixes for stable Martin Brandenburg
2017-04-11 16:41 ` [PATCH 1/3] orangefs: fix memory leak of string 'new' on exit path Martin Brandenburg
2017-04-11 16:41 ` [PATCH 2/3] orangefs: Dan Carpenter influenced cleanups Martin Brandenburg
2017-04-12 13:00 ` Greg KH
2017-04-12 15:27 ` Martin Brandenburg
2017-04-12 20:03 ` Greg KH
2017-04-11 16:41 ` [PATCH 3/3] orangefs: fix buffer size mis-match between kernel space and user space Martin Brandenburg
2017-04-12 13:01 ` Greg KH [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=20170412130130.GB10858@kroah.com \
--to=greg@kroah.com \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@omnibond.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).