From: Andrew Morton <akpm@linux-foundation.org>
To: "Rick L. Vinyard Jr." <rvinyard@cs.nmsu.edu>
Cc: linux-kernel@vger.kernel.org, felipe.balbi@nokia.com,
pavel@ucw.cz, jayakumar.lkml@gmail.com,
linux-usb@vger.kernel.org, oliver@neukum.org,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
npavel@ituner.com, tomi.valkeinen@nokia.com, tony@atomide.com,
FlorianSchandinat@gmx.de, krzysztof.h1@wp.pl,
linux-fbdev@vger.kernel.org, jkosina@suse.cz,
bonbons@linux-vserver.org
Subject: Re: [PATCH] Add sysfs support for fbdefio delay
Date: Wed, 03 Mar 2010 00:19:19 +0000 [thread overview]
Message-ID: <20100302161919.19df3a18.akpm@linux-foundation.org> (raw)
In-Reply-To: <201003021847.o22IlYR8004349@mustang.cs.nmsu.edu>
On Tue, 02 Mar 2010 11:47:34 -0700
"Rick L. Vinyard Jr." <rvinyard@cs.nmsu.edu> wrote:
> This patch adds support for examining and modifying the fbdefio delay
> parameter through sysfs. It also adds two driver definable minimum
> and maximum bounds.
>
> The default behavior is to not permit modifications if delay_max is 0,
> thus preventing modification of the delay if the driver does not
> explicitly permit modification.
Why is this being added? You have some device which doesn't function
properly without this change?
If so, that's pretty critical changelog info - we presently have no
reason to merge the patch!
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: "Rick L. Vinyard Jr." <rvinyard@cs.nmsu.edu>
Cc: linux-kernel@vger.kernel.org, felipe.balbi@nokia.com,
pavel@ucw.cz, jayakumar.lkml@gmail.com,
linux-usb@vger.kernel.org, oliver@neukum.org,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
npavel@ituner.com, tomi.valkeinen@nokia.com, tony@atomide.com,
FlorianSchandinat@gmx.de, krzysztof.h1@wp.pl,
linux-fbdev@vger.kernel.org, jkosina@suse.cz,
bonbons@linux-vserver.org
Subject: Re: [PATCH] Add sysfs support for fbdefio delay
Date: Tue, 2 Mar 2010 16:19:19 -0800 [thread overview]
Message-ID: <20100302161919.19df3a18.akpm@linux-foundation.org> (raw)
In-Reply-To: <201003021847.o22IlYR8004349@mustang.cs.nmsu.edu>
On Tue, 02 Mar 2010 11:47:34 -0700
"Rick L. Vinyard Jr." <rvinyard@cs.nmsu.edu> wrote:
> This patch adds support for examining and modifying the fbdefio delay
> parameter through sysfs. It also adds two driver definable minimum
> and maximum bounds.
>
> The default behavior is to not permit modifications if delay_max is 0,
> thus preventing modification of the delay if the driver does not
> explicitly permit modification.
Why is this being added? You have some device which doesn't function
properly without this change?
If so, that's pretty critical changelog info - we presently have no
reason to merge the patch!
Thanks.
next prev parent reply other threads:[~2010-03-03 0:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 22:15 [PATCH] Add sysfs support for fbdefio delay Rick L. Vinyard Jr.
2010-02-25 22:15 ` Rick L. Vinyard Jr.
2010-02-25 22:32 ` Bruno Prémont
2010-02-25 22:32 ` Bruno Prémont
2010-02-25 22:41 ` Rick L. Vinyard, Jr.
2010-02-25 22:41 ` Rick L. Vinyard, Jr.
2010-02-26 2:30 ` Jaya Kumar
2010-02-26 2:30 ` Jaya Kumar
2010-02-26 10:53 ` Bruno Prémont
2010-02-26 10:53 ` Bruno Prémont
2010-02-26 11:09 ` Jaya Kumar
2010-02-26 11:09 ` Jaya Kumar
2010-02-26 11:37 ` Bruno Prémont
2010-02-26 11:37 ` Bruno Prémont
2010-03-01 16:10 ` Rick L. Vinyard, Jr.
2010-03-01 16:10 ` Rick L. Vinyard, Jr.
2010-03-02 6:49 ` Jaya Kumar
2010-03-02 6:49 ` Jaya Kumar
2010-03-02 15:36 ` Rick L. Vinyard, Jr.
2010-03-02 15:36 ` Rick L. Vinyard, Jr.
2010-03-03 0:11 ` Jaya Kumar
2010-03-03 0:11 ` Jaya Kumar
2010-04-13 15:50 ` Rick L. Vinyard, Jr.
2010-04-13 15:50 ` Rick L. Vinyard, Jr.
2010-03-02 18:47 ` Rick L. Vinyard Jr.
2010-03-02 18:47 ` Rick L. Vinyard Jr.
2010-03-03 0:19 ` Andrew Morton [this message]
2010-03-03 0:19 ` Andrew Morton
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=20100302161919.19df3a18.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=FlorianSchandinat@gmx.de \
--cc=bonbons@linux-vserver.org \
--cc=dmitry.torokhov@gmail.com \
--cc=felipe.balbi@nokia.com \
--cc=jayakumar.lkml@gmail.com \
--cc=jkosina@suse.cz \
--cc=krzysztof.h1@wp.pl \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=npavel@ituner.com \
--cc=oliver@neukum.org \
--cc=pavel@ucw.cz \
--cc=rvinyard@cs.nmsu.edu \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.