Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 03 3月, 2010 2 次提交
  3. 02 3月, 2010 2 次提交
  5. 17 2月, 2010 1 次提交
    • T
      percpu: add __percpu sparse annotations to what's left · a29d8b8e
      由 Tejun Heo 提交于 
      Add __percpu sparse annotations to places which didn't make it in one
of the previous patches.  All converions are trivial.

These annotations are to make sparse consider percpu variables to be
in a different address space and warn if accessed without going
through percpu accessors.  This patch doesn't affect normal builds.
Signed-off-by: NTejun Heo <tj@kernel.org>
Acked-by: NBorislav Petkov <borislav.petkov@amd.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Huang Ying <ying.huang@intel.com>
Cc: Len Brown <lenb@kernel.org>
Cc: Neil Brown <neilb@suse.de>
      a29d8b8e
  7. 16 2月, 2010 19 次提交
  9. 05 2月, 2010 1 次提交
  11. 04 2月, 2010 1 次提交
  13. 17 1月, 2010 2 次提交
  15. 07 1月, 2010 1 次提交
  17. 23 12月, 2009 1 次提交
  19. 18 12月, 2009 1 次提交
  21. 23 11月, 2009 2 次提交
  23. 20 11月, 2009 1 次提交
    • D
      async_tx: build-time toggling of async_{syndrome,xor}_val dma support · 7b3cc2b1
      由 Dan Williams 提交于 
      ioat3.2 does not support asynchronous error notifications which makes
the driver experience latencies when non-zero pq validate results are
expected.  Provide a mechanism for turning off async_xor_val and
async_syndrome_val via Kconfig.  This approach is generally useful for
any driver that specifies ASYNC_TX_DISABLE_CHANNEL_SWITCH and would like
to force the async_tx api to fall back to the synchronous path for
certain operations.
Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      7b3cc2b1
  25. 19 11月, 2009 1 次提交
  27. 16 11月, 2009 1 次提交
    • H
      crypto: gcm - fix another complete call in complete fuction · 62c5593a
      由 Huang Ying 提交于 
      The flow of the complete function (xxx_done) in gcm.c is as follow:

void complete(struct crypto_async_request *areq, int err)
{
	struct aead_request *req = areq->data;

	if (!err) {
		err = async_next_step();
		if (err == -EINPROGRESS || err == -EBUSY)
			return;
	}

	complete_for_next_step(areq, err);
}

But *areq may be destroyed in async_next_step(), this makes
complete_for_next_step() can not work properly. To fix this, one of
following methods is used for each complete function.

- Add a __complete() for each complete(), which accept struct
  aead_request *req instead of areq, so avoid using areq after it is
  destroyed.

- Expand complete_for_next_step().

The fixing method is based on the idea of Herbert Xu.
Signed-off-by: NHuang Ying <ying.huang@intel.com>
Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      62c5593a
  29. 12 11月, 2009 1 次提交
  31. 27 10月, 2009 3 次提交
反馈
建议 客服 返回
顶部