From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Karim Raslan <karim.allah.ahmed@gmail.com>,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] staging: rtl8723au: rtw_sta_mgt: change rtw_alloc_stainfo23a to use gfp_t instead if int
Date: Mon, 19 May 2014 12:49:03 +0200 [thread overview]
Message-ID: <wrfjlhtyrqlc.fsf@ultrasam.lan.trained-monkey.org> (raw)
In-Reply-To: <20140519104012.GP16255@mwanda> (Dan Carpenter's message of "Mon, 19 May 2014 13:40:12 +0300")
Dan Carpenter <dan.carpenter@oracle.com> writes:
> On Mon, May 19, 2014 at 12:25:13PM +0200, Jes Sorensen wrote:
>> Dan,
>>
>> Calm down, I haven't been bombarding the list, due to the sheer volume
>> of commits. If you want me to spam the list, tell me where and I'll add
>> that to the CC list next time.
>
> We provide the scripts/get_maintainer.pl script for that. You can leave
> linux-kernel off if you want because they don't care about staging
> drivers. The staging list is devel@driverdev.osuosl.org.
You should be running your tools against the staging tree automatically,
that way you catch it before it hits the mainline tree.
Just flooding mailing lists for the sake of flooding them doesn't add
any value either.
Jes
next prev parent reply other threads:[~2014-05-19 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 6:39 Karim Raslan
2014-05-19 10:18 ` Dan Carpenter
2014-05-19 10:25 ` Jes Sorensen
2014-05-19 10:40 ` Dan Carpenter
2014-05-19 10:49 ` Jes Sorensen [this message]
2014-05-19 11:40 ` Dan Carpenter
2014-05-19 13:10 ` Jes Sorensen
2014-05-19 14:05 ` Dan Carpenter
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=wrfjlhtyrqlc.fsf@ultrasam.lan.trained-monkey.org \
--to=jes.sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=karim.allah.ahmed@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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®