[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140927.185501.2157704066172736196.davem@davemloft.net>
Date: Sat, 27 Sep 2014 18:55:01 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: fugang.duan@...escale.com
Cc: netdev@...r.kernel.org, Frank.Li@...escale.com
Subject: Re: [PATCH v1 0/4] net: fec: Code cleanup
From: "fugang.duan@...escale.com" <fugang.duan@...escale.com>
Date: Sat, 27 Sep 2014 09:51:52 +0000
> From: David Miller <davem@...emloft.net> Sent: Saturday, September 27, 2014 4:06 AM
>>To: Duan Fugang-B38611
>>Cc: netdev@...r.kernel.org; Li Frank-B20596
>>Subject: Re: [PATCH v1 0/4] net: fec: Code cleanup
>>
>>From: Fugang Duan <b38611@...escale.com>
>>Date: Tue, 23 Sep 2014 15:40:54 +0800
>>
>>> This patches does several things:
>>> - Fixing multiqueue issue.
>>> - Removing the unnecessary errata workaround.
>>> - Aligning the data buffer dma map/unmap size.
>>> - Freeing resource after probe failed.
>>
>>Series applied to net-next, thanks.
>>
>>Please always explicitly state what tree you expect your patches to be
>>applied to in the future.
>
> No special requirement, just follow the normal rel flow.
That doesn't mean anything to me.
You must state what tree your patches apply properly to, and thus
where you expect them to be intergrated.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists