All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Dmitrii Lebed <dlebed@quantenna.com>,
	linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
	Avinash Patil <avinashp@quantenna.com>
Subject: Re: [PATCH] cfg80211/nl80211: add DFS offload flag
Date: Tue, 27 Feb 2018 10:40:31 +0200	[thread overview]
Message-ID: <87r2p6hlkw.fsf@codeaurora.org> (raw)
In-Reply-To: <20180222082340.jfogkd4vgtapcyzl@bars> (Sergey Matyukevich's message of "Thu, 22 Feb 2018 11:23:40 +0300")

Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> writes:

> Hello Kalle,
>
>> > Friendly advice: you may want to avoid using this footer in emails on
>> > the kernel.org mailing lists.
>> 
>> Indeed. Most of the time I don't even reply to mails with such
>> disclaimers and patches containing that will be automatically dropped.
>
> Based on our previous experience we already know that sending patches from
> our 'normal' emails with disclaimer is being frowned upon. So all the
> patches are being sent from 'oss' emails. But so far we had impression
> that participating in further discussion was allowed even from email
> addresses with disclaimer.

I think it's just rude to send emails to public with such disclaimers,
this is a public list where people voluntarily use their time to reply
to emails. I guess some people don't mind but there are people who do
not like it, myself included.

-- 
Kalle Valo

      reply	other threads:[~2018-02-27  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 10:56 [PATCH] cfg80211/nl80211: add DFS offload flag Sergey Matyukevich
2018-02-21 11:03 ` Arend van Spriel
2018-02-21 11:25   ` Dmitrii Lebed
2018-02-21 19:59     ` Arend van Spriel
2018-02-22  7:57       ` Kalle Valo
2018-02-22  8:23         ` Sergey Matyukevich
2018-02-27  8:40           ` Kalle Valo [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=87r2p6hlkw.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=avinashp@quantenna.com \
    --cc=dlebed@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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.