Hi Chen, On Thu, Oct 27, 2011 at 11:18 AM, Ganir, Chen <chen.ganir@xxxxxx> wrote: >> As a general suggestion, I propose you first get the API changes >> "approved" and committed upstream, then proceed with code changes. >> Unless you are comfortable with doing lots of rounds of patch >> submissions (or you are planning only RFC to get early comments). >> > This is the purpose of this document. Early next week I'll send the modified API text with the changes made according to the comments, and get the approval. For now, my implementation is internal, and is mostly to support some other work I need to get done. Once you are happy with the amount of comments, you should send your changes in a format suitable for upstream submission (e.g. sent with git send-email, no sign-off line, "[PATCH BlueZ]" as prefix etc.) Thanks, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
