All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2
Date: Fri, 18 May 2018 07:46:36 -0400	[thread overview]
Message-ID: <20180518114636.GV18423@char.us.oracle.com> (raw)
In-Reply-To: <20180518082036.GA6330@kroah.com>

> > 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

  parent reply	other threads:[~2018-05-18 11:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  3:18 [MODERATED] [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2 konrad.wilk
2018-05-18  8:20 ` [MODERATED] " Greg KH
2018-05-18  9:02   ` Thomas Gleixner
2018-05-18 11:46   ` Konrad Rzeszutek Wilk [this message]
2018-05-18  9:14 ` Thomas Gleixner
2018-05-18 11:43   ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18 12:03     ` Greg KH
2018-05-18 13:21 ` Greg KH
2018-05-18 18:22   ` Konrad Rzeszutek Wilk
2018-05-18 19:57     ` Thomas Gleixner
2018-05-18 20:34       ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18 20:40         ` Linus Torvalds
2018-05-18 21:05           ` Konrad Rzeszutek Wilk
2018-05-18 21:10             ` Linus Torvalds
2018-05-19  8:33         ` Thomas Gleixner

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=20180518114636.GV18423@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=speck@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.