All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: fxload putting code at a wrong place
Date: Thu, 17 Jan 2002 14:48:40 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101127910708633@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101125719217654@msgid-missing>

Whoops!  Good catch.  I also added "-Wall" to CFLAGS in
the Makefile (one gets used to having compilers tell about
such bugs :) and fixed the other warnings (minor) too.  All
in CVS now.

Curious ... the firmware I tested with didn't misbehave
with that bug in place.  But this fixes a problem I was
scratching my head about yesterday ... thanks!

- Dave

----- Original Message ----- 
From: "Matthieu Lochegnies" <lochegm1@cti.ecp.fr>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Thursday, January 17, 2002 12:45 AM
Subject: fxload putting code at a wrong place


>   High !
> 
>   I just bought an Ez USB development kit and tried to play with it
> using fxload. The new merging algorithm seems to forget to initialize
> data_addr.
> 
>   Attached is a small patch that, I think, fixes it.
> 
>   Regards,
> 
> -- 
> Matthieu Lochegnies
> 


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      reply	other threads:[~2002-01-17 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17  8:45 fxload putting code at a wrong place Matthieu Lochegnies
2002-01-17 14:48 ` David Brownell [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=marc-linux-hotplug-101127910708633@msgid-missing \
    --to=david-b@pacbell.net \
    --cc=linux-hotplug@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.