public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Ihalainen Nickolay <ihanic@dev.ehouse.ru>,
	admin@list.net.ru, linux-kernel@vger.kernel.org,
	Wen Xiong <wendyx@us.ibm.com>
Subject: Re: Digi Neo 8: linux-2.6.12_r2  jsm driver
Date: Tue, 12 Apr 2005 10:30:33 -0700	[thread overview]
Message-ID: <20050412173033.GC14857@kroah.com> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F12215B@mtk-sms-mail01.digi.com>

On Tue, Apr 12, 2005 at 11:54:04AM -0500, Kilau, Scott wrote:
> Hi Greg,
> 
> > What features?  Didn't we end up with a valid resolution to all of the
> > additional stuff in the jsm driver that you originally asked for?  Why
> > not work on adding those new features to the serial core, and then
> there
> > would be no issue with accepting your other driver?
> 
> I appreciate your "calm" response. =)
> 
> DPA (Digi Port Authority) support (the special ioctls)
> and /proc (and /sys) files were left unresolved.
> Wendy had no choice but to remove them to get the driver
> into the kernel sources.

I understand.

> IBM was okay with removing them, so I was okay with doing it as well,
> as the whole point of the JSM driver is to support IBM's card directly.
> 
> However, removing those things are just unacceptable for Digi for our
> cards.

Ok, but wasn't it possible to get those additional things added to the
main kernel serial core, which would then provide everything that Digi's
customers are accustomed to?  And then this thread would not be an issue
at all.

And yes, I understand you need to support 2.4, but that's not a
kernel.org issue, and you can continue to have your 2.4 driver.

thanks,

greg k-h

  reply	other threads:[~2005-04-12 17:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 16:54 Digi Neo 8: linux-2.6.12_r2 jsm driver Kilau, Scott
2005-04-12 17:30 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-13 14:25 Kilau, Scott
     [not found] <3SAEx-7Yo-9@gated-at.bofh.it>
2005-04-12 23:21 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-13  7:27   ` Christoph Hellwig
2005-04-12 21:46 Kilau, Scott
2005-04-12 22:28 ` Matt Mackall
2005-04-12 20:21 Kilau, Scott
2005-04-12 21:32 ` Matt Mackall
2005-04-12 21:42 ` Greg KH
2005-04-12 20:01 Kilau, Scott
2005-04-12 16:42 Kilau, Scott
2005-04-12 18:48 ` Jan-Benedict Glaw
2005-04-12 15:55 Kilau, Scott
2005-04-12 15:30 Kilau, Scott
2005-04-12 15:32 ` Christoph Hellwig
2005-04-13  3:27   ` Ricky Beam
2005-04-13  7:26     ` Christoph Hellwig
2005-04-12 16:16 ` Greg KH
2005-04-12 16:23 ` Jan-Benedict Glaw
2005-04-12 14:55 Kilau, Scott
2005-04-12 15:13 ` Christoph Hellwig
2005-04-12 14:02 Kilau, Scott
2005-04-12 14:44 ` Christoph Hellwig
2005-04-12 12:13 Ihalainen Nickolay
2005-04-12 14:44 ` Christoph Hellwig
2005-04-12 15:38   ` Ihalainen Nickolay

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=20050412173033.GC14857@kroah.com \
    --to=greg@kroah.com \
    --cc=Scott_Kilau@digi.com \
    --cc=admin@list.net.ru \
    --cc=hch@infradead.org \
    --cc=ihanic@dev.ehouse.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wendyx@us.ibm.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