linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Jungkamp <p.jungkamp@gmx.net>
To: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>,
	Jiri Kosina <jikos@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 0/4] IIO: More HID custom sensors
Date: Tue, 13 Dec 2022 23:51:50 +0100	[thread overview]
Message-ID: <cc35bdc25daedb32dbb5949f99559485a7f83080.camel@gmx.net> (raw)
In-Reply-To: <623f2206647e69199c64064c48eb8bf03afb99da.camel@linux.intel.com>

Hello,

Is there something I still need to do for this to be merged in the next
merge window?

I don't quite understand what would happen next. I'm curious and hope I
don't bother in the busy times when approaching a merge window.

Regards,
Philipp Jungkamp

On Sun, 2022-11-27 at 09:33 -0800, srinivas pandruvada wrote:
> On Fri, 2022-11-25 at 00:38 +0100, Philipp Jungkamp wrote:
> > Hello,
> > 
> > I'm sorry for the confusion caused by me sending revisions as
> > replies.
> > I've now addresses the points raised. As I'm unfamiliar with
> > mailing
> > lists
> > any recommendation on making the process more seamless is welcome.
> > 
> > Thank you for your time!
> > 
> 
> For the series
> 
> Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> 
> 
> > v2:
> > - Patch 1/4:
> >   - Remove unnecessary comments.
> >   - Change return type of functions to bool. (introduced an error,
> > fixed in v4)
> >   - Swallows return value of a function. (fixed in v4)
> > - Patch 2/4:
> >   - Create this 'noop' patch that just adds the LISS sensors to the
> > custom
> >     sensor match table.
> > - Patch 3/4:
> >   - Remove some unnecessary newlines in function calls.
> > - Patch 4/4:
> >   - Allow for 1 byte human presence reports.
> > 
> > v3:
> > - Patch 2/4
> >   - Add missing 'Signed-Off-By'
> > 
> > v4:
> > - Patch 1/4:
> >   - Fix return value and error codes on property query.
> >   - Document and ignore return values for queries of optionally
> > matched
> >     properties.
> >   - Don't modify *known in _get_known, return error when not
> > matched.
> >   - Remove comment on newly added sensors from commit message.
> > - Patch 4/4:
> >   - Clean up switch statement.
> > 
> > Regards,
> > Philipp Jungkamp
> > 
> > Philipp Jungkamp (4):
> >   HID: hid-sensor-custom: Allow more custom iio sensors
> >   HID: hid-sensor-custom: Add LISS custom sensors
> >   IIO: hid-sensor-als: Use generic usage
> >   IIO: hid-sensor-prox: Use generic usage
> > 
> >  drivers/hid/hid-sensor-custom.c     | 233 +++++++++++++++++++-----
> > ----
> >  drivers/iio/light/hid-sensor-als.c  |  27 ++--
> >  drivers/iio/light/hid-sensor-prox.c |  37 +++--
> >  include/linux/hid-sensor-ids.h      |   1 +
> >  4 files changed, 199 insertions(+), 99 deletions(-)
> > 
> > --
> > 2.38.1
> > 
> 
> 


  reply	other threads:[~2022-12-13 22:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 23:38 [PATCH v4 0/4] IIO: More HID custom sensors Philipp Jungkamp
2022-11-24 23:38 ` [PATCH v4 1/4] HID: hid-sensor-custom: Allow more custom iio sensors Philipp Jungkamp
2022-11-26 19:11   ` Jonathan Cameron
2022-11-24 23:38 ` [PATCH v4 2/4] HID: hid-sensor-custom: Add LISS custom sensors Philipp Jungkamp
2022-11-26 19:11   ` Jonathan Cameron
2022-11-24 23:38 ` [PATCH v4 3/4] IIO: hid-sensor-als: Use generic usage Philipp Jungkamp
2022-11-26 19:05   ` Jonathan Cameron
2022-11-24 23:38 ` [PATCH v4 4/4] IIO: hid-sensor-prox: " Philipp Jungkamp
2022-11-26 19:04   ` Jonathan Cameron
2022-11-27 17:33 ` [PATCH v4 0/4] IIO: More HID custom sensors srinivas pandruvada
2022-12-13 22:51   ` Philipp Jungkamp [this message]
2022-12-14  9:27     ` Jonathan Cameron
2022-12-14 17:20     ` Jiri Kosina
2022-12-15 16:21       ` Jonathan Cameron
2022-12-20 14:26         ` 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=cc35bdc25daedb32dbb5949f99559485a7f83080.camel@gmx.net \
    --to=p.jungkamp@gmx.net \
    --cc=jic23@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).