From: Grant Grundler <grundler@parisc-linux.org>
To: rubisher <rubisher@scarlet.be>
Cc: linux-parisc@vger.kernel.org
Subject: Re: dma_addr_t: which comment is correct?
Date: Mon, 24 Dec 2007 01:51:59 -0700 [thread overview]
Message-ID: <20071224085159.GC15161@colo.lackof.org> (raw)
In-Reply-To: <476EE63A.9080807@scarlet.be>
On Sun, Dec 23, 2007 at 10:50:34PM +0000, rubisher wrote:
...
> btw do you notice how much way are there (in so few lines) to use a
> unsigned 32bits integer: u32, __u32 but also uint32_t, u_int32_t, ...
>
> Is there some advise om the best pratice?
IIRC, Preferred is "u32". But use whatever is consistent with the
file you are editing.
>
> Ah also related to ccio-dma patch test on my c110, it seems that removing
> DELAYED_RESOURCE_CNT code help a bit this system with few ram (64Mb only)
> to survive a bit longer (enough to debootstrap and download 800Mb to be
> installed) but that didn't make the drill: there are still fs corruption
> from time to time and some reset on the lasi disk ;-(.
> This test just seems to confirm an issue of i/o coherency somewhere but
> where those rules could be broken???
ISTR Joel Soete reporting problems for CCIO machines as well.
Offhand, I don't know what's wrong and we depend on Ryan Bradetich
and other volunteers to track that down.
cheers,
grant
>
> Merry Xmas,
> r.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-12-24 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 12:15 dma_addr_t: which comment is correct? rubisher
2007-12-23 9:39 ` Grant Grundler
2007-12-23 22:50 ` rubisher
2007-12-24 8:51 ` Grant Grundler [this message]
2007-12-26 10:01 ` Thibaut VARENE
2007-12-26 17:31 ` iommu_fill_pdir() and its /* Horrible hack. ... */ reading rubisher
2007-12-28 8:27 ` Grant Grundler
2007-12-28 15:27 ` rubisher
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=20071224085159.GC15161@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rubisher@scarlet.be \
/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.