From: "David S. Miller" <davem@redhat.com>
To: perex@suse.cz
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA update [10/10] - 2002/08/05
Date: Mon, 30 Sep 2002 14:41:44 -0700 (PDT) [thread overview]
Message-ID: <20020930.144144.25095563.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0209302327500.503-100000@pnote.perex-int.cz>
From: Jaroslav Kysela <perex@suse.cz>
Date: Mon, 30 Sep 2002 23:29:30 +0200 (CEST)
On Mon, 30 Sep 2002, David S. Miller wrote:
> I sent this stuff to Linus seperately last night to save time.
I need to redo next 7 patches because your update :-(
My fault, I should be faster.
Sorry for the conflict, but I have been waiting for almost 2 months
for my SBUS diffs to show up in the tree so I could merge in my
Sparc drivers.
next prev parent reply other threads:[~2002-09-30 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 19:02 [PATCH] ALSA update [10/10] - 2002/08/05 Jaroslav Kysela
2002-09-30 0:56 ` David S. Miller
2002-09-30 16:20 ` Jaroslav Kysela
2002-09-30 20:52 ` David S. Miller
2002-09-30 21:29 ` Jaroslav Kysela
2002-09-30 21:41 ` David S. Miller [this message]
2002-10-01 23:22 ` Linus Torvalds
2002-10-01 23:18 ` David S. Miller
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=20020930.144144.25095563.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--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 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.