mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacobe Zang <jacobe.zang@wesion.com>
To: "Ondřej Jirman" <megi@xff.cz>
Cc: "arend.vanspriel@broadcom.com" <arend.vanspriel@broadcom.com>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"duoming@zju.edu.cn" <duoming@zju.edu.cn>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"minipli@grsecurity.net" <minipli@grsecurity.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"brcm80211@lists.linux.dev" <brcm80211@lists.linux.dev>,
	"brcm80211-dev-list.pdl@broadcom.com"
	<brcm80211-dev-list.pdl@broadcom.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"heiko@sntech.de" <heiko@sntech.de>, Nick Xie <nick@khadas.com>,
	"efectn@protonmail.com" <efectn@protonmail.com>,
	"jagan@edgeble.ai" <jagan@edgeble.ai>,
	"dsimic@manjaro.org" <dsimic@manjaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 3/3] net: wireless: brcmfmac: Add support for AP6275P
Date: Sun, 23 Jun 2024 02:21:39 +0000	[thread overview]
Message-ID: <TYZPR03MB700154AE39D44B8D166344BF80CB2@TYZPR03MB7001.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <fro2xcwsnvbxmpszny6g2p36z4zwoq4kegmpvww4twxir5piez@a3c2nbwitmab>

> Any reason to strip info about origin of the patch, my SoB and
> present this work as your own?

Sincerely express my apology to Ondrej. It's really my mistake. After getting your permission if I could submit the patches. I jsut think if the author and submitter is not the same person is strange so I changed it. Next tiem I will avoid this mistake. Apologize again.


> I sincerely hope this is just a rookie mistake so please carefully read
the URL below:

> https://www.kernel.org/doc/html/latest/process/submitting-patches.html

Thanks for the guidance Arend. After reading the document I realized what a stupid mistake I made.

BTW I have another question, except the SoB of the real author, should I also post the original link in commit message?

---
Best Regards
Jacobe

  parent reply	other threads:[~2024-06-23  2:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  2:00 [PATCH v1 0/3] Add AP6275P wireless support Jacobe Zang
2024-06-20  2:00 ` [PATCH v1 1/3] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2 Jacobe Zang
2024-06-20  2:00 ` [PATCH v1 2/3] net: wireless: brcmfmac: Add optional 32k clock enable support Jacobe Zang
2024-06-20  6:22   ` Ondřej Jirman
2024-06-20  6:54   ` Krzysztof Kozlowski
2024-06-21  1:45     ` Jacobe Zang
2024-06-21  4:59       ` Arend Van Spriel
2024-06-21  6:03       ` Krzysztof Kozlowski
2024-06-21  7:45         ` Jacobe Zang
2024-06-21 10:06           ` Krzysztof Kozlowski
2024-06-20  2:00 ` [PATCH v1 3/3] net: wireless: brcmfmac: Add support for AP6275P Jacobe Zang
2024-06-22  0:22   ` Ondřej Jirman
2024-06-22 10:59     ` Arend van Spriel
2024-06-23  2:21     ` Jacobe Zang [this message]
2024-06-23  5:34       ` Arend Van Spriel
2024-06-23  8:01       ` Ondřej Jirman
2024-06-23 10:11         ` Jacobe Zang
2024-06-20 17:33 ` [PATCH v1 0/3] Add AP6275P wireless support Arend Van Spriel
2024-06-21  0:18   ` Jacobe Zang

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=TYZPR03MB700154AE39D44B8D166344BF80CB2@TYZPR03MB7001.apcprd03.prod.outlook.com \
    --to=jacobe.zang@wesion.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=duoming@zju.edu.cn \
    --cc=efectn@protonmail.com \
    --cc=heiko@sntech.de \
    --cc=jagan@edgeble.ai \
    --cc=krzk+dt@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=megi@xff.cz \
    --cc=minipli@grsecurity.net \
    --cc=nick@khadas.com \
    --cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®