From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: Marin Mitov <mitov@issp.bas.bg>
Subject: [PATCH 3/8] docs: use DMA_BIT_MASK
Date: Wed, 04 Nov 2009 16:04:52 -0800 [thread overview]
Message-ID: <12573794921038@xenotime.net> (raw)
In-Reply-To: <1257379492822@xenotime.net>
From: Marin Mitov <mitov@issp.bas.bg>
Subject: use DMA_BIT_MASK instead of inline constant
Use DMA_BIT_MASK(24) instead of 0x00ffffff in DMA-mapping.txt
Signed-off-by: Marin Mitov <mitov@issp.bas.bg>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/DMA-mapping.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- lnx-2632-rc6.orig/Documentation/DMA-mapping.txt
+++ lnx-2632-rc6/Documentation/DMA-mapping.txt
@@ -214,7 +214,7 @@ most specific mask.
Here is pseudo-code showing how this might be done:
#define PLAYBACK_ADDRESS_BITS DMA_BIT_MASK(32)
- #define RECORD_ADDRESS_BITS 0x00ffffff
+ #define RECORD_ADDRESS_BITS DMA_BIT_MASK(24)
struct my_sound_card *card;
struct pci_dev *pdev;
--
next prev parent reply other threads:[~2009-11-05 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 0:04 [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 7/8] docs: serial/tty, add to ldisc methods Randy Dunlap
2009-11-05 0:16 ` Alan Cox
2009-11-05 0:04 ` [PATCH 6/8] docs: explain procs_running better Randy Dunlap
2009-11-05 0:04 ` Randy Dunlap [this message]
2009-11-05 0:04 ` [PATCH 4/8] docbook: signal_pending has an argument Randy Dunlap
2009-11-05 0:04 ` [PATCH 2/8] docs: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-11-05 0:04 ` [PATCH 8/8] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-11-05 8:10 ` [PATCH 1/8] sound: use KERN_WARNING, not KERN_WARN Takashi Iwai
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=12573794921038@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mitov@issp.bas.bg \
/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