From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: Lnux 2.6.24-rc5
Date: Wed, 12 Dec 2007 18:29:11 +0530 [thread overview]
Message-ID: <1197464351.4710.103.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20071212065437.73e708ef@weaponx>
On Wed, 2007-12-12 at 06:54 -0600, Josh Boyer wrote:
> On Wed, 12 Dec 2007 15:25:01 +0530
> Subrata Modak <subrata@linux.vnet.ibm.com> wrote:
>
> > On Mon, 2007-12-10 at 21:40 -0800, Linus Torvalds wrote:
> > > It's been a week, and I promised to be a good boy and try to follow my
> > > release rules, so here is the next -rc.
> > >
> > > Things _have_ slowed down, although I'd obviously be lying if I said we've
> > > got all the regressions handled and under control. They are being worked
> > > on, and the list is shrinking, but at a guess, we're definitely not going
> > > to have a final 2.6.24 out before xmas unless santa puts some more elves
> > > to work on those regressions..
> > >
> > > So any elves out there - please keep working.
> > >
> > > I'm including the shortlog since it's small enough, and quite frankly,
> > > gives about as readable explanation of the changes as can be imagined.
> > > Nothing hugely exciting here.
> > >
> > > I'd post the diffstat too, but it's not really all that interesting, and
> > > it only highlights a textually big PA-RISC revert, and the powerpc
> > > defconfig updates. And the Blackfin SPI driver. The rest is largely random
> > > noise in various subsystems (drivers/net, xfs filesystem, and arch updates
> > > are some of the areas that show more changes).
> > >
> > > Linus
> > >
> > > ---
> > >
> > > Benjamin Herrenschmidt (6):
> > > ibm_newemac: Fix ZMII refcounting bug
> > > ibm_newemac: Workaround reset timeout when no link
> > > ibm_newemac: Cleanup/Fix RGMII MDIO support detection
> > > ibm_newemac: Cleanup/fix support for STACR register variants
> > > ibm_newemac: Update file headers copyright notices
> > > powerpc: Fix IDE legacy vs. native fixups
> > >
> >
> > Dear Benjamin,
> >
> > Since you are working on Device drivers, do you want to see whether your
> > Device drivers testcases can fit in here in LTP:
> > http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/kernel/device-drivers/,
>
> There are no testcases for the EMAC drivers per se. Also, I don't see
> any testcases for any network driver in there at all. Is that not
> something LTP is testing yet?
Nope. LTP is not doing that. Like lkml it is also dependent on community
for contributions. Our Device Driver Test cases needs to be
re-rejuvenated as they are pretty old. I am of the idea of maintaining
Architecture specific device drivers testcases inside LTP as well
provided you guys give me the required test cases.
--Subrata
>
> josh
prev parent reply other threads:[~2007-12-12 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.9999.0712102130370.28293@woody.linux-foundation.org>
2007-12-12 9:55 ` Lnux 2.6.24-rc5 Subrata Modak
2007-12-12 12:54 ` Josh Boyer
2007-12-12 12:59 ` Subrata Modak [this message]
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=1197464351.4710.103.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jwboyer@linux.vnet.ibm.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 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).