Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Geoffrey Espin <espin@idiom.com>
To: Pete Popov <ppopov@mvista.com>
Cc: James Simmons <jsimmons@transvirtual.com>,
	"Gleb O. Raiko" <raiko@niisi.msk.ru>,
	linux-mips <linux-mips@oss.sgi.com>
Subject: Re: kmalloc/pci_alloc and skbuff's
Date: Wed, 19 Dec 2001 11:53:18 -0800	[thread overview]
Message-ID: <20011219115318.A12344@idiom.com> (raw)
In-Reply-To: <1008789145.31066.140.camel@zeus>; from Pete Popov on Wed, Dec 19, 2001 at 11:12:25AM -0800


> > Currently, my private pci_alloc/free_consistent() routines manage

> FYI, this is not an isolated issue. We deal with a number of
> architectures and we've seen this problem with other arches and system
> controllers as well. A 'generic' solution would be nice and probably
> necessary at some point. 2.5 would be a good place to do it, if only
> someone would volunteer ;-)   [Pete]

Thanks for the reassurance.

Can one include one's own arch/mips/korva/skbuff.c?
But with network.o being a monolithic blob .o instead of a .a,
seems like patching the one file is not feasible.
I tried tweaking $(HEAD) but then stumbled onto this.

How does one package such a work-around?  Include a patch file in
the LSP, which gets automatically run to munge on kernel sources?

Or will linux-mips.sf.net accept a patch for net/core/skbuff.c?

Geoff
-- 
Geoffrey Espin espin@idiom.com

  reply	other threads:[~2001-12-19 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 20:38 kmalloc/pci_alloc and skbuff's Geoffrey Espin
2001-12-19  9:05 ` Gleb O. Raiko
2001-12-19 17:09   ` James Simmons
2001-12-19 18:56     ` Geoffrey Espin
2001-12-19 19:12       ` Pete Popov
2001-12-19 19:53         ` Geoffrey Espin [this message]
2001-12-19 21:23           ` Pete Popov
2001-12-19 21:56             ` Geoffrey Espin
2001-12-19 22:06               ` Pete Popov

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=20011219115318.A12344@idiom.com \
    --to=espin@idiom.com \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ppopov@mvista.com \
    --cc=raiko@niisi.msk.ru \
    /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