From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: seraph@xs4all.nl, Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
linux-kernel@vger.kernel.org
Subject: Fwd: [SPARC64] INO problem Re: [Bug 10273] New: Sun GEM (PCI) - network device doesn't work
Date: Wed, 2 Apr 2008 20:26:55 +0200 [thread overview]
Message-ID: <20080402182655.GA2739@ami.dom.local> (raw)
In-Reply-To: <20080317143624.da313311.akpm@linux-foundation.org>
Nice work Jos! I forward it to the author and the lists.
Jarek P.
Andrew Morton wrote, On 03/17/2008 10:36 PM:
> On Mon, 17 Mar 2008 14:25:50 -0700 (PDT)
> bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=10273
>>
>> Summary: Sun GEM (PCI) - network device doesn't work
----- Forwarded message from bugme-daemon@bugzilla.kernel.org -----
> ------- Comment #24 from seraph@xs4all.nl 2008-04-02 07:24 -------
> I did bisection. The bad commit is:
>
> 5a606b72a4309a656cd1a19ad137dc5557c4b8ea is first bad commit
> commit 5a606b72a4309a656cd1a19ad137dc5557c4b8ea
> Author: David S. Miller <davem@sunset.davemloft.net>
> Date: Mon Jul 9 22:40:36 2007 -0700
>
> [SPARC64]: Do not ACK an INO if it is disabled or inprogress.
>
>
> --
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
----- End forwarded message -----
next parent reply other threads:[~2008-04-02 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080317143624.da313311.akpm@linux-foundation.org>
2008-04-02 18:26 ` Jarek Poplawski [this message]
2008-04-10 10:30 ` [SPARC64] INO problem Re: [Bug 10273] New: Sun GEM (PCI) - network device doesn't work David Miller
2008-04-25 7:26 ` David Miller
2008-04-25 19:59 ` Jos van der Ende
2008-04-25 20:35 ` David Miller
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=20080402182655.GA2739@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=seraph@xs4all.nl \
/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