From: Ben Hutchings <ben@decadent.org.uk>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: Maximilian Attems <max@stro.at>, Michael Prokop <mika@debian.org>,
Marco d'Itri <md@linux.it>,
Debian kernel team <debian-kernel@lists.debian.org>,
Mike Miller <mike.miller@hp.com>,
Jens Axboe <jaxboe@fusionio.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>,
Martin Pitt <martin.pitt@ubuntu.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: HP G6 hardware kernel boot issue > 2.6.37 cciss/hpsa
Date: Tue, 08 Mar 2011 13:49:48 +0000 [thread overview]
Message-ID: <1299592188.4146.2.camel@localhost> (raw)
In-Reply-To: <1299580166.11985.11.camel@firesoul.comx.local>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Tue, 2011-03-08 at 11:29 +0100, Jesper Dangaard Brouer wrote:
> On Thu, 2011-03-03 at 13:47 +0100, Maximilian Attems wrote:
> > On Wed, 02 Mar 2011, Jesper Dangaard Brouer wrote:
> >
> [...]
> > please file proper Debian bug report with reportbug.
> > we already have scripts dealing with such device changes.
> > Had previously thought that the need of them was over after the
> > libata change, but obviously you show the contrare.
> >
> > So fire up reportbug and report against linux-2.6 with severity grave.
>
> I finally succeeded filing a Debian bug-report (as Debians mail system
> clamav kept categorizing me as malware... hmm)
Nothing personal, it was bouncing most incoming mail for a few hours.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-03-08 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:42 HP G6 hardware kernel boot issue > 2.6.37 cciss/hpsa Jesper Dangaard Brouer
2011-03-03 12:47 ` Maximilian Attems
2011-03-08 10:29 ` Jesper Dangaard Brouer
2011-03-08 13:49 ` Ben Hutchings [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 17:42 Jesper Dangaard Brouer
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=1299592188.4146.2.camel@localhost \
--to=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=eric.dumazet@gmail.com \
--cc=hawk@comx.dk \
--cc=jaxboe@fusionio.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=max@stro.at \
--cc=md@linux.it \
--cc=mika@debian.org \
--cc=mike.miller@hp.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.