From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Martin Brandenburg <martin@omnibond.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] orangefs: Axe some dead code
Date: Fri, 25 Nov 2016 21:51:39 +0000 [thread overview]
Message-ID: <20161125215139.GM6266@mwanda> (raw)
In-Reply-To: <CAOg9mSRZ8VLGPD876DPq1iLFofwPExWb-rzvieoiP+kQJZiJeQ@mail.gmail.com>
On Thu, Nov 24, 2016 at 07:31:11AM -0500, Mike Marshall wrote:
> This seems like a good and proper patch to me, and simple too.
> But like all changes, it needs tested. While I was testing it, I
> discovered a regression in the associated userspace code. I
> "bisected" (we use SVN for the userspace part of Orangefs)
> down to the commit that caused the regression, and some
> of the userspace folks are going to fix it.
>
> I don't think I should ask Linus to pull this patch until I can
> test it. Since we're about to go into rc7, it might not go in
> until the next go around...
>
Linus is on 4.9-rc7 so you're saying this would probably go into 4.11?
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Martin Brandenburg <martin@omnibond.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] orangefs: Axe some dead code
Date: Sat, 26 Nov 2016 00:51:39 +0300 [thread overview]
Message-ID: <20161125215139.GM6266@mwanda> (raw)
In-Reply-To: <CAOg9mSRZ8VLGPD876DPq1iLFofwPExWb-rzvieoiP+kQJZiJeQ@mail.gmail.com>
On Thu, Nov 24, 2016 at 07:31:11AM -0500, Mike Marshall wrote:
> This seems like a good and proper patch to me, and simple too.
> But like all changes, it needs tested. While I was testing it, I
> discovered a regression in the associated userspace code. I
> "bisected" (we use SVN for the userspace part of Orangefs)
> down to the commit that caused the regression, and some
> of the userspace folks are going to fix it.
>
> I don't think I should ask Linus to pull this patch until I can
> test it. Since we're about to go into rc7, it might not go in
> until the next go around...
>
Linus is on 4.9-rc7 so you're saying this would probably go into 4.11?
regards,
dan carpenter
next prev parent reply other threads:[~2016-11-25 21:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 22:17 [PATCH] orangefs: Axe some dead code Christophe JAILLET
2016-11-21 22:17 ` Christophe JAILLET
2016-11-22 15:49 ` Martin Brandenburg
2016-11-22 15:49 ` Martin Brandenburg
2016-11-24 12:31 ` Mike Marshall
2016-11-24 12:31 ` Mike Marshall
2016-11-25 21:51 ` Dan Carpenter [this message]
2016-11-25 21:51 ` Dan Carpenter
2016-11-25 23:09 ` Mike Marshall
2016-11-25 23:09 ` Mike Marshall
2016-11-26 10:02 ` Dan Carpenter
2016-11-26 10:02 ` Dan Carpenter
2016-11-26 13:51 ` Mike Marshall
2016-11-26 13:51 ` Mike Marshall
2016-11-28 11:07 ` Dan Carpenter
2016-11-28 11:07 ` Dan Carpenter
2016-11-28 14:06 ` Mike Marshall
2016-11-28 14:06 ` Mike Marshall
2016-11-28 14:36 ` Dan Carpenter
2016-11-28 14:36 ` Dan Carpenter
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=20161125215139.GM6266@mwanda \
--to=dan.carpenter@oracle.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hubcap@omnibond.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.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.