From: Kalle Valo <kvalo@codeaurora.org>
To: Oscar Forner Martinez <oscar.forner.martinez@gmail.com>
Cc: zajec5@gmail.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] Drivers: bcma: Fix three coding style issues, more than 80 characters per line.
Date: Wed, 24 Dec 2014 09:20:59 +0200 [thread overview]
Message-ID: <877fxhbjj8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1419378909-14414-1-git-send-email-oscar.forner.martinez@gmail.com> (Oscar Forner Martinez's message of "Tue, 23 Dec 2014 23:55:09 +0000")
Oscar Forner Martinez <oscar.forner.martinez@gmail.com> writes:
> Three lines with more than 80 characters per line have been split in several lines.
>
> Signed-off-by: Oscar Forner Martinez <oscar.forner.martinez@gmail.com>
> ---
> drivers/bcma/driver_chipcommon.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
Just to handle the bureaucracy before v2 is submitted:
To which tree should this go to? I see that earlier John has applied
patches to drivers/bcma/, but what about now? Should I take these? John,
any suggestions?
Oscar, the patchwork entry for this patch looked odd. I'm guessing it
was because your time (or timezone) is wrong:
https://patchwork.kernel.org/patch/5535751/
--
Kalle Valo
next prev parent reply other threads:[~2014-12-24 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 23:55 [PATCH] Drivers: bcma: Fix three coding style issues, more than 80 characters per line Oscar Forner Martinez
2014-12-23 23:46 ` Rafał Miłecki
2014-12-24 0:55 ` Joe Perches
2014-12-23 23:47 ` Rafał Miłecki
2014-12-24 7:20 ` Kalle Valo [this message]
2014-12-24 9:09 ` Arend van Spriel
2014-12-24 9:44 ` Òscar Forner Martínez
2014-12-26 9:19 ` Rafał Miłecki
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=877fxhbjj8.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=oscar.forner.martinez@gmail.com \
--cc=zajec5@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).