From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH 1/2 v2] regulator: add missing description for set_over_current_protection
Date: Wed, 23 Mar 2016 11:53:46 +0000 [thread overview]
Message-ID: <56F283CA.6050703@osg.samsung.com> (raw)
In-Reply-To: <20160323114548.GJ2566@sirena.org.uk>
On 23/03/16 11:45, Mark Brown wrote:
> On Wed, Mar 23, 2016 at 11:35:39AM +0000, Luis de Bethencourt wrote:
>
>> Sorry. I missed this second missing description related to over current
>> protection in regulator_linear_range struct.
>
> Please don't send new patches in reply to old ones, especially not
> individual ones in the middle of a series. It makes it much harder to
> tell what's going on and what current versions of things are.
>
My bad. Next time I will send the [v2] as a new thread.
Sorry for making it harder to read,
Luis
next prev parent reply other threads:[~2016-03-23 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 11:23 [PATCH 0/2] regulator: add missing descriptions for docs Luis de Bethencourt
2016-03-23 11:24 ` [PATCH 1/2] regulator: add missing description for set_over_current_protection Luis de Bethencourt
2016-03-23 11:35 ` [PATCH 1/2 v2] " Luis de Bethencourt
2016-03-23 11:45 ` Mark Brown
2016-03-23 11:53 ` Luis de Bethencourt [this message]
2016-03-23 13:43 ` Applied "regulator: add missing description for set_over_current_protection" to the regulator tree Mark Brown
2016-03-23 11:24 ` [PATCH 2/2] regulator: add missing descriptions in regulator_desc Luis de Bethencourt
2016-03-23 13:43 ` Applied "regulator: add missing descriptions in regulator_desc" to the regulator tree Mark Brown
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=56F283CA.6050703@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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.