public inbox for platform-driver-x86@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Mario.Limonciello@dell.com
Cc: srinivas.pandruvada@linux.intel.com, andy.shevchenko@gmail.com,
	alex.hung@canonical.com, andy@infradead.org,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, rjw@rjwysocki.net
Subject: Re: [PATCH v2] platform/x86: intel-hid: Add support for Device Specific Methods
Date: Mon, 9 Jul 2018 14:06:46 -0700	[thread overview]
Message-ID: <20180709210646.GA30247@fury> (raw)
In-Reply-To: <1dfb07bd3461414e8db492e643d7de88@ausx13mpc120.AMER.DELL.COM>

On Mon, Jul 09, 2018 at 04:38:16AM +0000, Mario.Limonciello@dell.com wrote:
> > -----Original Message-----
> > From: Srinivas Pandruvada [mailto:srinivas.pandruvada@linux.intel.com]
> > Sent: Saturday, July 7, 2018 8:44 AM
> > To: Darren Hart; Andy Shevchenko
> > Cc: Limonciello, Mario; Alex Hung; Andy Shevchenko; Platform Driver; Linux Kernel
> > Mailing List; Rafael J. Wysocki
> > Subject: Re: [PATCH v2] platform/x86: intel-hid: Add support for Device Specific
> > Methods
> > 
> > On Fri, 2018-07-06 at 16:59 -0700, Darren Hart wrote:
> > > On Mon, Jul 02, 2018 at 05:06:14PM +0300, Andy Shevchenko wrote:
> > > > On Mon, Jul 2, 2018 at 4:51 PM,  <Mario.Limonciello@dell.com>
> > > > wrote:
...
> > Mario can add more.
> > But I think Dell has released a BIOS fix, so that power button can
> > still work using non _DSM way. So I think we can wait for normal
> > release cycle.
> 
> Yeah, I added some comments on a separate reply already indicating this.
> 
> The affected system we know about has reverted the new interface.
> 
> This all stems from an expectation that the _DSM has been there for "many"
> releases on the Windows side.  Long enough that even all the corporate downgrade
> scenarios to older Windows versions and the drivers with them all worked properly.
> 
> If this doesn't end up being a candidate for backporting to stable we'll probably
> end up asking our various OS partners to backport it as a SAUCE type patch in distro
> kernels to eventually be able to turn this back on.

Thanks Mario. We'll skip the RC. We can discuss -stable as a separate
issue.  This patch fixes a demonstrable bug, the biggest obstacle here
is the size. At 240 lines with context, it more than doubles the maximum
patch size for stable.

My recommendation is that we treat the stable backport of this as a
special case, e.g. Andy and I don't tag it, but you or Srinivas propose
it and specifically make the case for why an exception should be made to
Greg.

How self contained and isolated this change is will be an important part
of the argument. On the one hand, it's all one file, on the other hand,
this is a fairly generic driver in use in more and more platforms, with
the potential for widespread impact if this introduces a new bug.

-- 
Darren Hart
VMware Open Source Technology Center

  reply	other threads:[~2018-07-09 21:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 18:19 [PATCH v2] platform/x86: intel-hid: Add support for Device Specific Methods Srinivas Pandruvada
2018-06-29 16:44 ` Mario.Limonciello
2018-06-29 18:41   ` Srinivas Pandruvada
2018-07-02 12:41     ` Andy Shevchenko
2018-07-02 13:51       ` Mario.Limonciello
2018-07-02 14:06         ` Andy Shevchenko
2018-07-06 23:59           ` Darren Hart
2018-07-07  3:48             ` Mario.Limonciello
2018-07-07 16:24               ` Andy Shevchenko
2018-07-07 23:37                 ` Srinivas Pandruvada
2018-07-08 17:53                   ` Andy Shevchenko
2018-07-07 13:43             ` Srinivas Pandruvada
2018-07-09  4:38               ` Mario.Limonciello
2018-07-09 21:06                 ` Darren Hart [this message]
2018-07-09 21:08                   ` Mario.Limonciello
2018-07-09 23:17                     ` Darren Hart

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=20180709210646.GA30247@fury \
    --to=dvhart@infradead.org \
    --cc=Mario.Limonciello@dell.com \
    --cc=alex.hung@canonical.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox