From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: jic23@kernel.org, benjamin.tissoires@redhat.com,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, chaya.golan@intel.com,
daniel.drubin@intel.com, A.Bhattacharya@ulg.ac.be
Subject: Re: [PATCH 2/6] hid: intel_ish-hid: ISH Transport layer
Date: Fri, 17 Jun 2016 14:09:05 -0700 [thread overview]
Message-ID: <1466197745.24319.106.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1606172243590.6874@cbobk.fhfr.pm>
On Fri, 2016-06-17 at 22:45 +0200, Jiri Kosina wrote:
> On Fri, 17 Jun 2016, Jiri Kosina wrote:
>
> > > +struct ishtp_cl_device *ishtp_bus_add_device(struct ishtp_device
> *dev,
> > > + uuid_le uuid, char
> *name)
> > > +{
> >
> > Should be static.
>
> Actually, going deeper into the code and trying to untangle all the
> dependencies, there are quite a few more in other ipc.c, hid-
> client.c,
> etc. Please fix that globally in the next iteration.
>
Great. I ran sparse and identified few more. I will fix this is new
iteration.
One thing I am still wondering is that the current ISH model is built
in only. Some distros configure CONFIG_HID as module. So in Kconfig in
drivers/hid/intel-ish-hid/, I need to add "select HID".
What do you think about this?
Unless you are in middle of review, I want to go ahead and send v2.
Thanks,
Srinivas
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
next prev parent reply other threads:[~2016-06-17 21:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 12:13 [PATCH 0/6] Intel Integrated Sensor Hub Support (ISH) Srinivas Pandruvada
2016-06-11 12:13 ` Srinivas Pandruvada
2016-06-11 12:13 ` [PATCH 1/6] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
[not found] ` <1465647219-7798-2-git-send-email-srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-17 20:43 ` Jiri Kosina
2016-06-17 20:43 ` Jiri Kosina
2016-06-11 12:13 ` [PATCH 2/6] hid: intel_ish-hid: ISH Transport layer Srinivas Pandruvada
2016-06-17 20:43 ` Jiri Kosina
2016-06-17 20:45 ` Jiri Kosina
2016-06-17 21:09 ` Srinivas Pandruvada [this message]
2016-06-17 21:12 ` Srinivas Pandruvada
2016-06-20 9:29 ` Jiri Kosina
[not found] ` <alpine.LNX.2.00.1606201129060.6874-YHPUNQjx9ReKbouaWp301Q@public.gmane.org>
2016-06-20 14:19 ` One Thousand Gnomes
2016-06-20 14:19 ` One Thousand Gnomes
2016-06-11 12:13 ` [PATCH 3/6] hid: intel-ish-hid: ipc layer Srinivas Pandruvada
2016-06-11 12:13 ` [PATCH 4/6] hid: intel-ish-hid: ISH HID client driver Srinivas Pandruvada
2016-06-11 12:13 ` [PATCH 5/6] iio: hid-sensors: use asynchronous resume Srinivas Pandruvada
2016-06-11 12:13 ` [PATCH 6/6] hid: hid-sensor-hub: Add ISH quirk Srinivas Pandruvada
2016-06-11 13:10 ` [PATCH 0/6] Intel Integrated Sensor Hub Support (ISH) Atri Bhattacharya
2016-06-12 6:28 ` Atri Bhattacharya
2016-06-14 17:16 ` Daniel Turton
2016-06-16 19:14 ` Grant Likely
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=1466197745.24319.106.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=A.Bhattacharya@ulg.ac.be \
--cc=benjamin.tissoires@redhat.com \
--cc=chaya.golan@intel.com \
--cc=daniel.drubin@intel.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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.