From: Greg KH <gregkh@linuxfoundation.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: saeedm@mellanox.com, jsorensen@fb.com, tglx@linutronix.de,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "Revert "mlx5: move affinity hints assignments to generic code"" has been added to the 4.14-stable tree
Date: Sun, 31 Dec 2017 12:24:52 +0100 [thread overview]
Message-ID: <20171231112452.GA3995@kroah.com> (raw)
In-Reply-To: <a952c166-5a37-fa1e-a2f1-9acc702103f2@grimberg.me>
On Sun, Dec 31, 2017 at 12:47:57PM +0200, Sagi Grimberg wrote:
>
> > This is a note to let you know that I've just added the patch titled
> >
> > Revert "mlx5: move affinity hints assignments to generic code"
> >
> > to the 4.14-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > revert-mlx5-move-affinity-hints-assignments-to-generic-code.patch
> > and it can be found in the queue-4.14 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> This patch in its current form, breaks nvme-rdma affinity settings. I've
> mentioned that in the patch review and Saeed promised to send a fix for
> it (which I haven't seen so far).
So things are broken in Linus's tree?
Usually reverting is the safe thing to do, we should just be now back at
the state the code was in before the patch, or has something else
changed here?
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-31 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 10:14 Patch "Revert "mlx5: move affinity hints assignments to generic code"" has been added to the 4.14-stable tree gregkh
2017-12-31 10:47 ` Sagi Grimberg
2017-12-31 11:24 ` Greg KH [this message]
2017-12-31 11:37 ` Sagi Grimberg
2017-12-31 11:45 ` Greg KH
2017-12-31 12:00 ` Sagi Grimberg
2018-01-03 22:02 ` Saeed Mahameed
2018-01-03 21:59 ` Saeed Mahameed
2018-01-04 2:04 ` Saeed Mahameed
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=20171231112452.GA3995@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jsorensen@fb.com \
--cc=saeedm@mellanox.com \
--cc=sagi@grimberg.me \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.