All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Cameron Williams <cang1@live.co.uk>
Cc: jirislaby@kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 1/7] tty: 8250: Fix IS-200 PCI ID comment
Date: Sat, 14 Oct 2023 20:28:59 +0200	[thread overview]
Message-ID: <2023101411-disarray-olive-afc3@gregkh> (raw)
In-Reply-To: <DU0PR02MB7899E040B68084B59972EC66C4D1A@DU0PR02MB7899.eurprd02.prod.outlook.com>

On Sat, Oct 14, 2023 at 12:56:31PM +0100, Cameron Williams wrote:
> On Sat, Oct 14, 2023 at 10:28:33AM +0200, Greg KH wrote:
> > On Fri, Oct 13, 2023 at 11:11:09PM +0100, Cameron Williams wrote:
> > > Fix the PCI comment for the IS-200 card
> > 
> > "Fix" it how?  What was wrong with it, and what is now right with it?
> >
> I should have specified better, my mistake. The PCI ID comment (135a.0811)
> is incorrect, the card ID itself is 0x0d80 and the definition used
> (PCI_DEVICE_ID_INTASHIELD_IS200) is indeed 0x0d80. It's just a cosmetic change
> as the rest of the IS range of cards are also being added in this series and their
> IDs are all 0x0020 offset from each other (though the IS-300, 0x0da0 is in a
> parport_serial patch). Makes no functional difference.

Please put that info in the changelog text when you send your next
version.

> > > Signed-off-by: Cameron Williams <cang1@live.co.uk>
> > > ---
> > > This is a resubmission series for the patch series below. That series
> > > was lots of changes sent to lots of maintainers, this series is just for
> > > the tty/serial/8250 subsystem.
> > 
> > Your patches here are not threaded at all, was that intentional?  Our
> > tools will not pick them up properly, and so I would have to do it by
> > hand, slowing things down and making me dread handling them.  Any reason
> > you didn't just use 'git send-email' to send it?
> > 
> This was not intentional, no. I had problems getting git send-email set up,
> somthing to do with TLS issues and since Mutt was already set up for general
> email, I chose to use that instead for convenience. I can look into getting
> git send-email working and re-sending this series as v3 if you want the
> series threading properly.

You can use mutt to thread things, you need to do it "by hand" with
mutt, that's what I used to do all the time before git send-email was
created (it's based on some old scripts of mine.)  But I would recommend
setting up git send-email if you want to send lots of patches over time.

thanks,

greg k-h

      reply	other threads:[~2023-10-14 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 22:11 [PATCH v2 1/7] tty: 8250: Fix IS-200 PCI ID comment Cameron Williams
2023-10-14  8:28 ` Greg KH
2023-10-14 11:56   ` Cameron Williams
2023-10-14 18:28     ` Greg KH [this message]

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=2023101411-disarray-olive-afc3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cang1@live.co.uk \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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.