From: Gao feng <gaofeng-BthXqXjhjHXQFUHtdCDX3A@public•gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org>
Cc: steffen.klassert-opNxpl+3fjRBDgjK7y7TUQ@public•gmane.org,
herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public•gmane.org,
eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public•gmane.org,
ebiederm-aS9lmoZGLiVWk0Htik3J/w@public•gmane.org
Subject: Re: [PATCH net-next v2 1/2] inetpeer: add namespace support for inetpeer
Date: Fri, 08 Jun 2012 13:27:18 +0800 [thread overview]
Message-ID: <4FD18D36.3090101@cn.fujitsu.com> (raw)
In-Reply-To: <20120607.205348.913373847915721607.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
于 2012年06月08日 11:53, David Miller 写道:
> From: Gao feng <gaofeng@cn•fujitsu.com>
> Date: Fri, 08 Jun 2012 09:44:04 +0800
>
>> Sorry for my pool english, I don't understand this.
>> Can you explain it for me?
>
> Look at the end of the parts of the patch that change
> net/ipv4/inetpeer.c:
>
> @@ -586,3 +617,3 @@ out:
> write_sequnlock_bh(&base->lock);
> }
> EXPORT_SYMBOL(inetpeer_invalidate_tree);
>
> That makes no sense, it's a patch hunk with no "+" or "-"
> lines.
Thanks David,got it.
>
> Your patch was corrupted by something.
>
> This is extremely irritating. I would recommend that you email
> patches to yourself, and try to apply the copies you receive
> in those emails. Because that's what the people trying to use
> your patch are going to do.
>
Sorry, I will try it myself next time. ;)
_______________________________________________
Containers mailing list
Containers@lists•linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
prev parent reply other threads:[~2012-06-08 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 7:52 [PATCH net-next v2 1/2] inetpeer: add namespace support for inetpeer Gao feng
[not found] ` <1338882737-11914-1-git-send-email-gaofeng-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2012-06-05 7:52 ` [PATCH net-next v2 2/2] inetpeer: add parameter net for inet_getpeer_v4, v6 Gao feng
2012-06-05 8:57 ` [PATCH net-next v2 1/2] inetpeer: add namespace support for inetpeer Eric Dumazet
2012-06-05 11:27 ` Steffen Klassert
2012-06-05 12:00 ` Eric Dumazet
2012-06-05 12:15 ` Steffen Klassert
[not found] ` <20120605121510.GD27795-opNxpl+3fjRBDgjK7y7TUQ@public.gmane.org>
2012-06-05 12:18 ` Eric Dumazet
2012-06-05 12:29 ` Gao feng
2012-06-06 17:43 ` David Miller
[not found] ` <20120606.104323.1698446129331745479.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-07 21:43 ` David Miller
[not found] ` <20120607.144301.1259354794384347085.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-08 1:44 ` Gao feng
2012-06-08 3:53 ` David Miller
[not found] ` <20120607.205348.913373847915721607.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-08 5:27 ` Gao feng [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=4FD18D36.3090101@cn.fujitsu.com \
--to=gaofeng-bthxqxjhjhxqfuhtdcdx3a@public$(echo .)gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public$(echo .)gmane.org \
--cc=eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=steffen.klassert-opNxpl+3fjRBDgjK7y7TUQ@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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