All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pavel@ucw.cz
Cc: kvalo@codeaurora.org, torvalds@linux-foundation.org,
	xiyou.wangcong@gmail.com, akpm@linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl1251: add a missing spin_lock_init()
Date: Thu, 31 Aug 2017 10:33:05 -0700 (PDT)	[thread overview]
Message-ID: <20170831.103305.1809212990680774811.davem@davemloft.net> (raw)
In-Reply-To: <20170831144743.GA21261@amd>

From: Pavel Machek <pavel@ucw.cz>
Date: Thu, 31 Aug 2017 16:47:43 +0200

> Dave, Linus -- can you still take the patch?

Pavel, please do not bypass maintainers like this.

It's really rude, and if you do things like that instead of
trying to work properly with us, your relationship with
these maintainers will suffer in the long term.

Thank you.

  reply	other threads:[~2017-08-31 17:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  0:52 [GIT] Networking David Miller
2017-08-16  2:21 ` Linus Torvalds
2017-08-16  3:03   ` David Miller
2017-08-30  9:48 ` Pavel Machek
2017-08-30 14:45   ` Kalle Valo
2017-08-30 17:11     ` David Miller
2017-08-30 17:31       ` Kalle Valo
2017-08-30 17:54         ` David Miller
2017-08-31  4:44           ` Kalle Valo
2017-08-31  6:52             ` Pavel Machek
2017-08-31 11:50               ` Kalle Valo
2017-08-31 14:47                 ` [PATCH] wl1251: add a missing spin_lock_init() Pavel Machek
2017-08-31 17:33                   ` David Miller [this message]
2017-08-31 18:57                     ` Pavel Machek
2017-08-31 18:57                       ` Pavel Machek
2017-08-31 19:26                       ` David Miller
2017-08-31 19:59                         ` Pavel Machek
2017-08-31 20:10                           ` David Miller

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=20170831.103305.1809212990680774811.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@linux-foundation.org \
    --cc=xiyou.wangcong@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.