diff options
author | Michael Witten <mfwitten@gmail.com> | 2011-08-25 15:42:20 -0400 |
---|---|---|
committer | Michael Witten <mfwitten@gmail.com> | 2011-08-29 16:00:01 -0400 |
commit | 9029bd7a42e3c32783866630ee3eb6b82e273544 (patch) | |
tree | c01d9d79845140b39cb15153c065f19682fd6690 /Documentation | |
parent | 54f2cb8fc930e08fd6156519b28c45d576615f82 (diff) |
DocBook/drm: The word `so-called'; I do not think it connotes what you think it connotes
From Webster's Revised Unabridged Dictionary (1913) [web1913]:
So-called \So"-called`\, a.
So named; called by such a name (but perhaps called thus with
doubtful propriety).
From WordNet (r) 2.0 [wn]:
so-called
adj : doubtful or suspect; "these so-called experts are no help"
[syn: {alleged(a)}, {supposed}]
My strong conviction is that widespread use of 'so gennant'
or 'sogennant' in German has led to the creeping misuse of
'so-called' in English (especially through technical writings).
In English, it would be better to use:
what is called
or a better translation of 'so gennant':
so named
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/DocBook/drm.tmpl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl index 3470c6b2f843..66a114a05c6f 100644 --- a/Documentation/DocBook/drm.tmpl +++ b/Documentation/DocBook/drm.tmpl | |||
@@ -455,7 +455,7 @@ | |||
455 | a GTT DRM MM object, which provides an address space pool for | 455 | a GTT DRM MM object, which provides an address space pool for |
456 | object allocation. In a KMS configuration, the driver | 456 | object allocation. In a KMS configuration, the driver |
457 | needs to allocate and initialize a command ring buffer following | 457 | needs to allocate and initialize a command ring buffer following |
458 | core GEM initialization. A UMA device usually has a so-called | 458 | core GEM initialization. A UMA device usually has what is called a |
459 | "stolen" memory region, which provides space for the initial | 459 | "stolen" memory region, which provides space for the initial |
460 | framebuffer and large, contiguous memory regions required by the | 460 | framebuffer and large, contiguous memory regions required by the |
461 | device. This space is not typically managed by GEM, and must | 461 | device. This space is not typically managed by GEM, and must |