All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: baruch@tkos.co.il, netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Orphan usb/net/hso driver
Date: Tue, 28 Feb 2017 18:51:24 +0100	[thread overview]
Message-ID: <20170228175124.GA14016@kroah.com> (raw)
In-Reply-To: <20170228.103844.1220680109576438605.davem@davemloft.net>

On Tue, Feb 28, 2017 at 10:38:44AM -0500, David Miller wrote:
> From: Baruch Siach <baruch@tkos.co.il>
> Date: Tue, 28 Feb 2017 10:39:48 +0200
> 
> > The email address of Jan Dumon bounces, and there is not relevant information
> > in the linked website.
> > 
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> 
> This patch is fine and I will apply it later, however I will make a
> general statement that we list USB networking drivers very
> inconsistently.
> 
> Specifically, some list linux-usb as the mailing list, others list
> netdev.  We should figure out which one (or both) is the best to
> specify, and apply that rule consitently to the MAINTAINERS file.

I don't want them :)

Seriously, I don't have a problem with the patches being cc:ed to
linux-usb as long as you will take them, as often times the issues
involved are USB specific things, not network driver-specific things, so
the developers here can weigh in on them.

Want me to make up a patch to do that?

thanks,

greg k-h

  reply	other threads:[~2017-02-28 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  8:39 [PATCH] MAINTAINERS: Orphan usb/net/hso driver Baruch Siach
2017-02-28 15:38 ` David Miller
2017-02-28 17:51   ` Greg KH [this message]
     [not found] ` <30ad43134a6a7d155a257abaa31d120cf2c4d74c.1488271188.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2017-03-01 17:52   ` David Miller

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=20170228175124.GA14016@kroah.com \
    --to=greg@kroah.com \
    --cc=baruch@tkos.co.il \
    --cc=davem@davemloft.net \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@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.