All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Daniel Baluta <daniel.baluta@intel.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: light: hid-sensor-prox: Fix modifier
Date: Sat, 18 Apr 2015 19:12:42 +0100	[thread overview]
Message-ID: <55329E9A.3020805@kernel.org> (raw)
In-Reply-To: <1429199662.24805.40.camel@spandruv-DESK3.jf.intel.com>

On 16/04/15 16:54, Srinivas Pandruvada wrote:
> On Wed, 2015-04-15 at 15:01 +0300, Daniel Baluta wrote: 
>> On Wed, Apr 15, 2015 at 12:53 AM, Srinivas Pandruvada
>> <srinivas.pandruvada@linux.intel.com> wrote:
>>> Currently in_proximity_(null)_raw is getting presented as raw sysfs
>>> attribute. Same with the scan_elements.
>>> The modifier doesn't apply to this channel.
>>>
>>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>>> ---
>>
>> Would be also nice to add a line like this:
>>
>> Fixes COMMIT_ID ("Commit subject")
It is a nice convention, but when it's been a bug for all versions of the
file that have ever been in the tree, it's not so important.
>>
>> in order for stable teams to pick this up.
> We can add tag
> Cc: stable@vger.kernel.org
> 
> Usually Jonathan copies after his merge.
I will indeed.

Applied to the fixes-togreg branch of iio.git and marked for
stable.
> 
> Thanks,
> Srinivas
> 
>>
>> thanks,
>> Daniel.
> 
> 


      reply	other threads:[~2015-04-18 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 21:53 [PATCH] iio: light: hid-sensor-prox: Fix modifier Srinivas Pandruvada
2015-04-15 12:01 ` Daniel Baluta
2015-04-16 15:54   ` Srinivas Pandruvada
2015-04-18 18:12     ` Jonathan Cameron [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=55329E9A.3020805@kernel.org \
    --to=jic23@kernel.org \
    --cc=daniel.baluta@intel.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --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 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.