Hello Roger,
        Thank you for the time and patience you devoted to reading my messages 
and e-mails. I really appreciate that.
        I can't use git send-email so I attach the patches directly. In the 
0001 patch I introduce suspend_cancel mechanism for frontend devices and in the 
0002 patch I release all resources after hot unplug NICs.

    Note: These two patches is on the base of the origin/release/10.2.0 branch 
and the 0002 patch is made after the 0001 patch.

发件人: freebsd xen [mailto:roger....@citrix.com] 
发送时间: 2016年12月13日 22:29
收件人: Liuyingdong
抄送: freebsd-xen@freebsd.org; Zhaojun (Euler); Suoben; Ouyangzhaowei (Charles)
主题: Re: [PATCH]netfront: need release all resources after adding and removing 
NICs time and again

On Tue, Dec 13, 2016 at 02:03:08PM +0800, liuyingdong wrote:
> Hello Roger,
>     I want to know how about this patch,Please let me know if you have any 
> questions.
>     Thanks.


Thanks for the patches! This one is looking fine, it's just that I'm a little 
bit busy at the moment, and there are some issues in HEAD related to Xen that I 
would like to fix before pushing anything new.

In any case, I see that you are sending the patches using Thunderbird, which is 
not ideal (MUAs tend to mangle patches). The preferred way for sending patches 
is using "git send-email"[0] directly. There are also several tutorials online 
that will help you setup git send-email correctly. If there's some reason why 
you can't use git send-email I would recommend that you also attach the patches 
directly to emails, that way they won't probably get mangled.


[0] https://git-scm.com/docs/git-send-email

Attachment: 0001-introduce-suspend-cancel-mechanism-for-frontend-devices.patch
Description: 0001-introduce-suspend-cancel-mechanism-for-frontend-devices.patch

Attachment: 0002-netfront-need-release-all-resources-after-hot-plug.patch
Description: 0002-netfront-need-release-all-resources-after-hot-plug.patch

freebsd-xen@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to