Linux IIO development
 help / color / mirror / Atom feed
From: Aditya Garg <gargaditya08@live.com>
To: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	"jkosina@suse.cz" <jkosina@suse.cz>,
	"benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"orlandoch.dev@gmail.com" <orlandoch.dev@gmail.com>,
	"ronald@innovation.ch" <ronald@innovation.ch>
Subject: Re: [PATCH v2] HID: Recognize sensors with application collections too.
Date: Wed, 11 Jan 2023 10:06:27 +0000	[thread overview]
Message-ID: <A02BE14A-8532-4C2D-940B-06DCCDB005D3@live.com> (raw)
In-Reply-To: <74fbf0eb19ebdb964397d8f8d9b5fc12a06128cf.camel@linux.intel.com>



> On 11-Jan-2023, at 3:46 AM, srinivas pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
> 
> 
> Don't add full stop at the end.
> 
> HID: Recognize sensors with application collection
> 
> Better not use language extensions. Simple to use
> 
> report->field[i]->physical ?  report->field[i]->physical : report-
>> field[i]->application
> 
> 

Sending a v3 with the changes.



  reply	other threads:[~2023-01-11 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  7:26 [PATCH] HID: Recognize sensors with application collections too Aditya Garg
2023-01-10  8:55 ` [PATCH RESEND] " Aditya Garg
2023-01-10  8:57   ` [PATCH v2] " Aditya Garg
2023-01-10 22:16     ` srinivas pandruvada
2023-01-11 10:06       ` Aditya Garg [this message]
2023-01-11 10:07     ` [PATCH v3] HID: Recognize sensors with application collections Aditya Garg
2023-01-11 16:59       ` srinivas pandruvada
2023-01-18  8:54       ` 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=A02BE14A-8532-4C2D-940B-06DCCDB005D3@live.com \
    --to=gargaditya08@live.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jic23@kernel.org \
    --cc=jikos@kernel.org \
    --cc=jkosina@suse.cz \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orlandoch.dev@gmail.com \
    --cc=ronald@innovation.ch \
    --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