From: Pho Tran <Pho.Tran@silabs.com>
To: 'Greg KH' <gregkh@linuxfoundation.org>
Cc: 'Pho Tran' <photranvan0712@gmail.com>,
"'johan@kernel.org'" <johan@kernel.org>,
"'linux-usb@vger.kernel.org'" <linux-usb@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
Hung Nguyen <Hung.Nguyen@silabs.com>,
Tung Pham <Tung.Pham@silabs.com>,
'Kernel test robot' <lkp@intel.com>
Subject: RE: [PATCH v7] USB: serial: cp210x: Add support for GPIOs on CP2108
Date: Tue, 6 Apr 2021 09:25:18 +0000 [thread overview]
Message-ID: <DM6PR11MB4441660856AC72EA5764BD43E3769@DM6PR11MB4441.namprd11.prod.outlook.com> (raw)
In-Reply-To: <YGwltSD+iEPmRblS@kroah.com>
Hi Greg!
Should I send the Patch with new version (PATCH v8) or keep version of the Patch is v7?
-----Original Message-----
From: 'Greg KH' <gregkh@linuxfoundation.org>
Sent: Tuesday, April 6, 2021 4:11 PM
To: Pho Tran <Pho.Tran@silabs.com>
Cc: 'Pho Tran' <photranvan0712@gmail.com>; 'johan@kernel.org' <johan@kernel.org>; 'linux-usb@vger.kernel.org' <linux-usb@vger.kernel.org>; 'linux-kernel@vger.kernel.org' <linux-kernel@vger.kernel.org>; Hung Nguyen <Hung.Nguyen@silabs.com>; Tung Pham <Tung.Pham@silabs.com>; 'Kernel test robot' <lkp@intel.com>
Subject: Re: [PATCH v7] USB: serial: cp210x: Add support for GPIOs on CP2108
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On Tue, Apr 06, 2021 at 08:17:42AM +0000, Pho Tran wrote:
> Hi Greg!
> I am grateful for your promptly reply!
> Yesterday, I got the response from the kernel test robot with this message:
> " If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>".
> It's a reason why I added "Reported-by: kernel test robot <lkp@intel.com>"
> to my new Patch.
> Could you tell me what I need to do in the next step to submit this patch to the kernel mainline?
> Once again, Thank you a lot!
If you fixed this as an add-on patch, yes it would belong in the
reported-by: But as you are just fixing this up to a patch that has not been accepted yet, all you need to do is write it in the "what changed from the previous version" section of the changelog, below the --- line.
thanks,
greg k-h
next prev parent reply other threads:[~2021-04-06 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 4:02 [PATCH v7] USB: serial: cp210x: Add support for GPIOs on CP2108 Pho Tran
2021-04-06 5:14 ` Greg KH
2021-04-06 8:17 ` Pho Tran
2021-04-06 9:11 ` 'Greg KH'
2021-04-06 9:25 ` Pho Tran [this message]
2021-04-06 9:34 ` '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=DM6PR11MB4441660856AC72EA5764BD43E3769@DM6PR11MB4441.namprd11.prod.outlook.com \
--to=pho.tran@silabs.com \
--cc=Hung.Nguyen@silabs.com \
--cc=Tung.Pham@silabs.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=photranvan0712@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).