On Wed, Oct 3, 2012 at 7:46 AM, Daniel Santos <danielfsantos@xxxxxxx> wrote: > On 10/03/2012 09:01 AM, Steven Rostedt wrote: >> You don't need to use get_maintainers. It's more of a help tool to find >> maintainers and not something that is mandatory. Not everyone that has >> ever touched one of these files needs to be Cc'd. >> >> Please move the patch to the patch series where it is used. Otherwise it >> confuses reviewers as it did here. > Ok then, but this would also apply to the addition of these macros as well: > BUILD_BUG_ON_NON_CONST > BUILD_BUG42 > BUILD_BUG_ON_NON_CONST42 > > Should these then also be moved? Yes, this would actually make things easier. > Should I only CC those who have responded to these patches and whomever > is in the MAINTAINERS file then? There is no strong rule here, but generally get_maintainers returns too many people. You want to trim down the list to something shorter; a dozen people is the most I would consider (but for most patches a half-dozen is already plenty). -- Michel "Walken" Lespinasse A program is never fully debugged until the last user dies. -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
