From: Grant Likely <grant.likely@secretlab.ca>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3] Series short description
Date: Thu, 2 Apr 2009 07:41:23 -0600 [thread overview]
Message-ID: <fa686aa40904020641k4db9e66dh4f80b5b32f68455d@mail.gmail.com> (raw)
In-Reply-To: <20090402.005715.02030593.davem@davemloft.net>
On Thu, Apr 2, 2009 at 1:57 AM, David Miller <davem@davemloft.net> wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
> Date: Wed, 01 Apr 2009 00:16:46 -0600
>
>> Here are the fec_mpc52xx patches which should be picked up for 2.6.29.
>> Patch #1 fixes a dma related BUG_ON() discovered after the merge window
>> opened. #2 & #3 were original a single patch posted prior to the merge
>> window, but not having a s-o-b line from the original author held them up.
>> In the end I rewrote it from scratch as two patches just so I can get
>> them merged. #2 makes the driver use net_device_ops, and #3 fixes a NULL
>> dereference.
>>
>> I've tested these patches on several MPC5200 platforms.
>
> All applied, thanks Grant.
Thanks David!
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-04-02 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 6:16 [PATCH 0/3] Series short description Grant Likely
2009-04-01 6:16 ` [PATCH 1/3] net/fec_mpc52xx: fix BUG on missing dma_ops Grant Likely
2009-04-01 6:16 ` [PATCH 2/3] net/fec_mpc52xx: Migrate to net_device_ops Grant Likely
2009-04-01 6:17 ` [PATCH 3/3] net/fec_mpc52xx: Don't dereference phy_device if it is NULL Grant Likely
2009-04-02 7:57 ` [PATCH 0/3] Series short description David Miller
2009-04-02 13:41 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-04 23:10 Dave Jiang
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=fa686aa40904020641k4db9e66dh4f80b5b32f68455d@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).