Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1581335 > unrolled thread

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)

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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) "H. Nikolaus Schaller" <hns@goldelico.com> - 2017-02-15 15:10 +0100
    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) Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-02-17 21:50 +0100
      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) "H. Nikolaus Schaller" <hns@goldelico.com> - 2017-02-18 12:40 +0100

#1581335 — 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)

Hi Dmitry,

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

What is still missing what we can do or provide as information?

BR and thanks,
Nikolaus

[toc] | [next] | [standalone]

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

[toc] | [prev] | [next] | [standalone]

#1583887

Hi Dmitry,

> Am 17.02.2017 um 21:43 schrieb Dmitry Torokhov <dmitry.torokhov@gmail.com>:
> 
> 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@goldelico.com>:
>>> 
>>> Hi Dmitry,
>>> 
>>>> Am 28.01.2017 um 19:16 schrieb H. Nikolaus Schaller <hns@goldelico.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.

Fine. Now I have better understanding.

> 
>> 
>> What is still missing what we can do or provide as information?
> 
> I just replied to the other email from you.

BR and thanks,
Nikolaus

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web