public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new kernel patch (relative to 2.5.8-pre3)
Date: Fri, 12 Apr 2002 05:31:04 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905439@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905293@msgid-missing>

>>>>> On Thu, 11 Apr 2002 20:50:35 -0700, Greg KH <greg@kroah.com> said:

  Greg> There is a uhci.c (sorry, meant to say this, instead of
  Greg> usb-uhci.c) change in the patch you just posted on kernel.org.
  Greg> Your diffstat says there is also a change to usb-ohci.c, but
  Greg> that doesn't show up in your patch.

This is really bugging you, eh? ;-)

  Greg> And it looks like the ia64.bkbits.net/to-linus-2.5 doesn't
  Greg> contain all of the changes you have listed in the patch you
  Greg> just posted, right?

Like I said: it's simply what the script produced.

  Greg> Is there a bk tree somewhere I can clone that matches up with
  Greg> your working tree right now?  I'd like to get that usb patch
  Greg> out of there :)

No, the lia64 patch is a union of about a dozen bk trees.  I'm
chipping away one tree after another, as Linus merges stuff, until at
the end only to-linus-2.5 is left.  I did make the union tree
available in the past, but it was a pain to maintain (it's a throwaway
tree and bkbits.net isn't well setup to handle that, as far as I can
tell).

Anyhow, I modified the tree containing the temporary hacks to omit the
uhci.c change.  I'm not sure whether the comment will be gone (I
suspect not, given bk's tendency never to forget anything), but the
patch should be correct.

	--david


  parent reply	other threads:[~2002-04-12  5:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  5:02 [Linux-ia64] new kernel patch (relative to 2.5.7-pre1) David Mosberger
2002-04-10 21:42 ` [Linux-ia64] new kernel patch (relative to 2.4.18) David Mosberger
2002-04-10 22:23 ` Stephane Eranian
2002-04-11 18:22 ` Chris McDermott
2002-04-11 20:04 ` Saxena, Sunil
2002-04-11 23:49 ` [Linux-ia64] new kernel patch (relative to 2.5.8-pre3) David Mosberger
2002-04-12  0:46 ` Greg KH
2002-04-12  0:49 ` David Mosberger
2002-04-12  1:01 ` Jes Sorensen
2002-04-12  1:04 ` Greg KH
2002-04-12  2:15 ` David Mosberger
2002-04-12  3:50 ` Greg KH
2002-04-12  4:43 ` Greg KH
2002-04-12  5:31 ` David Mosberger [this message]
2002-04-22  7:02 ` [Linux-ia64] new kernel patch (relative to 2.4.18) Zach, Yoav
2002-04-22 14:47 ` n0ano
2002-04-22 14:57 ` Andreas Schwab
2002-04-22 15:34 ` David Mosberger
2002-04-22 15:40 ` n0ano
2002-05-02 17:41 ` Steffen Persvold
2002-05-03  7:35 ` Ross Elliott
2002-05-03 17:23 ` David Mosberger
2002-05-03 23:36 ` Steffen Persvold
2002-05-08 17:49 ` David Mosberger
2002-05-08 18:25 ` Luck, Tony
2002-05-08 19:21 ` David Mosberger
2002-05-08 19:43 ` Jack Steiner
2002-05-08 20:29 ` David Mosberger
2002-05-08 23:26 ` Luck, Tony

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-ia64-105590701905439@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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