On Thu, Dec 15, 2022 at 05:21:36PM +0800, cy_huang wrote:
> From: ChiYuan Huang <[email protected]>
Why not send directly from this address so we can validate that this is
the correct email address of yours?
thanks,
greg k-h
Greg KH <[email protected]> 於 2022年12月15日 週四 下午5:44寫道：
>
> On Thu, Dec 15, 2022 at 05:21:36PM +0800, cy_huang wrote:
> > From: ChiYuan Huang <[email protected]>
>
> 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.
Sorry for the inconvinence.
> thanks,
>
> greg k-h
On Thu, Dec 15, 2022 at 05:53:44PM +0800, ChiYuan Huang wrote:
> Greg KH <[email protected]> 於 2022年12月15日 週四 下午5:44寫道：
> >
> > On Thu, Dec 15, 2022 at 05:21:36PM +0800, cy_huang wrote:
> > > From: ChiYuan Huang <[email protected]>
> >
> > 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
On Thu, Dec 15, 2022 at 12:43:35PM +0100, Greg KH wrote:
> On Thu, Dec 15, 2022 at 05:53:44PM +0800, ChiYuan Huang wrote:
> > Greg KH <[email protected]> 於 2022年12月15日 週四 下午5:44寫道：
> > >
> > > On Thu, Dec 15, 2022 at 05:21:36PM +0800, cy_huang wrote:
> > > > From: ChiYuan Huang <[email protected]>
> > >
> > > 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.
Thanks for your comment.
After the work with MIS for several weeks, we finnaly got one way to do it.
But I'm not sure all mail account can receive the mail.
If anyone cannot receive the mail, please inform me.
ChiYuan Huang.
>
> greg k-h
************* Email Confidentiality Notice ********************
The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!
On Mon, Jan 09, 2023 at 09:41:23AM +0800, ChiYuan Huang wrote:
> ************* Email Confidentiality Notice ********************
>
> The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!
Now deleted.
For obvious reasons, this wording is not compatible with kernel
development :(
Greg KH <[email protected]> 於 2023年1月9日 週一 下午2:38寫道：
>
> On Mon, Jan 09, 2023 at 09:41:23AM +0800, ChiYuan Huang wrote:
> > ************* Email Confidentiality Notice ********************
> >
> > The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!
>
> Now deleted.
>
> For obvious reasons, this wording is not compatible with kernel
> development :(
I'm sorry about that. Let me check with MIS..............
On Mon, Jan 09, 2023 at 02:46:34PM +0800, ChiYuan Huang wrote:
> Greg KH <[email protected]> 於 2023年1月9日 週一 下午2:38寫道：
> >
> > On Mon, Jan 09, 2023 at 09:41:23AM +0800, ChiYuan Huang wrote:
> > > ************* Email Confidentiality Notice ********************
> > >
> > > The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!
> >
> > Now deleted.
> >
> > For obvious reasons, this wording is not compatible with kernel
> > development :(
>
> I'm sorry about that. Let me check with MIS..............
This one seems work.
https://www.lkml.org/lkml/2023/1/9/73