public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Francois Romieu <romieu@cogenit.fr>,
	linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: [PATCH] HDLC patch for 2.5.5 (0/3)
Date: Thu, 21 Feb 2002 19:57:29 -0500	[thread overview]
Message-ID: <3C759779.8FA1EF3C@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202191732320.1443-100000@penguin.transmeta.com> <3C739351.20C03FDA@mandrakesoft.com> <m3u1sav1e0.fsf@defiant.pm.waw.pl>

Krzysztof Halasa wrote:
> 
> Jeff Garzik <jgarzik@mandrakesoft.com> writes:
> 
> > Sure.
> >
> > FWIW it looks like Krzysztof Halasa has some good points, so a "[BK
> > PATCH]" may be delayed a day or two before coming to you, I'm betting...
> 
> Anyway, I can't even touch it until March, 23. I think it's now best
> to apply the patches from Francois on top of my original patch.
> We could eventually make some small correction(s) if I really still
> have good points there, when I'm back in Poland.

Sounds good to me too.

Thanks,

	Jeff



-- 
Jeff Garzik      | "UNIX enhancements aren't."
Building 1024    |           -- says /usr/games/fortune
MandrakeSoft     |

  reply	other threads:[~2002-02-22  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-17 18:30 [PATCH] HDLC patch for 2.5.5 (0/3) Francois Romieu
2002-02-17 23:22 ` Jeff Garzik
2002-02-20  1:32   ` Linus Torvalds
2002-02-20 12:15     ` Jeff Garzik
2002-02-21 23:52       ` Krzysztof Halasa
2002-02-22  0:57         ` Jeff Garzik [this message]
2002-02-18 12:09 ` Krzysztof Halasa
2002-02-18 13:34   ` Francois Romieu
2002-02-19 11:02     ` Krzysztof Halasa
2002-02-20 13:39       ` Francois Romieu
2002-02-20 13:51         ` Jeff Garzik
2002-02-20 23:15           ` [PATCH] HDLC patch for 2.5.5 (updated) Francois Romieu

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=3C759779.8FA1EF3C@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=davem@redhat.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@cogenit.fr \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox