From: Jeff Garzik <jeff@garzik.org>
To: Petko Manolov <petkan@nucleusys.com>
Cc: netdev@vger.kernel.org
Subject: Re: [patch] pegasus.c
Date: Mon, 11 Feb 2008 10:38:28 -0500 [thread overview]
Message-ID: <47B06BF4.7010009@garzik.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0801091222560.3171@bender.nucleusys.com>
Petko Manolov wrote:
> Hi Jeff,
>
> Attached you'll find a patch that is fixing a driver bug triggered when
> malformed string is passed to the 'devid' module parameter. The
> expected format is:
>
> "device_name:vendor_id:device_id:flags"
>
> but it turned out people often type:
>
> "somename::0"
>
> instead of:
>
> "somename:::0"
ACK but two process problems preventing application:
* patch is base64-encoded
* no signed-off-by included
next prev parent reply other threads:[~2008-02-11 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 10:30 [patch] pegasus.c Petko Manolov
2008-02-11 15:38 ` Jeff Garzik [this message]
2008-02-19 8:11 ` Petko Manolov
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=47B06BF4.7010009@garzik.org \
--to=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.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 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.