From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
Subject: Re: [PATCH] serial: 8250_pci: remove unreachable code for ASIX devices
Date: Wed, 24 May 2023 17:01:15 +0300 (EEST) [thread overview]
Message-ID: <62142324-dc90-788a-f040-72ef11192e6@linux.intel.com> (raw)
In-Reply-To: <aee8ff85-5716-424e-3773-33700fd90dc2@linux.intel.com>
On Wed, 24 May 2023, Jiaqing Zhao wrote:
> On 2023-05-15 11:49, Greg Kroah-Hartman wrote:
> > On Mon, May 15, 2023 at 10:36:30AM +0800, Jiaqing Zhao wrote:
> >> On 2023-05-13 18:28, Greg Kroah-Hartman wrote:
> >>> Please follow the documented Intel kernel developer requirements before
> >>> you submit this again, based on the changes that process will require.
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >> Sorry I am unable to find this "Intel kernel developer requirements". Is
> >> there any link or contact where I can find this information? Thank you.
> >
> > Contact the Intel Linux developer team and they will point you at them.
> > This is a company-wide requirement, it is odd that your normal "Here is
> > how you can contribute to Linux!" training at Intel did not cover it?
>
> I contacted them and there is no reply so far. Could you please tell me if
> there is any general available docs about this or point out what I'm doing
> wrong in this patch? Thank you very much.
I've pointed him to the right direction (now that I noticed this has
just gone on here).
--
i.
prev parent reply other threads:[~2023-05-24 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 14:28 Jiaqing Zhao
2023-05-13 10:28 ` Greg Kroah-Hartman
2023-05-15 2:36 ` Jiaqing Zhao
2023-05-15 3:49 ` Greg Kroah-Hartman
2023-05-24 11:52 ` Jiaqing Zhao
2023-05-24 14:01 ` Ilpo Järvinen [this message]
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=62142324-dc90-788a-f040-72ef11192e6@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiaqing.zhao@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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®