On 7/2/2013 9:44 AM, Gupta, Pekon wrote:
This does not apply to l2-mtd.git, could you please re-base?
[Pekon]: rebased to l2-mtd.git
- updated [Patch 3/4] which conflicted with commit '26331c04' which
touched omap2.c.
- Please ignore [Patch 4/4] as it’s a DT update, which adds on top of Benoit's
tree (which has NAND node commits too).
If you need one patch (DT patch) in the series to be merged in another
repository (DT maintainer tree) then separate out that patch as separate
series and mention the dependency or need ack from the driver maintainer
so that both maintainer can apply the whole series into his repository
instead of applying partially here and there.
Agree. Yes, I should have sent the DT patch separately.
But I posted all changes as part of single series, as its easy for users to
Test and Ack them.
Similarly patches for GPMC (Tony's tree) and NAND (Artem's tree) are
functionally coupled, So at times I have to send them as part of same series.
However, I'll clearly mention that in my cover-letter for future patches.
Thanks for feedback ..
In that case you can publish your testing branch to a public repo and point to
that repo in your cover letter so that someone who wants to test can test
from your repo which has all dependent patches.
Regards
Mugunthan V N
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
