On Wed, Feb 15, 2017 at 03:03:07PM +0100, H. Nikolaus Schaller wrote: > Hi Dmitry, > > > Am 12.02.2017 um 16:18 schrieb H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>: > > > > Hi Dmitry, > > > >> Am 28.01.2017 um 19:16 schrieb H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>: > >> > >> Hi Dmitry, > >> there have been no further comments/complaints about this patch series in the last month. > >> And it appears as if only your action is needed. > >> > >> What is missing for this patch series to be finally accepted? > > > > Did you find time to look into my comment on patch 1/9 and make a decision on patch 6/8? > > > > Is there anything open which prohibits inclusion to (and further testing within) linux/next? > > May I ask a question for my fundamental understanding of the Linux integration process. > Maybe, I have a wrong expectation which you can clarify. > > My question is how it does come that patches like > > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=449aa83e69ff10d77fe088eadacafe1e97937c14 > > appear within 2 days in linux-next, but our patch series had months of review (we are at v9) > and there have been no further comments from the community for weeks? Simpler patches are easy to apply, patches that have some contention tend to get unapplied longer, as they require more consideration. > > What is still missing what we can do or provide as information? I just replied to the other email from you. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
