archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <>
To: Philip Stephens <>
	linux-modules <>
Subject: Re: question - where to file bug report for modprobe
Date: Wed, 25 Mar 2020 10:03:05 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

It's on kmod's mailing list linux-modules
<>, already CC'ed here.

Lucas De Marchi

On Wed, Mar 25, 2020 at 8:54 AM Philip Stephens <> wrote:
> Hi!
> I've run into an issue I think is a bug, and I'm having a problem targeting the correct group. As you all were listed in the modprobe manpage, I thought I'd give you a try.
> That's the bug (possibly), can you tell me which project to file it with?
> Thanks,
> Philip

Lucas De Marchi

           reply	other threads:[~2020-03-25 17:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).