linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/5] Fix set but unused variable warnings
Date: Wed, 16 Jun 2010 00:01:15 -0700	[thread overview]
Message-ID: <4C1876BB.9030807@gmail.com> (raw)
In-Reply-To: <AANLkTikwKHITQJDaSf9BnHQ9FLiQ-KYlCWNiH438otsV@mail.gmail.com>

On 06/15/2010 10:52 PM, Julian Calaby wrote:
> On Wed, Jun 16, 2010 at 15:33, Justin P. Mattock
> <justinmattock@gmail.com>  wrote:
>> Here is another set of patches fixing some warning messages generated
>> when building the kernel when using gcc 4.6.0.
>>
>> This set just focuses in on the variables warnings that are reported
>> to be unused. Keep in mind there are still lots more warning messages
>> that I'm seeing, and will try my hardest to see if I can come up with
>> a fix, but if things become too difficult and so forth then a bug should
>> be filled etc..
>
> Given that patches 3, 4 and 5 seem to be a cases of missing error
> handling, (3 and 4 in particular seem to be breaking things rather
> than fixing them) in my humble opinion, I think this set needs some
> work and discussion.
>

alright..

> Justin, maybe you'd be better off posting the actual error messages
> (split up by subsystem) and letting the lists discuss them, rather
> than posting patches which are obviously wrong. (like the ones I've
> pointed out)
>

yeah I'm a newbie!! alright so just file bugs for all these then.

> I'm sure that everyone here is as committed as you are to eliminating
> compile warnings and errors and, in my opinion, more good will come
> from a healthy discussion of the warnings than maintainers NAKing your
> patches out of hand.
>
> Thanks,
>


NAKing is o.k. but having discussions is better..

Justin P. Mattock

  reply	other threads:[~2010-06-16  7:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  5:33 [PATCH 0/5] Fix set but unused variable warnings Justin P. Mattock
2010-06-16  5:33 ` [PATCH 1/5]wireless:hostap_main.c warning: variable 'iface' set but not used Justin P. Mattock
2010-06-16  5:33 ` [PATCH 2/5]wireless:hostap_ap.c Fix warning: variable 'fc' " Justin P. Mattock
2010-06-16  5:33 ` [PATCH 3/5]pci:bus.c Fix variable 'retval' " Justin P. Mattock
2010-06-16  5:42   ` Julian Calaby
2010-06-16  6:56     ` Justin P. Mattock
2010-06-16  6:07   ` Junchang Wang
2010-06-16  6:58     ` Justin P. Mattock
2010-06-16 17:01     ` Justin P. Mattock
2010-06-17 17:15     ` Justin P. Mattock
2010-06-16  5:33 ` [PATCH 4/5]pci:setup_bus.c Fix warning: " Justin P. Mattock
2010-06-18 17:23   ` Jesse Barnes
2010-06-18 17:31     ` Justin P. Mattock
2010-06-18 18:38     ` Justin P. Mattock
2010-06-18 18:48     ` Yinghai Lu
2010-06-18 19:49       ` Jesse Barnes
2010-06-18 19:59         ` Justin P. Mattock
2010-06-18 20:05           ` Jesse Barnes
2010-06-18 20:26             ` Justin P. Mattock
2010-06-18 20:46               ` Jesse Barnes
2010-06-18 21:12                 ` Justin P. Mattock
2010-06-16  5:33 ` [PATCH 5/5]scsi:hosts.c Fix warning: variable 'rval' " Justin P. Mattock
2010-06-16 15:34   ` James Bottomley
2010-06-16 16:00     ` Justin P. Mattock
2010-06-16 17:25       ` Rolf Eike Beer
2010-06-16 17:33       ` James Bottomley
2010-06-16 18:14         ` Justin P. Mattock
2010-06-17 16:16         ` Justin P. Mattock
2010-06-18 19:37           ` James Bottomley
2010-06-18 19:55             ` Justin P. Mattock
2010-06-18 20:17             ` Justin P. Mattock
2010-06-16  5:52 ` [PATCH 0/5] Fix set but unused variable warnings Julian Calaby
2010-06-16  7:01   ` Justin P. Mattock [this message]
2010-06-16 11:09   ` Matthew Wilcox
2010-06-16 11:30     ` Julian Calaby

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=4C1876BB.9030807@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@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).