From: Kalle Valo <kvalo@codeaurora.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH V2] bcma: clean bus initialization code
Date: Thu, 22 Jan 2015 16:01:10 +0200 [thread overview]
Message-ID: <87ppa6ncd5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <54BBFCE5.9050500@hauke-m.de> (Hauke Mehrtens's message of "Sun, 18 Jan 2015 19:35:17 +0100")
Hauke Mehrtens <hauke@hauke-m.de> writes:
> On 01/16/2015 08:59 PM, Rafał Miłecki wrote:
>> This moves main bus init code to the main.c and renames old function to
>> make its purpose clear.
>> Thanks to this change we'll also be able to separate scanning from
>> registration (and support PCIe Gen 2 devices) in the future.
>>
>> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
No need to change anything now, but I think that in cases like this you
should use Acked-by:
"13) When to use Acked-by: and Cc:
The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery
path.
If a person was not directly involved in the preparation or handling
of a patch but wishes to signify and record their approval of it then
they can arrange to have an Acked-by: line added to the patch's
changelog.
Acked-by: is often used by the maintainer of the affected code when
that maintainer neither contributed to nor forwarded the patch."
--
Kalle Valo
next prev parent reply other threads:[~2015-01-22 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 19:18 [PATCH] bcma: clean bus initialiation code Rafał Miłecki
2015-01-16 19:59 ` [PATCH V2] bcma: clean bus initialization code Rafał Miłecki
2015-01-18 18:35 ` Hauke Mehrtens
2015-01-22 14:01 ` Kalle Valo [this message]
2015-01-22 20:55 ` Hauke Mehrtens
2015-01-23 17:49 ` Kalle Valo
2015-01-23 19:16 ` Rafał Miłecki
2015-01-23 19:30 ` 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=87ppa6ncd5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--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.