From: Andrew Buehler <abuehler.kernel@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Pinter <oliver.pntr@gmail.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>,
SCSI development list <linux-scsi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: USB regression (and other failures) in 2.6.2[45]* - mostly resolved
Date: Thu, 21 Feb 2008 11:05:21 -0500 [thread overview]
Message-ID: <47BDA141.70806@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0802201428390.7056-100000@iolanthe.rowland.org>
On 2/20/2008 2:29 PM, Alan Stern wrote:
> On Wed, 20 Feb 2008, Andrew Buehler wrote:
>
>> In other words: I don't think that's likely to be practical in the
>> present instance. If you have reason to believe otherwise (past
>> positive experience with Novell, for instance), I'd be glad to hear
>> it.
>
> Greg KH may be able to help in that respect.
I know he's in the CC:, but I'm not sure he's reading this thread, and
I'm hesitant to bother people about things out of the blue unless I have
reason to expect that it's something they're going to care about. (Just
because it's a big deal for me doesn't mean it makes one whit of
difference to anyone else, and from what little I've seen on
linux-kernel he seems to be somewhat important and fairly busy...)
>> Is there any place (aside from maybe the kernel changelog, which
>> contains a whole lot - if not several lots - of unrelated
>> information) where I could find a list of config-symbol name
>> additions, changes, deletions and meaning changes by version or by
>> date? That would at least let me build a mapping between the
>> symbols in the older config and the ones in the new one, which is
>> about where I would have to start.
>
> Not as far as I know.
Then I suppose I'm reduced to browsing the Kconfig files, reading old
changelogs, and trying a lot of different configs... thanks anyway.
--
Andrew Buehler
next prev parent reply other threads:[~2008-02-21 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 21:45 USB regression (and other failures) in 2.6.2[45]* Andrew Buehler
2008-02-16 14:32 ` Oliver Pinter
2008-02-16 15:20 ` Alan Stern
2008-02-16 16:46 ` Andrew Buehler
2008-02-16 17:16 ` Alan Stern
2008-02-16 21:33 ` Andrew Buehler
2008-02-16 23:11 ` Alan Stern
2008-02-17 1:12 ` Andrew Buehler
2008-02-17 3:35 ` Alan Stern
2008-02-17 16:21 ` Andrew Buehler
2008-02-19 20:35 ` USB regression (and other failures) in 2.6.2[45]* - mostly resolved Andrew Buehler
2008-02-20 15:50 ` Alan Stern
2008-02-20 17:06 ` Andrew Buehler
2008-02-20 17:15 ` Alan Stern
2008-02-20 18:27 ` Andrew Buehler
2008-02-20 19:29 ` Alan Stern
2008-02-21 16:05 ` Andrew Buehler [this message]
2008-02-21 16:36 ` Alan Stern
2008-02-21 17:17 ` Greg KH
2008-02-21 19:43 ` Andrew Buehler
2008-02-21 20:02 ` Alan Stern
2008-02-17 4:10 ` [OT] GMail (was USB regression (and other failures)...) Joseph Fannin
2008-02-17 10:55 ` USB regression (and other failures) in 2.6.2[45]* Sergey Vlasov
2008-02-17 7:20 ` Paul Jackson
2008-02-17 16:17 ` Andrew Buehler
2008-02-17 16:20 ` Paul Jackson
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=47BDA141.70806@gmail.com \
--to=abuehler.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=stern@rowland.harvard.edu \
/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