From: "dbasehore ." <dbasehore@chromium.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
jingoohan1@gmail.com, Lee Jones <lee.jones@linaro.org>,
briannorris@chromium.org, linux-pwm@vger.kernel.org,
Derek Basehore <dbasehore@chromium.org>
Subject: Re: [PATCH v2] pwm_bl: Fix overflow condition
Date: Tue, 29 Aug 2017 13:42:30 -0700 [thread overview]
Message-ID: <CAGAzgsr_6ddSs5D-GsnHWvBHmpBbn=WBgf4ROuz3_pKF8TOPXQ@mail.gmail.com> (raw)
In-Reply-To: <20170829204002.8663-1-dbasehore@chromium.org>
Okay, I think that this is just my email client confusing me. Please
ignore this email and just review the first "PATCH v2" patch.
next prev parent reply other threads:[~2017-08-29 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 20:40 [PATCH v2] pwm_bl: Fix overflow condition Derek Basehore
2017-08-29 20:42 ` dbasehore . [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-29 20:34 Derek Basehore
2017-08-29 20:46 ` Brian Norris
2017-08-30 14:27 ` Thierry Reding
2017-08-30 16:26 ` Brian Norris
2017-09-04 15:16 ` Lee Jones
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='CAGAzgsr_6ddSs5D-GsnHWvBHmpBbn=WBgf4ROuz3_pKF8TOPXQ@mail.gmail.com' \
--to=dbasehore@chromium.org \
--cc=briannorris@chromium.org \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.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).