1. 12 6月, 2015 1 次提交
  2. 06 6月, 2015 5 次提交
  3. 04 6月, 2015 1 次提交
  4. 02 6月, 2015 2 次提交
  5. 28 5月, 2015 2 次提交
  6. 25 5月, 2015 1 次提交
  7. 22 5月, 2015 1 次提交
  8. 13 5月, 2015 1 次提交
  9. 10 5月, 2015 1 次提交
  10. 06 5月, 2015 2 次提交
  11. 17 4月, 2015 1 次提交
    • M
      cxgb4: drop __GFP_NOFAIL allocation · f72f116a
      Michal Hocko 提交于
      set_filter_wr is requesting __GFP_NOFAIL allocation although it can return
      ENOMEM without any problems obviously (t4_l2t_set_switching does that
      already).  So the non-failing requirement is too strong without any
      obvious reason.  Drop __GFP_NOFAIL and reorganize the code to have the
      failure paths easier.
      
      The same applies to _c4iw_write_mem_dma_aligned which uses __GFP_NOFAIL
      and then checks the return value and returns -ENOMEM on failure.  This
      doesn't make any sense what so ever.  Either the allocation cannot fail or
      it can.
      
      del_filter_wr seems to be safe as well because the filter entry is not
      marked as pending and the return value is propagated up the stack up to
      c4iw_destroy_listen.
      Signed-off-by: NMichal Hocko <mhocko@suse.cz>
      Cc: David Rientjes <rientjes@google.com>
      Cc: Johannes Weiner <hannes@cmpxchg.org>
      Cc: Dave Chinner <david@fromorbit.com>
      Cc: "Theodore Ts'o" <tytso@mit.edu>
      Cc: Mel Gorman <mgorman@suse.de>
      Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Hariprasad S <hariprasad@chelsio.com>
      Cc: Jan Kara <jack@suse.cz>
      Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f72f116a
  12. 15 4月, 2015 1 次提交
  13. 08 4月, 2015 1 次提交
  14. 02 4月, 2015 1 次提交
  15. 30 3月, 2015 2 次提交
  16. 25 3月, 2015 1 次提交
  17. 20 3月, 2015 1 次提交
  18. 09 3月, 2015 1 次提交
  19. 06 3月, 2015 2 次提交
  20. 10 2月, 2015 1 次提交
  21. 05 2月, 2015 2 次提交
  22. 28 1月, 2015 1 次提交
  23. 27 1月, 2015 2 次提交
  24. 16 1月, 2015 1 次提交
  25. 14 1月, 2015 1 次提交
  26. 13 1月, 2015 2 次提交
  27. 09 1月, 2015 1 次提交
  28. 06 1月, 2015 1 次提交