All of lore.kernel.org
 help / color / mirror / Atom feed
From: "andriy.shevchenko@linux.intel.com"  <andriy.shevchenko@linux.intel.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Orlando Chamberlain <redecorating@protonmail.com>
Subject: Re: [PATCHv4] mfd: intel-lpss: Add support for MacBookPro16,2 ICL-N UART
Date: Fri, 22 Oct 2021 18:09:13 +0300	[thread overview]
Message-ID: <YXLUGCC9GdY4SeH6@smile.fi.intel.com> (raw)
In-Reply-To: <PNZPR01MB44151488C970DB48157D5AFCB8809@PNZPR01MB4415.INDPRD01.PROD.OUTLOOK.COM>

On Fri, Oct 22, 2021 at 12:43:33PM +0000, Aditya Garg wrote:
> I am really sorry. I don’t have any experience regarding submitting patches upstream. I copied and pasted the diff generated using git. My email client doesn’t seem to support git send email. I would be happy if I could get some guidance.

First and very important guidance: do not top-post!

Next, as Lee pointed out there are available documents on how to submit patches
properly. Please, read them (they are available inside kernel source tree as
well).

TL;DR: again as Lee said, `git format-patch` (produces a file in mbox format)
followed by `git send-email` will suffice.

> From: Lee Jones <lee.jones@linaro.org>
> Sent: Friday, October 22, 2021 1:28:42 PM
> To: Aditya Garg <gargaditya08@live.com>
> Cc: andriy.shevchenko@linux.intel.com <andriy.shevchenko@linux.intel.com>; stable@vger.kernel.org <stable@vger.kernel.org>; Orlando Chamberlain <redecorating@protonmail.com>
> Subject: Re: [PATCHv4] mfd: intel-lpss: Add support for MacBookPro16,2 ICL-N UART
> 
> On Fri, 22 Oct 2021, Aditya Garg wrote:
> 
> >
> > From 76d8253d90233b2c2d3fbc82355c603bf0eb9964 Mon Sep 17 00:00:00 2001
> > From: Orlando Chamberlain <redecorating@protonmail.com>
> > Date: Fri, 1 Oct 2021 13:30:19 +0530
> > Subject: [PATCH] Add support for MacBookPro16,2 UART
> > Cc: stable@vger.kernel.org
> 
> What is this?
> 
> These headers should not be part of the patch.
> 
> How are you submitting this?
> What tools are you using?
> Did you read the documents I sent you (see below)?
> 
> > Added 8086:38a8 to the intel_lpss_pci driver. It is an Intel Ice Lake PCH-N UART controller present on the MacBookPro16,2.
> 
> This line is too long.
> 
> > Signed-off-by: Aditya Garg <gargaditya08@live.com>
> > ---
> >  drivers/mfd/intel-lpss-pci.c | 2 ++
> >  1 file changed, 2 insertions(+)
> 
> This diff looks better.
> 
> > diff --git a/drivers/mfd/intel-lpss-pci.c b/drivers/mfd/intel-lpss-pci.c
> > index c54d19fb1..33d5043fd 100644
> > --- a/drivers/mfd/intel-lpss-pci.c
> > +++ b/drivers/mfd/intel-lpss-pci.c
> > @@ -253,6 +253,8 @@ static const struct pci_device_id intel_lpss_pci_ids[] = {
> >        { PCI_VDEVICE(INTEL, 0x34ea), (kernel_ulong_t)&bxt_i2c_info },
> >        { PCI_VDEVICE(INTEL, 0x34eb), (kernel_ulong_t)&bxt_i2c_info },
> >        { PCI_VDEVICE(INTEL, 0x34fb), (kernel_ulong_t)&spt_info },
> > +     /* ICL-N*/
> > +     { PCI_VDEVICE(INTEL, 0x38a8), (kernel_ulong_t)&bxt_uart_info },
> >        /* TGL-H */
> >        { PCI_VDEVICE(INTEL, 0x43a7), (kernel_ulong_t)&bxt_uart_info },
> >        { PCI_VDEVICE(INTEL, 0x43a8), (kernel_ulong_t)&bxt_uart_info },
> >
> > > On 21-Oct-2021, at 4:45 PM, Lee Jones <lee.jones@linaro.org> wrote:
> > >
> > > On Thu, 14 Oct 2021, andriy.shevchenko@linux.intel.com wrote:
> > >
> > >> On Thu, Oct 14, 2021 at 04:15:05AM +0000, Aditya Garg wrote:
> > >>
> > >> Entire message looks like a mess. Are you sure you are using proper tools
> > >> for sending it?
> > >
> > > Agreed.
> > >
> > > I can't apply this until it's submitted properly.
> > >
> > > - Please read Documentation/process/submitting-patches.rst
> > > - Please read Documentation/process/coding-style.rst
> > >
> > > If you have any questions, please reach out.  We're happy to help.
> > >
> 
> This quoted text can't be part of a submitted patch.
> 
> Please submit the patch on its own, as a new thread, using the correct
> tooling (provided mostly by the Git package (i.e. `git format-patch`
> and `git send-email`).
> 
> If you're stuck, or there is something you do not understand, please
> ask.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2021-10-22 15:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  4:05 [PATCHv4] mfd: intel-lpss: Add support for MacBookPro16,2 ICL-N UART Aditya Garg
2021-10-12 11:58 ` Lee Jones
2021-10-14  4:15   ` Aditya Garg
2021-10-14 14:33     ` andriy.shevchenko
2021-10-21 11:15       ` Lee Jones
2021-10-22  4:24         ` Aditya Garg
2021-10-22  6:02           ` Greg KH
2021-10-22  7:58           ` Lee Jones
     [not found]             ` <PNZPR01MB44151488C970DB48157D5AFCB8809@PNZPR01MB4415.INDPRD01.PROD.OUTLOOK.COM>
2021-10-22 15:09               ` andriy.shevchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-01  8:51 [PATCH] mfd: intel-lpss: Add support for MacBookPro16,2 UART Orlando Chamberlain
2021-10-02 11:16 ` [PATCHv4] mfd: intel-lpss: Add support for MacBookPro16,2 ICL-N UART Orlando Chamberlain
2021-10-04  7:17   ` Lee Jones
2021-10-04 15:58     ` Aditya Garg
2021-10-04 16:10       ` Lee Jones

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=YXLUGCC9GdY4SeH6@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gargaditya08@live.com \
    --cc=lee.jones@linaro.org \
    --cc=redecorating@protonmail.com \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.