From: tjiang@codeaurora.org
To: Matthias Kaehlcke <mka@chromium.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
bgodavar@codeaurora.org, c-hbandi@codeaurora.org,
hemantg@codeaurora.org, rjliao@codeaurora.org,
zijuhu@codeaurora.org
Subject: Re: [PATCH v3] Bluetooth: btusb: Add support for variant WCN6855 by using different nvm
Date: Thu, 28 Oct 2021 15:15:01 +0800 [thread overview]
Message-ID: <a04518bd30761a2fecfbee8f435d4daf@codeaurora.org> (raw)
In-Reply-To: <YXl3S7TT30PFfyB8@google.com>
Thanks Matthias for the comments.
the conclusion is that I can continue to use this patch , right ? thank
you.
regards.
tim
On 2021-10-27 23:59, Matthias Kaehlcke wrote:
> On Wed, Oct 27, 2021 at 02:12:07PM +0800, tjiang@codeaurora.org wrote:
>> Hi Matthias:
>> the previous patch is submitted by zijun , as he is not working on
>> this
>> project, I take over his job, so can we assume abandon the previous
>> patch,
>> using my new patch ? thank you.
>> regards.
>
> Your patch is clearly based on zijun's one, it even has the same
> subject. A
> change of authorship shouldn't result in resetting the version number,
> it's
> still the same patch/series. You can always add a 'Co-developed-by:'
> tag to
> indicate that someone else contributed to a patch, or use a 'From:' tag
> if
> you only made minor changes on top of someone else's work.
>
> Not sure how to proceed best with the version number, especially since
> there
> are already 3 versions of the 'new' patch. Either option can create
> confusion,
> I guess you can continue with the new scheme, it seems the patch is
> almost
> ready to land anyway.
next prev parent reply other threads:[~2021-10-28 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 5:35 [PATCH v3] Bluetooth: btusb: Add support for variant WCN6855 by using different nvm tjiang
2021-10-26 5:53 ` tjiang
2021-10-26 16:24 ` Matthias Kaehlcke
2021-10-27 6:12 ` tjiang
2021-10-27 15:59 ` Matthias Kaehlcke
2021-10-28 7:15 ` tjiang [this message]
2021-10-28 14:00 ` Marcel Holtmann
2021-10-29 3:09 ` tjiang
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=a04518bd30761a2fecfbee8f435d4daf@codeaurora.org \
--to=tjiang@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=c-hbandi@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=rjliao@codeaurora.org \
--cc=zijuhu@codeaurora.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.