linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-man@vger.kernel.org,
	"Maciej Żenczykowski" <maze@google.com>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	"Matthias Gerstner" <matthias.gerstner@suse.com>,
	"Avinesh Kumar" <akumar@suse.de>
Subject: Re: [PATCH 1/1] socket.7: Mention CAP_NET_RAW on SO_MARK
Date: Wed, 17 Jan 2024 13:02:13 +0100	[thread overview]
Message-ID: <ZafBxnhOSWxBRWko@debian> (raw)
In-Reply-To: <20240117091452.GB2665992@pevik>

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

Hi Petr,

On Wed, Jan 17, 2024 at 10:14:52AM +0100, Petr Vorel wrote:
> Hi Alex,
> 
> > Hi Petr,
> 
> > On Tue, Jan 16, 2024 at 12:04:18PM +0100, Petr Vorel wrote:
> > > Added in 079925cce1d0 ("net: allow SO_MARK with CAP_NET_RAW") in v5.17.
> 
> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> 
> > Patch applied.  Thanks!
> 
> Thank you! BTW I don't see this patch in git tree [1], maybe you just haven't
> push yet.

That's it.  I'm first pushing them to a 'contrib' branch (similar to
Linux 'next') in my own server[1], and after one day or so I push to
master.  That buffering allows me to catch some mistakes.

[1]:  <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/log/?h=contrib>

	$ git log --all --graph --oneline -10
	* 0c118822f (alx/contrib, contrib) open.2: srcfix
	* 24347d22a syscalls.2: ffix
	* 9e04cb40f mremap.2: wfix
	* 3a271d5b8 fts.3, div_t.3type: ffix
	* 527f31b9f socket.7: Mention CAP_NET_RAW on SO_MARK
	| * 71c25f15d (alx/MR, MR) man*/: ffix (MR.sed)
	|/  
	* d82ce270c (HEAD -> master, korg/master, alx/main, main) locale.5: tfix
	* f65154cba cpuid.4: Note which CPUs don't support CPUID and what happens
	* f98168310 sched_getcpu.3: tfix
	* 26cdb3ebb faccessat(2), utimensat(2): Document AT_EMPTY_PATH flag

I'll push in a moment to master.

Have a lovely day,
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-01-17 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 11:04 [PATCH 1/1] socket.7: Mention CAP_NET_RAW on SO_MARK Petr Vorel
2024-01-16 15:14 ` Alejandro Colomar
2024-01-17  9:14   ` Petr Vorel
2024-01-17 12:02     ` Alejandro Colomar [this message]
2024-01-17 12:08       ` Petr Vorel

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=ZafBxnhOSWxBRWko@debian \
    --to=alx@kernel.org \
    --cc=akumar@suse.de \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=matthias.gerstner@suse.com \
    --cc=maze@google.com \
    --cc=pvorel@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).