From: Matthew Wilcox <matthew@wil.cx>
To: jie.yang@atheros.com
Cc: akpm@linux-foundation.org, bugme-daemon@bugzilla.kernel.org,
harn-solo@gmx.de, jeff@garzik.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]atl1e:fix bug [Bug 11454] New: atl1e - BUG: scheduling while atomic: modprobe/678/0x00000002
Date: Sat, 30 Aug 2008 23:08:47 -0600 [thread overview]
Message-ID: <20080831050837.GK1239@parisc-linux.org> (raw)
In-Reply-To: <12201583182726-git-send-email-jie.yang@atheros.com>
On Sun, Aug 31, 2008 at 12:51:58PM +0800, jie.yang@atheros.com wrote:
> from Jie Yang <jie.yang@atheros.com>
>
> On Saturday, August 30, 2008 5:27 AM
> Andrew Morton <akpm@linux-foundation.org]>
> > On Fri, 29 Aug 2008 14:08:09 -0700 (PDT)
> > bugme-daemon@bugzilla.kernel.org wrote:
> >
> > > http://bugzilla.kernel.org/show_bug.cgi?id=11454
> > >
> > > Summary: atl1e - BUG: scheduling while atomic:
> > > modprobe/678/0x00000002
> > > Product: Drivers
> > > Version: 2.5
> > > KernelVersion: 2.6.27-rc5
> > > Platform: All
> > > OS/Version: Linux
> > > Tree: Mainline
> > > Status: NEW
> > > Severity: high
> > > Priority: P1
> > > Component: Network
> > > AssignedTo: jgarzik@pobox.com
How about taking my original patch, sent August 12th instead? That has
a good changelog and proper attribution. The removal of the
unnecessary casts can be a separate message.
If you weren't cc'd on the patch (Jeff was), you can pick it up from
netdev.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-08-31 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 4:51 jie.yang
2008-08-31 5:08 ` Matthew Wilcox [this message]
2008-08-31 5:31 ` Jie Yang
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=20080831050837.GK1239@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=harn-solo@gmx.de \
--cc=jeff@garzik.org \
--cc=jie.yang@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®