From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Oscar Forner Martinez <oscar.forner.martinez@gmail.com>,
<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 10:09:10 +0100 [thread overview]
Message-ID: <549A82B6.40105@broadcom.com> (raw)
In-Reply-To: <877fxhbjj8.fsf@kamboji.qca.qualcomm.com>
On 12/24/14 08:20, Kalle Valo wrote:
> 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?
It is a bit of an odd ball, but there are couple of wireless driver
relying on bcma and it is more than just a bus driver. It also does some
steps of the device initialization (which is convenient, but not sure I
like it). So I would hope it can stay with wireless subsystem to catch
issue caused in that area early on.
Regards,
Arend
> 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/
>
next prev parent reply other threads:[~2014-12-24 9:09 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
2014-12-24 9:09 ` Arend van Spriel [this message]
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=549A82B6.40105@broadcom.com \
--to=arend@broadcom.com \
--cc=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 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.