From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joseph Lutz <joseph.lutz@novatechautomation.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: drivers/usb/class/usbtmc.c
Date: Wed, 29 Mar 2023 06:59:36 +0200 [thread overview]
Message-ID: <ZCPFuJnQ6BbF4n6o@kroah.com> (raw)
In-Reply-To: <DS7PR07MB775169F24942174F54B4246494889@DS7PR07MB7751.namprd07.prod.outlook.com>
On Tue, Mar 28, 2023 at 06:23:31PM +0000, Joseph Lutz wrote:
> I am having some issues with the kernel driver "drivers/usb/class/usbtmc.c". I am trying to figure out who I can contact that would have information about how this driver is working.
Hi,
First off, please do not send html email, the mailing lists reject it
(as you found out), and it will not get to anyone.
> The script ./scripts/get_maintainer.pl drivers/usb/class/usbtmc.c gives me the following addresses which is why I am writing to you.
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:USB SUBSYSTEM)
> linux-usb@vger.kernel.org (open list:USB SUBSYSTEM)
> linux-kernel@vger.kernel.org (open list)
>
> I am not certain whether I should be communicating with these email addresses or if I should be communicating with the individuals on the github sight. https://github.com/dpenkler/linux-usbtmc
If you look at the git history for the driver in the kernel, you will
see Dave Penkler <dpenkler@gmail.com> as a probably good contact.
So try resending your message, with the information you had before about
the problem you are seeing, to the lists and to Dave and in non-html
format and we can go from there.
thanks,
greg k-h
parent reply other threads:[~2023-03-29 4:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DS7PR07MB775169F24942174F54B4246494889@DS7PR07MB7751.namprd07.prod.outlook.com>]
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=ZCPFuJnQ6BbF4n6o@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=joseph.lutz@novatechautomation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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