From: Greg KH <gregkh@linuxfoundation.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: alexander.levin@microsoft.com, davem@davemloft.net,
stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "net: qlge: Eliminate duplicate barriers on weakly-ordered archs" has been added to the 4.16-stable tree
Date: Tue, 1 May 2018 16:03:32 -0700 [thread overview]
Message-ID: <20180501230332.GA3081@kroah.com> (raw)
In-Reply-To: <dad97a1f-23c2-af6d-1d5a-fc35ec9cb64d@codeaurora.org>
On Tue, May 01, 2018 at 06:39:06PM -0400, Sinan Kaya wrote:
> On 5/1/2018 6:32 PM, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > net: qlge: Eliminate duplicate barriers on weakly-ordered archs
> >
> > to the 4.16-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:
> > net-qlge-eliminate-duplicate-barriers-on-weakly-ordered-archs.patch
> > and it can be found in the queue-4.16 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.
> >
>
> I don't think these should be pulled at this moment. There is still more barrier
> work to be done and the patch below goes in the wrong direction after discussion
> with Linus.
>
> I'm waiting for all architectures to reach to functional parity at the end of 4.17
> to pick up from where I left.
>
> There are still few architectures still violating writel() guarantee.
Fair enough, thanks for the information, I'll drop this now.
greg k-h
prev parent reply other threads:[~2018-05-01 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15252139793450@kroah.com>
2018-05-01 22:39 ` Patch "net: qlge: Eliminate duplicate barriers on weakly-ordered archs" has been added to the 4.16-stable tree Sinan Kaya
2018-05-01 23:03 ` 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=20180501230332.GA3081@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=davem@davemloft.net \
--cc=okaya@codeaurora.org \
--cc=stable-commits@vger.kernel.org \
--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 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.