All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH v3 2/2] hwmon: (ads1015) Use of_property_read_u32 at appropriate places
Date: Tue, 05 Aug 2014 05:00:26 +0000	[thread overview]
Message-ID: <53E064EA.10300@roeck-us.net> (raw)
In-Reply-To: <1407204038.20206.1.camel@phoenix>

On 08/04/2014 07:52 PM, Axel Lin wrote:
> 2014-08-05 10:49 GMT+08:00 Guenter Roeck <linux@roeck-us.net>:
>> On 08/04/2014 07:00 PM, Axel Lin wrote:
>>>
>>> Simplify the code a bit and also improve readability.
>>>
>>> Signed-off-by: Axel Lin <axel.lin@ingics.com>
>>
>>
>> Hi Axel,
>>
>> Unfortunately, this patch does not apply for me. Looks like your branch is
>> missing
>> commit 56de1377 (hwmon: (ads1015) Fix off-by-one for valid channel index
>> checking).
>> Can you rebase your branch to make sure it is included ? The above patch
>> should
>> hopefully be in mainline in a day or so, but you should have it already
>> (after all,
>> it is one of your patches ;-).
> It's because I use linux-next tree.
> And the commit 56de1377 (hwmon: (ads1015) Fix off-by-one for valid
> channel index checking is still
> not in linux-next (20140804).
>
Yeah, sorry. I missed to rebase my -next branch to my bug-fix branch
last week, and only noticed this morning when I prepared my pull request.
Vacation does that for you. I already got a ding on my head for it from
Stephen, with copy to Linus :-(.

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2014-08-05  5:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  2:00 [lm-sensors] [PATCH v3 2/2] hwmon: (ads1015) Use of_property_read_u32 at appropriate places Axel Lin
2014-08-05  2:49 ` Guenter Roeck
2014-08-05  2:52 ` Axel Lin
2014-08-05  5:00 ` Guenter Roeck [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=53E064EA.10300@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@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.