Date: Fri, 18 May 2018 07:46:36 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [MODERATED] Re: [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2
Message-ID: <20180518114636.GV18423@char.us.oracle.com>
References: <20180517031815.016936086@localhost.localdomain>
 <20180518082036.GA6330@kroah.com>
MIME-Version: 1.0
In-Reply-To: <20180518082036.GA6330@kroah.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: speck@linutronix.de

> > 2.14.3
> 
> Why is this a part of this series?  Shouldn't this just go into the tree
> through the "normal" patch process if this really is an issue?  And if
> so, please cc: stable as the patch you are trying to "fix" here has been
> backported already to stable kernel releases.

It certainly can; I thought it made more sense to have it as part of this
series as this series is the one that git bisection is going to finger.
> 
> I really hate the "open coding" here though, it feels odd that the xen
> developers feel that it is needed and they can't trust the fact that
> since the kernel works fine today with this, it will continue to work ok
> in the future (and if it breaks then, great, we can fix it...)

The open coding was done b/c they expected push back from Thomas on doing
the proper fix and instead ended with band-aid solution in their back-yard.

> 
> thanks,
> 
> greg k-h