From: Lee Jones <lee.jones@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, "Mark Brown" <broonie@kernel.org>,
"Krzysztof Kozłowski" <k.kozlowski@samsung.com>,
"Charles Keepax" <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily
Date: Tue, 4 Oct 2016 15:41:31 +0100 [thread overview]
Message-ID: <20161004144131.GB29257@dell> (raw)
In-Reply-To: <20161003105615.GB4664@vireshk-i7>
On Mon, 03 Oct 2016, Viresh Kumar wrote:
> On 16-09-16, 08:56, Viresh Kumar wrote:
> > These can fit in a single line (80 columns), don't split lines
> > unnecessarily.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> >
> > ---
> > V1->V2: New patch
> > ---
> > drivers/mfd/wm8994-core.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
>
> Ping!!
Don't do that!
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-10-04 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 3:26 [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily Viresh Kumar
2016-09-16 3:26 ` [PATCH V2 2/3] mfd: wm8994-core: disable regulators before removing them Viresh Kumar
2016-10-26 12:22 ` Lee Jones
2016-09-16 3:27 ` [PATCH V2 3/3] mfd: wm8994-core: Don't use managed regulator bulk get API Viresh Kumar
2016-09-16 7:38 ` Charles Keepax
2016-10-26 12:22 ` Lee Jones
2016-10-26 12:24 ` Lee Jones
2016-09-16 7:37 ` [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily Charles Keepax
2016-10-03 10:56 ` Viresh Kumar
2016-10-04 14:41 ` Lee Jones [this message]
2016-10-05 0:39 ` Viresh Kumar
2016-10-05 8:49 ` Lee Jones
2016-10-05 8:55 ` Viresh Kumar
2016-10-05 9:10 ` Lee Jones
2016-10-26 12:20 ` 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=20161004144131.GB29257@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=k.kozlowski@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=viresh.kumar@linaro.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.