From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: torvalds@linux-foundation.org, rjw@sisk.pl, bzolnier@gmail.com,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
stable@kernel.org
Subject: Re: linux-next: Tree for July 30
Date: Thu, 7 Aug 2008 15:06:10 -0400 [thread overview]
Message-ID: <20080807150231.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080807115031.6e136ecf.akpm@linux-foundation.org>
On Thu, Aug 07, 2008 at 11:50:31AM -0700, Andrew Morton wrote:
> On Thu, 7 Aug 2008 14:11:09 -0400
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> > On Thu, Jul 31, 2008 at 01:10:56PM -0700, Andrew Morton wrote:
> > >
> > > If that works then great. But I think the printk could be improved.
> > > Please provide sufficient information so that users (not programmers)
> > > can go off and fix things up without needing to email kernel developers.
> > >
> > > One suitable approach would be
> > >
> > > printk("see http://userweb.kernel.org/~dtor/read-this.txt")
> > >
> >
> > Ok, I made a small page here:
> >
> > http://userweb.kernel.org/~dtor/eviocgbit-bug.html
>
> You need to mv that file. It's actually at
> http://userweb.kernel.org/~dtor/eviogcbit-bug.html
>
> And
>
> evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64
> bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
>
> will get a 404.
>
Fixed.
> typo: s/distribbution/distribution/
>
Fixed.
> The text looks good. A user would come away wondering which packages
> need to be updated. Do we have a suitable text pattern whcih will help
> them?
>
> On a fedora system I have
>
> y:/home/akpm> rpm -qa|grep -i syna
> synaptics-0.14.6-2.fc8
>
> So "the synaptics package" would be a suitably distro-neutral description.
>
There is apparently Synaptic package manager - quite similar name - so
I want to emphasize that we are concerned with a driver for X.
> `rpm -qa|grep -i tslib' comes up blank so I don't know about that one.
This is a touchscreen library that is used by embedded people.
Unfortunately I have no idea where the authoritative source is.
>
> > If you think this is sufficient I'd like to put the patch with the
> > warning in 2.6.27 so people and distributions could start updarting
> > affected programs.
>
> Sure. It'd make sense to get that warning into 2.6.25.x and 2.6.26.x
> as well, to accelerate the process a bit.
>
Ok, good.
--
Dmitry
next prev parent reply other threads:[~2008-08-07 19:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080730170635.f737ffe9.sfr@canb.auug.org.au>
2008-07-31 6:10 ` linux-next: Tree for July 30 Andrew Morton
2008-07-31 14:07 ` Dmitry Torokhov
2008-07-31 15:36 ` Bartlomiej Zolnierkiewicz
2008-07-31 15:56 ` Dmitry Torokhov
2008-07-31 17:44 ` Andrew Morton
2008-07-31 18:17 ` Dmitry Torokhov
2008-07-31 18:26 ` Andrew Morton
2008-07-31 18:34 ` Dmitry Torokhov
2008-07-31 18:55 ` Andrew Morton
2008-07-31 19:03 ` Dmitry Torokhov
2008-07-31 19:20 ` Hugh Dickins
2008-07-31 18:48 ` Rafael J. Wysocki
2008-07-31 18:54 ` Dmitry Torokhov
2008-07-31 19:10 ` Linus Torvalds
2008-07-31 19:24 ` Dmitry Torokhov
2008-07-31 19:42 ` Dmitry Torokhov
2008-07-31 20:10 ` Andrew Morton
2008-08-07 18:11 ` Dmitry Torokhov
2008-08-07 18:50 ` Andrew Morton
2008-08-07 19:06 ` Dmitry Torokhov [this message]
2008-08-07 18:55 ` Rafael J. Wysocki
2008-08-01 19:12 ` Linus Torvalds
2008-08-01 19:23 ` Dmitry Torokhov
2008-08-01 19:26 ` Linus Torvalds
2008-07-31 19:44 ` Linus Torvalds
2008-07-31 20:05 ` Dmitry Torokhov
2008-07-31 20:16 ` Linus Torvalds
2008-07-31 20:28 ` Linus Torvalds
2008-07-31 20:39 ` Dmitry Torokhov
2008-07-31 20:28 ` Dmitry Torokhov
2008-07-31 19:13 ` Andrew Morton
2008-07-31 19:57 ` Rafael J. Wysocki
2008-08-04 5:47 ` Stephen Rothwell
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=20080807150231.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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).