linux-kernel - Re: [PATCH v9 0/8] drivers: touchscreen: tsc2007 and ads7846/tsc2046 improvements (use common touchscreen bindings, pre-calibration, spi fix and provide iio raw values)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170217204351.GF13050@dtor-ws>
Date:   Fri, 17 Feb 2017 12:43:51 -0800
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     "H. Nikolaus Schaller" <hns@...delico.com>
Cc:     devicetree <devicetree@...r.kernel.org>,
        linux-omap <linux-omap@...r.kernel.org>,
        linux-iio@...r.kernel.org, kernel@...a-handheld.com,
        LKML <linux-kernel@...r.kernel.org>, linux-input@...r.kernel.org,
        Discussions about the Letux Kernel 
        <letux-kernel@...nphoenux.org>, Sebastian Reichel <sre@...nel.org>
Subject: Re: [PATCH v9 0/8] drivers: touchscreen: tsc2007 and ads7846/tsc2046
 improvements (use common touchscreen bindings, pre-calibration, spi fix and
 provide iio raw values)

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@...delico.com>:
> > 
> > Hi Dmitry,
> > 
> >> Am 28.01.2017 um 19:16 schrieb H. Nikolaus Schaller <hns@...delico.com>:
> >> 
> >> 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