All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org
Subject: Re: Issue in applying patch [hid-sensor-hub: clear memory to avoid random data]
Date: Wed, 14 Dec 2016 12:42:50 -0800	[thread overview]
Message-ID: <1481748170.6973.3.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1612142130490.16984@cbobk.fhfr.pm>

On Wed, 2016-12-14 at 21:33 +0100, Jiri Kosina wrote:
> On Wed, 14 Dec 2016, Srinivas Pandruvada wrote:
> 
> > As per the comment here, it seems that you applied v4 version of
> patch.
> > 
> > https://patchwork.kernel.org/patch/9428715/
> > 
> > But when I look at the upstream kernel, the very first version of
> the
> > patch was applied, which was wrong.
> > 
> > Basically the change should be in sensor_hub_get_feature() not in
> > sensor_hub_set_feature().
> > Otherwise it breaks sensor functionality.
> > 
> > How should we handle this?
> 
> Hi Srinivas,
> 
> my whole queue is now merged by Linus, so any fixups should be
> submitted 
> as standalone patches on top of current Linus' tree; I'll push the
> fix to 
> Linus then for 4.10 still.
> 
> Ideally we also put proper "Fixes:" tag, so that it gets picked up
> by 
> 4.9-stable once/if there is one.
> 
> Thanks, and sorry for my brainfart; I'll check my archives to see
> what 
> went wrong.
No problem at all.

Thanks,
Srinivas


      reply	other threads:[~2016-12-14 20:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 22:48 [PATCH] HID: intel_ish-hid: use %pUL for uuid formatting Rasmus Villemoes
2016-12-01 14:21 ` Benjamin Tissoires
2016-12-01 23:51   ` Srinivas Pandruvada
2016-12-02 14:04 ` Jiri Kosina
2016-12-14 18:27   ` Issue in applying patch [hid-sensor-hub: clear memory to avoid random data] Srinivas Pandruvada
2016-12-14 20:33     ` Jiri Kosina
2016-12-14 20:42       ` Srinivas Pandruvada [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=1481748170.6973.3.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@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.