From: Greg KH <gregkh@linuxfoundation.org>
To: Yonglin Tan <yonglin.tan@outlook.com>
Cc: mani@kernel.org, quic_hemantk@quicinc.com,
loic.poulain@linaro.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bus: mhi: host: Add support for Quectel EM120 FCCL project.
Date: Fri, 13 May 2022 09:10:12 +0200 [thread overview]
Message-ID: <Yn4EVHr/xrgB0kom@kroah.com> (raw)
In-Reply-To: <MEYP282MB23742A3646D681AF27BED85EFDCA9@MEYP282MB2374.AUSP282.PROD.OUTLOOK.COM>
On Fri, May 13, 2022 at 03:00:25PM +0800, Yonglin Tan wrote:
> From: ylintan <yonglin.tan@outlook.com>
>
> This patch add VendorID/DeviceID definitions for EM120 FCCL project.
> It has the same configration as Quectel EM160R-GL and EM120R-GL.
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Hemant Kumar <hemantk@codeaurora.org>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Signed-off-by: Yonglin Tan <yonglin.tan@outlook.com>
> ---
> drivers/bus/mhi/host/pci_generic.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bus/mhi/host/pci_generic.c b/drivers/bus/mhi/host/pci_generic.c
> index 8416267..0a6469c 100644
> --- a/drivers/bus/mhi/host/pci_generic.c
> +++ b/drivers/bus/mhi/host/pci_generic.c
> @@ -557,6 +557,8 @@ static const struct pci_device_id mhi_pci_id_table[] = {
> .driver_data = (kernel_ulong_t) &mhi_quectel_em1xx_info },
> { PCI_DEVICE(0x1eac, 0x1002), /* EM160R-GL (sdx24) */
> .driver_data = (kernel_ulong_t) &mhi_quectel_em1xx_info },
> + { PCI_DEVICE(0x1eac, 0x2001), /* EM120R-GL for FCCL (sdx24) */
> + .driver_data = (kernel_ulong_t) &mhi_quectel_em1xx_info },
> /* T99W175 (sdx55), Both for eSIM and Non-eSIM */
> { PCI_DEVICE(PCI_VENDOR_ID_FOXCONN, 0xe0ab),
> .driver_data = (kernel_ulong_t) &mhi_foxconn_sdx55_info },
> --
> 2.7.4
>
Ok, please stop and take a minute and go through the basic "how do I
write a kernel patch" tutorial on kernelnewbies.org.
You are submitting a patch that has a number of obvious things wrong
with it:
- invalid from: line that does not match the signed-off-by line
- made up out of thin air "reviewed-by:" lines from people who
have OBVIOUSLY NOT REVIEWED THIS PATCH!
- indented changelog text in an odd format
- extra spaces in the subject line
- no versioning in the subject line, or below the --- line as
the documentation requires
Please take some time off, and come back next week with this all fixed
up AFTER you have gone through the kernelnewbies tutorial AND you have
read all of the Documentation/process/submitting-patches.rst file.
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-13 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 7:00 [PATCH] bus: mhi: host: Add support for Quectel EM120 FCCL project Yonglin Tan
2022-05-13 7:10 ` Greg KH [this message]
2022-05-13 8:22 ` 回复: " 谭 永林
2022-05-13 8:43 ` Manivannan Sadhasivam
2022-05-13 8:53 ` 回复: " 谭 永林
-- strict thread matches above, loose matches on Subject: below --
2022-05-13 5:59 Yonglin Tan
2022-05-13 6:05 ` Greg KH
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=Yn4EVHr/xrgB0kom@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_hemantk@quicinc.com \
--cc=yonglin.tan@outlook.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