public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: Jens Axboe <axboe@suse.de>, Greg KH <greg@kroah.com>,
	Daniel Robbins <drobbins@gentoo.org>,
	linux-kernel@vger.kernel.org, Mike@kordik.net,
	kpfleming@backtobasicsmgmt.com
Subject: Re: [PATCH] Re: 2.6.3-bk9 QA testing: firewire good, USB printing dead
Date: Tue, 02 Mar 2004 13:09:45 +0000	[thread overview]
Message-ID: <40448799.5030508@grupopie.com> (raw)
In-Reply-To: 20040301074348.GA7646@ip68-4-255-84.oc.oc.cox.net

Barry K. Nathan wrote:

>  
> +		/* We must increment writecount here, and not at the
> +		 * end of the loop. Otherwise, the final loop iteration may
> +		 * be skipped, leading to incomplete printer output.
> +		 */


You are correct.


I'm affraid this is my fault, for correcting a bug and letting another one take 
its place :(

It seems that this patch squashes them both. It should go in ASAP.

-- 
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"


  parent reply	other threads:[~2004-03-02 13:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28  2:01 2.6.3-bk9 QA testing: firewire good, USB printing dead Daniel Robbins
2004-02-28  2:10 ` Greg KH
2004-02-28  2:57   ` Daniel Robbins
2004-02-28  3:39     ` Kevin P. Fleming
2004-02-28  6:44     ` Greg KH
2004-02-28 21:22     ` Mike
2004-02-29  9:51   ` Jens Axboe
2004-03-01  7:43     ` [PATCH] " Barry K. Nathan
2004-03-01  8:02       ` Jens Axboe
2004-03-02  3:01       ` Mike
2004-03-02 13:09       ` Paulo Marques [this message]
2004-03-02 15:18         ` firewire good, USB printing fixed, CD-ROM block device IO errors near end of media Daniel Robbins
2004-03-02 19:26         ` [PATCH] Re: 2.6.3-bk9 QA testing: firewire good, USB printing dead Greg KH

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=40448799.5030508@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=Mike@kordik.net \
    --cc=axboe@suse.de \
    --cc=barryn@pobox.com \
    --cc=drobbins@gentoo.org \
    --cc=greg@kroah.com \
    --cc=kpfleming@backtobasicsmgmt.com \
    --cc=linux-kernel@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