From: Greg KH <greg@kroah.com>
To: Matt Schulte <matts@commtech-fastcom.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-serial@vger.kernel.org
Subject: Re: New serial card development
Date: Tue, 23 Oct 2012 11:38:59 -0700 [thread overview]
Message-ID: <20121023183859.GA3317@kroah.com> (raw)
In-Reply-To: <CAJp1Oe67Jd+FaaDPosexrVrrUFS=c-0FUZx_JHTbpTN5RCCcUw@mail.gmail.com>
On Tue, Oct 23, 2012 at 11:31:41AM -0500, Matt Schulte wrote:
> On Tue, Oct 23, 2012 at 11:27 AM, Matt Schulte
> <matts@commtech-fastcom.com> wrote:
> > On Fri, Oct 19, 2012 at 4:21 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> >> Alan's advice to get your card working as a basic serial card is very
> >> good one. Get basic functionality working, and then you can add the
> >> support for the extra bits later....
> >
> > I can see the logic in getting it working as a basic serial card
> > first. I think at minimum I would still need to implement the extra
> > divisor calculations to get accurate bit rates.
> >
> > So when it works as a basic serial card, I assume you would want me to
> > use the default PCI IDs to keep it more generic. Then would I add my
> > own PCI IDs and refer them back to the generic port?
> >
>
> As more of a procedural question, when I go to make the patch(es) to
> submit which, kernel repo do I start with? Do I start with Greg KH's
> tty repo and then generate the patches and submit them here?
That would be a great place to work off of, use the tty-next branch
please.
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-23 18:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 18:43 New serial card development Matt Schulte
2012-10-14 9:37 ` Theodore Ts'o
2012-10-15 19:08 ` Matt Schulte
2012-10-15 23:26 ` Alan Cox
2012-10-16 2:32 ` Theodore Ts'o
2012-10-17 20:24 ` Matt Schulte
2012-10-19 21:21 ` Theodore Ts'o
2012-10-23 16:27 ` Matt Schulte
2012-10-23 16:31 ` Matt Schulte
2012-10-23 18:38 ` Greg KH [this message]
2012-10-29 20:04 ` Matt Schulte
2012-10-31 21:55 ` Matt Schulte
2012-11-01 22:03 ` Matt Schulte
2012-11-01 22:26 ` Alan Cox
2012-11-02 18:47 ` Matt Schulte
2012-11-02 20:21 ` Alan Cox
2012-10-23 18:06 ` Grant Edwards
2012-10-23 18:26 ` Alan Cox
2012-10-23 18:45 ` Grant Edwards
2012-10-23 19:16 ` Greg KH
2012-10-23 19:42 ` Grant Edwards
2012-10-23 20:10 ` Greg KH
2012-10-23 19:24 ` Alan Cox
2012-10-23 19:48 ` Grant Edwards
2012-10-23 20:31 ` Theodore Ts'o
2012-10-23 20:41 ` Grant Edwards
[not found] ` <CAJp1Oe6k7NWqdbYkJnd787JiT55-wSbG+tX1tP7Cy-oPShdVaA@mail.gmail.com>
2012-10-17 20:23 ` Matt Schulte
2012-10-17 21:53 ` Alan Cox
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=20121023183859.GA3317@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-serial@vger.kernel.org \
--cc=matts@commtech-fastcom.com \
--cc=tytso@mit.edu \
/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.