| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In commit a144c6a6c924 ("PM: Print a warning if firmware is requested
when tasks are frozen") we not only printed a warning if somebody tried
to load the firmware when tasks are frozen - we also failed the load.
But that check was done before the check for built-in firmware, and then
when we disallowed usermode helpers during bootup (commit 288d5abec831:
"Boot up with usermodehelper disabled"), that actually means that
built-in modules can no longer load their firmware even if the firmware
is built in too. Which used to work, and some people depended on it for
the R100 driver.
So move the test for usermodehelper_is_disabled() down, to after
checking the built-in firmware.
This should fix:
https://bugzilla.kernel.org/show_bug.cgi?id=40952
Reported-by: James Cloos <cloos@hjcloos.com>
Bisected-by: Elimar Riesebieter <riesebie@lxtec.de>
Cc: Michel Dänzer <michel@daenzer.net>
Cc: Rafael Wysocki <rjw@sisk.pl>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|
|\
| |
| |
| |
| |
| |
| | |
* 'for-31-rc3/i2c-fixes' of git://git.fluff.org/bjdooks/linux:
i2c-nomadik: fix kerneldoc warning
Revert "i2c-omap: fix static suspend vs. runtime suspend"
i2c-nomadik: Do not use _interruptible_ variant call
|
| |
| |
| |
| |
| |
| |
| |
| | |
There was a missing struct item in the kerneldoc, add it and fix
another pretty-printing formatting issue with a missing space.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit adf6e07922255937c8bfeea777d19502b4c9a2be.
Remove system PM methods which can race with runtime PM methods.
Also, as of v3.1, the PM domain level code for OMAP handles device
power state transistions automatically for devices, so drivers no
longer need to specifically call the bus/pm_domain methods themselves.
Signed-off-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If there is a signal pending and wait_for_completion_interruptible_timeout
exited because of the -ERESTARTSYS error we are unable to send any more
i2c messages.
So, deprecate this _interruptible_ variant call.
Signed-off-by: Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
|