From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v2 0/4] ISH Fixes for module loading
Date: Thu, 03 Nov 2016 19:39:47 -0700 [thread overview]
Message-ID: <1478227187.26953.0.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1611031204500.5061@cbobk.fhfr.pm>
On Thu, 2016-11-03 at 12:05 -0600, Jiri Kosina wrote:
> On Fri, 21 Oct 2016, Srinivas Pandruvada wrote:
>
> > Two issues are reported related to loading of intel-ishtp-hid:
> >
> > 1. Loading failure after rmmod and then modprobe
> > (Patch 1/4 to Patch 3/4) address this. Here first two patches are
> just
> > clean up patches which gets used in Patch 3/4 to fix the issue.
> >
> > 2. Loading failure due to request_irq failure on some platforms
> > (Patch 4/4)
>
> This actually looks like 4.9-rc material ... could you please confirm
> that
> you agree with that, or you'd rather have this for the next merge
> window?
I am fine with 4.9-rc.
Thanks,
Srinivas
>
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
next prev parent reply other threads:[~2016-11-04 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 22:48 [PATCH v2 0/4] ISH Fixes for module loading Srinivas Pandruvada
2016-10-21 22:48 ` [PATCH v2 1/4] hid: intel-ish-hid: ipc: consolidate ish wake up operation Srinivas Pandruvada
2016-10-21 22:48 ` [PATCH v2 2/4] hid: intel-ish-hid: ipc: Move DMA disable code to new function Srinivas Pandruvada
2016-10-21 22:48 ` [PATCH v2 3/4] hid: intel-ish-hid: ipc: Fix driver reinit failure Srinivas Pandruvada
2016-10-21 22:48 ` [PATCH v2 4/4] hid: intel-ish-hid: request_irq failure Srinivas Pandruvada
2016-11-03 18:05 ` [PATCH v2 0/4] ISH Fixes for module loading Jiri Kosina
2016-11-04 2:39 ` Srinivas Pandruvada [this message]
2016-11-05 15:02 ` Jiri Kosina
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=1478227187.26953.0.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.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.