From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Alexander Petrovsky <askjuise@gmail.com>
Cc: Julian Anastasov <ja@ssi.bg>,
"LinuxVirtualServer.org users mailing list."
<lvs-users@linuxvirtualserver.org>,
Simon Horman <horms@verge.net.au>,
"lvs-devel@vger.kernel.org" <lvs-devel@vger.kernel.org>,
brouer@redhat.com
Subject: Re: [lvs-users] Micro ipvsadm patch
Date: Mon, 23 Mar 2020 09:09:03 +0100 [thread overview]
Message-ID: <20200323090903.0753d01a@carbon> (raw)
In-Reply-To: <CAH57y_R=xUY-MPkFfeoOpH_f3eCLWDKuwW+wtNOKD9JJMjRkTw@mail.gmail.com>
On Fri, 20 Mar 2020 21:16:47 +0300
Alexander Petrovsky <askjuise@gmail.com> wrote:
> Oh, thanks.
>
> Where I can find out the full procedure?
As this is a tool that is closely related to the kernel, I/we try to
follow the kernel submitting patch guidelines, but losely:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
--Jesper
> пт, 20 марта 2020 г. в 15:32, Jesper Dangaard Brouer <brouer@redhat.com>:
>
> > On Wed, 11 Mar 2020 15:05:58 +0300
> > Alexander Petrovsky <askjuise@gmail.com> wrote:
> >
> > > Hello!
> > >
> > > This micro ipvsadm patch fixes wrong (negative) FWMARK values
> > > representation:
> > >
> > > # ipvsadm -L -f 2882430849
> > > Prot LocalAddress:Port Scheduler Flags
> > > -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> > > FWM -1412536447 wlc
> > > -> abc.my.host.net. Tunnel 1 0 0
> > >
> >
> > Hi Alexander,
> >
> > Your patch submission does not follow all the procedures, but given
> > this is fairly trivial, and Julian didn't object, I went ahead and
> > applied the patch with (your SoB and credit to you), here:
> >
> >
> > https://git.kernel.org/pub/scm/utils/kernel/ipvsadm/ipvsadm.git/commit/?id=e61c8cdd1dcad
> >
> > --
> > Best regards,
> > Jesper Dangaard Brouer
> > MSc.CS, Principal Kernel Engineer at Red Hat
> > LinkedIn: http://www.linkedin.com/in/brouer
> >
> > --
> Alexander Petrovsky
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2020-03-23 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH57y_TcVNdCe7ciAXX85HzWXPhWgUWvXn2f7r8yWjM2TUNecQ@mail.gmail.com>
2020-03-20 12:31 ` [lvs-users] Micro ipvsadm patch Jesper Dangaard Brouer
2020-03-20 18:16 ` Alexander Petrovsky
2020-03-23 8:09 ` Jesper Dangaard Brouer [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=20200323090903.0753d01a@carbon \
--to=brouer@redhat.com \
--cc=askjuise@gmail.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=lvs-users@linuxvirtualserver.org \
/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.