public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it, Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [LTP] [PATCH] syscalls/ioctl03: add IFF_NO_CARRIER feature flag
Date: Mon, 10 Oct 2022 17:20:20 +0200	[thread overview]
Message-ID: <Y0Q4NH77RySQFkDA@yuki> (raw)
In-Reply-To: <Y0Qx/dUX3f/TbZ5R@pevik>

Hi!
> @Sven it's not a good idea to post to ML without being subscribed,
> please subscribe next time before posting.

I've added him to allowed filter, I do that automatically for all email
addresses that send patches. But that still means that first post to the
ML will be delayed by a day or so until we get to review the queue.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2022-10-10 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  7:08 [LTP] [PATCH] syscalls/ioctl03: add IFF_NO_CARRIER feature flag Jan Stancek
2022-10-10 12:24 ` Cyril Hrubis
2022-10-10 12:53 ` Petr Vorel
2022-10-10 13:19   ` Jan Stancek
2022-10-10 14:53     ` Petr Vorel
2022-10-10 15:20       ` Cyril Hrubis [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=Y0Q4NH77RySQFkDA@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=svens@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox