From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Make frontend features distinct from netback feature flags.
Date: Fri, 09 Jul 2010 10:53:15 -0700 [thread overview]
Message-ID: <4C37620B.8040108@goop.org> (raw)
In-Reply-To: <291EDFCB1E9E224A99088639C47620227A476E6836@LONPMAILBOX01.citrite.net>
On 07/09/2010 09:17 AM, Paul Durrant wrote:
> Ian,
>
> I regenerated the patch with git-format-patches and re-checked with checkpatch.pl:
>
> [pauldu@cosworth:/misc/scratch/pauldu/git/linux-2.6-xen]./scripts/checkpatch.pl 0001-Make-frontend-features-distinct-from-netback-feature.patch
> total: 0 errors, 0 warnings, 237 lines checked
>
> 0001-Make-frontend-features-distinct-from-netback-feature.patch has no obvious style problems and is ready for submission.
>
> Can you see this ok now?
>
Actually I had already committed your changes with some fixups to
xen/dom0/backend/netback (excluding the feature watch one). Could you
double-check your changes in that branch?
Thanks,
J
next prev parent reply other threads:[~2010-07-09 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 9:28 [PATCH] Fix basic indentation issue Paul Durrant
2010-07-02 9:28 ` [PATCH] Add a new style of passing GSO packets to frontends Paul Durrant
2010-07-02 9:28 ` [PATCH] Make frontend features distinct from netback feature flags Paul Durrant
2010-07-02 14:54 ` Paul Durrant
2010-07-09 16:17 ` Paul Durrant
2010-07-09 17:53 ` Jeremy Fitzhardinge [this message]
2010-07-12 9:07 ` Paul Durrant
2010-07-03 7:22 ` [PATCH] Add a new style of passing GSO packets to frontends Jeremy Fitzhardinge
2010-07-09 14:59 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2010-07-02 14:55 [PATCH] Make frontend features distinct from netback feature flags Paul Durrant
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=4C37620B.8040108@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.