From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1D246C43332 for ; Tue, 26 Jan 2021 17:26:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EA47C207B5 for ; Tue, 26 Jan 2021 17:26:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390205AbhAZR0Q (ORCPT ); Tue, 26 Jan 2021 12:26:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:38052 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389425AbhAZHK7 (ORCPT ); Tue, 26 Jan 2021 02:10:59 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id B0C3E207D0; Tue, 26 Jan 2021 07:09:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1611644976; bh=VUKUXiWtc1WfRrnWZa+PidTl8O0Y71iu0ioZZtcjl8A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TI+CWhWKfvjVqATikcy+T5wHg4nmrMcSREmAxU5grW3dHsNTgSPVAqwfY06s26ubg 8/K9n4OQi2rp+sd+w6yllD3zSgupREk0Mb6tKbXO8p5zMr9kpMj96vP+bLYWnHynmc MEj+5R6Oqz4Q7DqCFyPGcV7srz9duNUrOp2gV1Kk= Date: Tue, 26 Jan 2021 08:09:32 +0100 From: Greg KH To: mateng Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, mateng Subject: Re: [PATCH] Change 'addres' to 'address'. Message-ID: References: <20210126045348.1454-1-ayowoe@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210126045348.1454-1-ayowoe@163.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 26, 2021 at 12:53:48PM +0800, mateng wrote: > From: mateng > > Signed-off-by: mateng > --- > drivers/misc/vmw_vmci/vmci_queue_pair.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/misc/vmw_vmci/vmci_queue_pair.h b/drivers/misc/vmw_vmci/vmci_queue_pair.h > index 00017fc..c4e6e92 100644 > --- a/drivers/misc/vmw_vmci/vmci_queue_pair.h > +++ b/drivers/misc/vmw_vmci/vmci_queue_pair.h > @@ -104,7 +104,7 @@ struct vmci_qp_dtch_info { > struct vmci_qp_page_store { > /* Reference to pages backing the queue pair. */ > u64 pages; > - /* Length of pageList/virtual addres range (in pages). */ > + /* Length of pageList/virtual address range (in pages). */ > u32 len; > }; > > -- > 1.9.1 > Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what is needed in order to properly describe the change. - You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what a proper Subject: line should look like. - It looks like you did not use your "real" name for the patch on either the Signed-off-by: line, or the From: line (both of which have to match). Please read the kernel file, Documentation/SubmittingPatches for how to do this correctly. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot