From: Johannes Berg <johannes@sipsolutions.net>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
trivial@kernel.org, davem@davemloft.net,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/21]include:net:mac80211.h remove one to many l's in the word.
Date: Fri, 25 Feb 2011 09:55:08 +0100 [thread overview]
Message-ID: <1298624108.4329.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <C0CEB11E-CD60-4A10-BFC8-7CB555D1413C@gmail.com>
On Thu, 2011-02-24 at 23:10 -0800, Justin Mattock wrote:
[please trim your quotes]
> yeah.. I agree, its just people have said that I should individually
> send each patch to each maintainer subsystem etc...
> (rather would just send one with everything on it, but then might make
> things more confusing)
I for one trust Jiri, and don't even need to see patches like this.
Certainly not the entire "maintainer chain" and multiple mailing lists!
johannes
next prev parent reply other threads:[~2011-02-25 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 6:15 Justin P. Mattock
2011-02-25 6:20 ` Julian Calaby
2011-02-25 7:10 ` Justin Mattock
2011-02-25 8:55 ` Johannes Berg [this message]
2011-02-25 8:20 ` Jiri Kosina
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=1298624108.4329.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=julian.calaby@gmail.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®