From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Oscar Forner Martinez <oscar.forner.martinez@gmail.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] bcma: fix two coding style issues, more than 80 characters per line.
Date: Wed, 07 Jan 2015 20:39:44 +0200 [thread overview]
Message-ID: <87y4peo2of.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CACna6rzWaHg=M15q=swf+yqMEB3smRRANuLHkSK1dU1MtG8jgg@mail.gmail.com> ("Rafał Miłecki"'s message of "Wed, 7 Jan 2015 19:12:30 +0100")
Rafał Miłecki <zajec5@gmail.com> writes:
> On 7 January 2015 at 18:55, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Oscar Forner Martinez <oscar.forner.martinez@gmail.com> writes:
>>
>>> Two 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>
>>
>> Thanks, applied to wireless-drivers-next.git.
>
> Could you still replace it (V4) with an older version (V3)? Before I
> explained V3 was OK Oscar already sent this (worse) V4.
No. I'm not going to rebase a public git tree unless there's a huge
disaster.
But if I see V4 I'm going to assume that's the one I need to apply, not
some older version. If V4 is not good for some reason, make it
ABSOLUTELY clear that I should not apply it. I do not want to start
guessing what patch I should apply.
> This is not critical though, we can always send separated patch for
> one more line > 80 chars.
Please send a followup patch if you want to fix something.
--
Kalle Valo
next prev parent reply other threads:[~2015-01-07 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 11:37 [PATCH v4] bcma: fix two coding style issues, more than 80 characters per line Oscar Forner Martinez
2015-01-07 17:55 ` Kalle Valo
2015-01-07 18:12 ` Rafał Miłecki
2015-01-07 18:39 ` Kalle Valo [this message]
2015-01-07 20:54 ` Rafał Miłecki
2015-01-09 14:03 ` Kalle Valo
2015-01-09 14:38 ` Rafał Miłecki
2015-01-09 14:43 ` Kalle Valo
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=87y4peo2of.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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