Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 31 3月, 2011 1 次提交
  3. 30 3月, 2011 1 次提交
  5. 24 3月, 2011 3 次提交
  7. 17 3月, 2011 1 次提交
  9. 11 3月, 2011 1 次提交
  11. 08 3月, 2011 2 次提交
  13. 07 3月, 2011 1 次提交
  15. 02 3月, 2011 2 次提交
  17. 01 3月, 2011 2 次提交
  19. 28 2月, 2011 2 次提交
  21. 26 2月, 2011 1 次提交
  23. 24 2月, 2011 1 次提交
  25. 23 2月, 2011 6 次提交
  27. 22 2月, 2011 1 次提交
  29. 21 2月, 2011 2 次提交
    • J
      random: update interface comments to reflect reality · 442a4fff
      由 Jarod Wilson 提交于 
      At present, the comment header in random.c makes no mention of
add_disk_randomness, and instead, suggests that disk activity adds to the
random pool by way of add_interrupt_randomness, which appears to not have
been the case since sometime prior to the existence of git, and even prior
to bitkeeper. Didn't look any further back. At least, as far as I can
tell, there are no storage drivers setting IRQF_SAMPLE_RANDOM, which is a
requirement for add_interrupt_randomness to trigger, so the only way for a
disk to contribute entropy is by way of add_disk_randomness. Update
comments accordingly, complete with special mention about solid state
drives being a crappy source of entropy (see e2e1a148 for reference).
Signed-off-by: NJarod Wilson <jarod@redhat.com>
Acked-by: NMatt Mackall <mpm@selenic.com>
Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      442a4fff
    • L
      Revert "tpm_tis: Use timeouts returned from TPM" · e5871372
      由 Linus Torvalds 提交于 
      This reverts commit 9b29050f.

It has caused hibernate regressions, for example Juri Sladby's report:

  "I'm unable to hibernate 2.6.37.1 unless I rmmod tpm_tis:
   [10974.074587] Suspending console(s) (use no_console_suspend to debug)
   [10974.103073] tpm_tis 00:0c: Operation Timed out
   [10974.103089] legacy_suspend(): pnp_bus_suspend+0x0/0xa0 returns -62
   [10974.103095] PM: Device 00:0c failed to freeze: error -62"

and Rafael points out that some of the new conditionals in that commit
seem to make no sense.  This commit needs more work and testing, let's
revert it for now.
Reported-by: NNorbert Preining <preining@logic.at>
Reported-and-requested-by: NJiri Slaby <jirislaby@gmail.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: Guillaume Chazarain <guichaz@gmail.com>
Cc: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Acked-by: NRafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e5871372
  31. 19 2月, 2011 2 次提交
    • A
      cm4000_cs: Fix undefined ops warning · 644e6e4a
      由 Alan Cox 提交于 
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      644e6e4a
    • J
      drivers/char/pcmcia/ipwireless/main.c: Convert release_resource to... · d5bb2923
      由 Julia Lawall 提交于 
      drivers/char/pcmcia/ipwireless/main.c: Convert release_resource to release_region/release_mem_region

Request_region should be used with release_region, not release_resource.

This patch contains a number of changes, related to calls to request_region,
request_mem_region, and the associated error handling code.

1. For the call to request_region, the variable io_resource storing the
result is dropped.  The call to release_resource at the end of the function
is changed to a call to release_region with the first two arguments of
request_region as its arguments.  The same call to release_region is also
added to release_ipwireless.

2. The first call to request_mem_region is now tested and ret is set to
-EBUSY if the the call has failed.  This call was associated with the
initialization of ipw->attr_memory.  But the error handling code was
testing ipw->common_memory.  The definition of release_ipwireless also
suggests that this call should be associated with ipw->common_memory, not
ipw->attr_memory.

3. The second call to request_mem_region is now tested and ret is
set to -EBUSY if the the call has failed.

4. The various gotos to the error handling code is adjusted so that there
is no need for ifs.

5. Return the value stored in the ret variable rather than -1.

The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)

// <smpl>
@@
expression x,E;
@@
(
*x = request_region(...)
|
*x = request_mem_region(...)
)
... when != release_region(x)
    when != x = E
* release_resource(x);
// </smpl>
Signed-off-by: NJulia Lawall <julia@diku.dk>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      d5bb2923
  33. 18 2月, 2011 4 次提交
  35. 16 2月, 2011 2 次提交
  37. 11 2月, 2011 2 次提交
  39. 04 2月, 2011 3 次提交