public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Luca Barbieri <ldb@ldb.ods.org>
Cc: Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [2.4] ATM driver for the Alcatel SpeedTouch USB DSL modem
Date: Thu, 30 May 2002 12:59:42 -0700	[thread overview]
Message-ID: <20020530195942.GA29522@kroah.com> (raw)
In-Reply-To: <1022782402.1920.130.camel@ldb> <20020530184817.GB28893@kroah.com> <1022787238.1921.185.camel@ldb>

On Thu, May 30, 2002 at 09:33:58PM +0200, Luca Barbieri wrote:
> > Because of these dependencies (and the fact that the maintainer doesn't
> > want it added yet) I will not apply this patch.
> That's ok (right now). Application of it should only be considered after
> discussion here and after the maintainer responds.
> 
> > Sending this to linux-usb-devel might be a better place, instead of
> > bothering linux-kernel.
> Should I have sent the first two patches to linux-kernel, the ATM SAR to
> linux-atm-general and the SpeedTouch driver to linux-usb-devel?
> How should I have handled the fact that the SpeedTouch and ATM SAR
> patches depend on main kernel patches and the fact that the SpeedTouch
> patch includes ATM code (since it is for an ATM device attached to the
> USB bus)?

Well, if you want a ATM patch added, you need to send it to the ATM
maintainer (but I don't know if there is one right now or not.)  And if
you want a USB driver added to the USB tree, you need to send it to the
USB maintainer.  So cross-posting to all of these lists is probably a
good idea :)

greg k-h

      reply	other threads:[~2002-05-30 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30 18:13 [PATCH] [2.4] ATM driver for the Alcatel SpeedTouch USB DSL modem Luca Barbieri
2002-05-30 18:48 ` Greg KH
2002-05-30 19:33   ` Luca Barbieri
2002-05-30 19:59     ` 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=20020530195942.GA29522@kroah.com \
    --to=greg@kroah.com \
    --cc=ldb@ldb.ods.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox