public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Orlando Chamberlain <redecorating@protonmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3] mfd: intel-lpss: Add support for MacBookPro16,2 ICL-N UART
Date: Mon, 4 Oct 2021 07:53:54 +0100	[thread overview]
Message-ID: <YVqlAsb1127/KXnb@google.com> (raw)
In-Reply-To: <20211002111221.1c3076f3@localhost>

On Sat, 02 Oct 2021, Orlando Chamberlain wrote:

> On Sat, 02 Oct 2021 21:04:30 +1000
> "Andy Shevchenko" <andriy.shevchenko@linux.intel.com> wrote:
> 
> > You ignoring my Reviewed-by tag. Any reason why?
> 
> Sorry, I'm new to this and assumed it needed to be reviewed again after
> any changes (including to the commit message).
> 
> > Besides that you are posting patches as continuation of the thread.
> > It may be problematic for some tools, like `b4`, although I dunno if
> > Lee is using such tools.
> 
> I'll make a v4 with the reviewed-by line. I'll make it a reply to the
> first version of the patch, and hopefully that'll be the first place
> tools like `b4` look.

You only need to add the *-by lines to *new* submissions.

Please don't submit new versions just to add *-by lines.

`b4` doesn't support replied-to patch-sets, so even replying-to the
very first submission/version won't help here.  Submissions need to be
completely separate.

FWIW: As it happens, I do use `b4`, but I don't use the auto-apply-set
functionality.  I either apply patches individually or select (tag)
the ones I wish to apply, so I do not suffer from this problem like
some others do.

> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > 
> > > Signed-off-by: Orlando Chamberlain <redecorating@protonmail.com>
> > > ---
> > > v2->v3: Mention "ICL-N" in commit message.
> > >  drivers/mfd/intel-lpss-pci.c | 2 ++
> > >  1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/mfd/intel-lpss-pci.c
> > > b/drivers/mfd/intel-lpss-pci.c index c54d19fb184c..a872b4485eac
> > > 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 }, --
> > > 2.33.0
> > >
> > >  
> > 
> 
> 
> 

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2021-10-04  6:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  8:51 [PATCH] mfd: intel-lpss: Add support for MacBookPro16,2 UART Orlando Chamberlain
2021-10-01 10:16 ` Andy Shevchenko
2021-10-01 10:40   ` [PATCHv2] " Orlando Chamberlain
2021-10-01 11:04     ` Andy Shevchenko
2021-10-01 18:14   ` [PATCH] " Lee Jones
2021-10-01 18:22     ` Andy Shevchenko
2021-10-02  3:31       ` [PATCHv3] mfd: intel-lpss: Add support for MacBookPro16,2 ICL-N UART Orlando Chamberlain
2021-10-02 11:04         ` Andy Shevchenko
2021-10-02 11:12           ` Orlando Chamberlain
2021-10-02 12:07             ` Andy Shevchenko
2021-10-04  6:53             ` Lee Jones [this message]
2021-10-04  7:16       ` [PATCH] mfd: intel-lpss: Add support for MacBookPro16,2 UART Lee Jones
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=YVqlAsb1127/KXnb@google.com \
    --to=lee.jones@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=redecorating@protonmail.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