Gadiyar, Anand wrote: > Tony Lindgren wrote: > > Hi all, > > > > I'm finally done sorting through the patchwork patches to add to > > the omap for-next queue. So I've nuked my linux-omap inbox, and > > cleared the patches that I'm supposed to deal with in patchwork. > > > > Please check that you patch is applied (or merged into some existing > > patch) in the omap for-next branch. > > > > If you don't see your patch in the omap for-next branch, and you > > don't see the patch in the patchwork list, please repost your > > patch. When reposting, please send the whole series again. > > > > The patchwork pending patches are at: > > > > http://patchwork.kernel.org/project/linux-omap/list/ > > > > I have not touched the patches in patchwork that are tagged for > > felipebalbi, khilman or pwsan, so this message only concerns the > > ones I'm supposed to deal with. > > > > If you have lots of patches, you can also post a git branch that's > > rebased on commit 8171d88089ad63fc442b2bf32af7c18653adc5cb. > > Don't use the omap for-next for rebasing, as it's still changing. > > > > I've dropped all the patches that did not apply to for-next, > > or that have dependency to some other subsystem. I've commented > > on few of the patches that don't apply, but not all of them. > > Then some fix patches I've merged to the earlier patches, > > and for those there's no APPLIED email message. > > > > I've probably also accidentally trashed some perfectly valid > > patches too.. So please check and repost as needed! > > > > Tony, > > What happened to the 3630 support stuff that had been merged to > your master branch as of yesterday? > > - Anand
I meant, I see these patches in for-next, but they're not present in the l-o master branch. Is this deliberate? - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
