Re: [PATCH 2/4] list.h: add list_cut_position()

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Luis R. Rodriguez <lrodriguez@...>
Cc: Randy Dunlap <randy.dunlap@...>, Luis Rodriguez <Luis.Rodriguez@...>, linville@tuxdriver.com <linville@...>, netdev@vger.kernel.org <netdev@...>, linux-kernel@vger.kernel.org <linux-kernel@...>, torvalds@linux-foundation.org <torvalds@...>, linux-wireless@vger.kernel.org <linux-wireless@...>, ath9k-devel@venema.h4ckr.net <ath9k-devel@...>
Date: Tuesday, August 5, 2008 - 4:52 am

Hi,

2008/8/5 Luis R. Rodriguez <lrodriguez@atheros.com>:

Isn't this just an over-complicated way of writing "new_first = entry->next"?


I think it would be helpful if the comment explained what the function
actually does, i.e. that it moves the inital part of 'head' (up to and
including 'entry' from 'head' to 'list'.


No other list function in "list.h" has BUG_ONs.  Why this one?


If there was data in 'list' before the call, it will be lost now.  Is
this intended behaviour?


I hope this helps,
Jochen
-- 
http://seehuhn.de/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 2/4] list.h: add list_cut_position(), Luis R. Rodriguez, (Mon Aug 4, 6:48 pm)
Re: [PATCH 2/4] list.h: add list_cut_position(), Randy Dunlap, (Mon Aug 4, 7:00 pm)
Re: [PATCH 2/4] list.h: add list_cut_position(), Luis R. Rodriguez, (Mon Aug 4, 7:13 pm)
Re: [PATCH 2/4] list.h: add list_cut_position(), Jochen Voß, (Tue Aug 5, 4:52 am)
Re: [PATCH 2/4] list.h: add list_cut_position(), Luis R. Rodriguez, (Wed Aug 6, 2:27 pm)
Re: [PATCH 2/4] list.h: add list_cut_position(), Randy Dunlap, (Wed Aug 6, 2:35 pm)