All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] extensions: libxt_devgroup: Add translation to nft
Date: Tue, 22 Dec 2015 18:29:08 +0100	[thread overview]
Message-ID: <20151222172908.GA21240@salvia> (raw)
In-Reply-To: <CAKHNQQHYwBq-uaiFfT8cv6bWfEf17AM0y650VKJ8Rpg7B2pUmA@mail.gmail.com>

On Tue, Dec 22, 2015 at 10:50:34PM +0530, Shivani Bhardwaj wrote:
> On Tue, Dec 22, 2015 at 10:30 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > On Sun, Dec 20, 2015 at 05:33:37PM +0530, Shivani Bhardwaj wrote:
> >> Add translation of device group to nftables.
> >
> > git am /tmp/extensions-libxt_devgroup-Add-translation-to-nft.patch -s
> > Applying: extensions: libxt_devgroup: Add translation to nft
> > error: patch failed: extensions/libxt_devgroup.c:37
> > error: extensions/libxt_devgroup.c: patch does not apply
> > Patch failed at 0001 extensions: libxt_devgroup: Add translation to nft
> > The copy of the patch that failed is found in:
> >    /home/pablo/devel/scm/git-netfilter/iptables/.git/rebase-apply/patch
> > When you have resolved this problem, run "git am --continue".
> > If you prefer to skip this patch, run "git am --skip" instead.
> > To restore the original branch and stop patching, run "git am --abort".
> >
> > This one doesn't apply for some reason.
> 
> Should I be sending this one again then?

Of course. If you can't see a patch here:

http://git.netfilter.org/iptables/log/?h=xlate3

Then it needs to be submitted again.

  reply	other threads:[~2015-12-22 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 12:03 [PATCH] extensions: libxt_devgroup: Add translation to nft Shivani Bhardwaj
2015-12-22 17:00 ` Pablo Neira Ayuso
2015-12-22 17:20   ` Shivani Bhardwaj
2015-12-22 17:29     ` Pablo Neira Ayuso [this message]
2015-12-22 19:10 Shivani Bhardwaj
2015-12-22 20:30 ` Shivani Bhardwaj

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=20151222172908.GA21240@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=shivanib134@gmail.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.