From: Greg KH <gregkh@linuxfoundation.org>
To: ChiYuan Huang <u0084500@gmail.com>
Cc: linux@roeck-us.net, heikki.krogerus@linux.intel.com,
matthias.bgg@gmail.com, tommyyl.chen@mediatek.com,
macpaul.lin@mediatek.com, gene_chen@richtek.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
ChiYuan Huang <cy_huang@richtek.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: typec: tcpm: Fix altmode re-registration causes sysfs create fail
Date: Thu, 15 Dec 2022 12:43:35 +0100 [thread overview]
Message-ID: <Y5sIZ3zC6o4ARDEn@kroah.com> (raw)
In-Reply-To: <CADiBU3-iVLQf6Q5SzOB_pMCs2PGcFuWryjpDn5Qvz41WQ6C2RA@mail.gmail.com>
On Thu, Dec 15, 2022 at 05:53:44PM +0800, ChiYuan Huang wrote:
> Greg KH <gregkh@linuxfoundation.org> 於 2022年12月15日 週四 下午5:44寫道：
> >
> > On Thu, Dec 15, 2022 at 05:21:36PM +0800, cy_huang wrote:
> > > From: ChiYuan Huang <cy_huang@richtek.com>
> >
> > Why not send directly from this address so we can validate that this is
> > the correct email address of yours?
> >
> It's the company mailbox policy. To send the external mail, there's
> the security text block at the bottom.
> Except this, some mail address are also blocked. To avoid this, I use
> my personal mail to send the patch
> and leave the SoB for the Richtek mailbox.
> It's lazy to fight for this.
Please fix it, otherwise your company's email address will be spoofed
and people can claim to be sending changes from their domain.
Please fix that up, abusing random gmail addresses like this is not ok,
sorry.
greg k-h
next prev parent reply other threads:[~2022-12-15 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:21 [PATCH] usb: typec: tcpm: Fix altmode re-registration causes sysfs create fail cy_huang
2022-12-15 9:44 ` Greg KH
2022-12-15 9:53 ` ChiYuan Huang
2022-12-15 11:43 ` Greg KH [this message]
2023-01-09 1:41 ` ChiYuan Huang
2023-01-09 6:38 ` Greg KH
2023-01-09 6:46 ` ChiYuan Huang
2023-01-09 7:22 ` ChiYuan Huang
2022-12-15 9:58 ` Macpaul Lin
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=Y5sIZ3zC6o4ARDEn@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cy_huang@richtek.com \
--cc=gene_chen@richtek.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tommyyl.chen@mediatek.com \
--cc=u0084500@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