From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Vipul Kumar Samar <vipulkumar.samar@st.com>
Subject: Re: [PATCH 1/2] Input: smtpe-ts: Use msecs_to_jiffies() instead of HZ
Date: Fri, 22 May 2015 16:30:48 -0700 [thread overview]
Message-ID: <20150522233048.GA20687@dtor-ws> (raw)
In-Reply-To: <201505220205.52913.marex@denx.de>
On Fri, May 22, 2015 at 02:05:52AM +0200, Marek Vasut wrote:
> On Friday, May 22, 2015 at 02:01:21 AM, Dmitry Torokhov wrote:
> > On Fri, May 22, 2015 at 01:58:34AM +0200, Marek Vasut wrote:
> > > On Friday, May 08, 2015 at 07:22:28 PM, Dmitry Torokhov wrote:
> > > > On Fri, May 08, 2015 at 11:47:39AM +0200, Marek Vasut wrote:
> > > > > On Friday, May 08, 2015 at 07:28:20 AM, Dmitry Torokhov wrote:
> > > > > > On Fri, May 08, 2015 at 07:45:48AM +0530, Viresh Kumar wrote:
> > > > > > > On 8 May 2015 at 07:23, Marek Vasut <marex@denx.de> wrote:
> > > > > > > > Use msecs_to_jiffies(20) instead of plain (HZ / 50), as the
> > > > > > > > former is much more explicit about it's behavior. We want
> > > > > > > > to schedule the task 20 mS from now, so make it explicit in
> > > > > > > > the code.
> > > > > > > >
> > > > > > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > > > > > Cc: Vipul Kumar Samar <vipulkumar.samar@st.com>
> > > > > > > > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > > > > > > > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > > > > > > ---
> > > > > > > >
> > > > > > > > drivers/input/touchscreen/stmpe-ts.c | 2 +-
> > > > > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > > >
> > > > > > > Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
> > > > > >
> > > > > > Applied both, thank you.
> > > > >
> > > > > Thank you! Shall I submit them for -stable as well please ?
> > > >
> > > > Please.
> > >
> > > Hi,
> > >
> > > these patches still didn't make it for Linus's tree. I cannot submit
> > > to -stable unless they hit Linus's tree to my knowledge. Shall I wait
> > > some more please ?
> >
> > They are in -next. I guess I could get them in 4.1...
>
> In case it's not much of a hassle for everyone involved, it would be nice.
> Otherwise, I will just wait for 4.2 merge window to open and submit for
> stable after that. Just let me know what you prefer and I will do so.
I sent pull request to Linus, so let's see.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-05-22 23:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 1:53 [PATCH 1/2] Input: smtpe-ts: Use msecs_to_jiffies() instead of HZ Marek Vasut
2015-05-08 1:53 ` [PATCH 2/2] Input: smtpe-ts: Wait 50mS until polling for pen-up Marek Vasut
2015-05-08 2:17 ` Viresh Kumar
2015-05-08 2:15 ` [PATCH 1/2] Input: smtpe-ts: Use msecs_to_jiffies() instead of HZ Viresh Kumar
2015-05-08 5:28 ` Dmitry Torokhov
2015-05-08 9:47 ` Marek Vasut
2015-05-08 17:22 ` Dmitry Torokhov
2015-05-21 23:58 ` Marek Vasut
2015-05-22 0:01 ` Dmitry Torokhov
2015-05-22 0:05 ` Marek Vasut
2015-05-22 23:30 ` Dmitry Torokhov [this message]
2015-05-24 21:54 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150522233048.GA20687@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=marex@denx.de \
--cc=vipulkumar.samar@st.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).