linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:25:13 +0200	[thread overview]
Message-ID: <wrfjtx8mrrp2.fsf@ultrasam.lan.trained-monkey.org> (raw)
In-Reply-To: <20140519101855.GU15585@mwanda> (Dan Carpenter's message of "Mon, 19 May 2014 13:18:56 +0300")

Dan Carpenter <dan.carpenter@oracle.com> writes:
> On Sun, May 18, 2014 at 07:39:23AM +0100, Karim Raslan wrote:
>> This should fix a few sparse warnings like the following:
>> 
>>   CHECK   drivers/staging/rtl8723au/core/rtw_ap.c
>> drivers/staging/rtl8723au/core/rtw_ap.c:1054:45: warning: incorrect
>> type in argument 3 (different base types)
>> drivers/staging/rtl8723au/core/rtw_ap.c:1054:45:    expected int [signed] gfp
>> drivers/staging/rtl8723au/core/rtw_ap.c:1054:45:    got restricted gfp_t
>> 
>
> Thanks, Karim, looks good.
>
> Jes's patch which added this never went to the list so I didn't review
> it.  This annoys me.
>
> I try to be fair when I review code.  I try to allow lots of patches in
> and let people send fix up patches for minor stuff.  But, obviously, you
> should be running Sparse as part of the review process so if I made you
> redo this patch it's because your process is broken.  When I review
> patches I am trying to help you.

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.

This particular case isn't exactly a real problem either.

Jes

  reply	other threads:[~2014-05-19 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-18  6:39 [PATCH] staging: rtl8723au: rtw_sta_mgt: change rtw_alloc_stainfo23a to use gfp_t instead if int Karim Raslan
2014-05-19 10:18 ` Dan Carpenter
2014-05-19 10:25   ` Jes Sorensen [this message]
2014-05-19 10:40     ` Dan Carpenter
2014-05-19 10:49       ` Jes Sorensen
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=wrfjtx8mrrp2.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;
as well as URLs for NNTP newsgroup(s).