public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Sinan Kaya <okaya@codeaurora.org>,
	Christopher Covington <cov@codeaurora.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Timur Tabi <timur@codeaurora.org>,
	jcm@redhat.com, helgaas@kernel.org, Len Brown <lenb@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V9 1/2] ACPI, PCI, irq: remove interrupt count restriction
Date: Fri, 01 Jan 2016 01:48:40 +0100	[thread overview]
Message-ID: <6338540.F7x0ET9vtV@vostro.rjw.lan> (raw)
In-Reply-To: <CAHp75VePLCAP8L3ve4F4745Nnes+kYa5QHHKQos4=0iHw0Ah0Q@mail.gmail.com>

On Wednesday, December 30, 2015 09:55:35 PM Andy Shevchenko wrote:
> On Wed, Dec 30, 2015 at 9:17 PM, Sinan Kaya <okaya@codeaurora.org> wrote:
> > On 12/30/2015 8:28 AM, Andy Shevchenko wrote:
> >> Yep, I meant not to use an additional variable.
> >>
> >>> > BTW, I suggest you spend some time around checkpatch for contributions. I could
> >>> > have caught most of the issues you are generally concerned before submitting a patch.
> >> Is it a question?
> >
> > It is a request not a question. I hate wasting your time and my time with things that I could
> > have fixed before submitting a patch.
> >
> > I ran the checkpatch and it said I'm good to go. But, obviously I'm not.
> 
> Hmm… checkpatch.pl is just a small helper to fix style issues. Here is
> just a common sense rule, or kind of Occam's razor: no need to have
> more variables then needed if it doesn't improve something really
> significantly.

That said, compilers optimize things anyway, so using an extra local variable
shouldn't matter for the resulting machine code.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-01-01  0:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 16:18 [PATCH V9 0/2] ACPI, PCI, irq: remove interrupt limitations Sinan Kaya
2015-12-09 16:18 ` [PATCH V9 1/2] ACPI, PCI, irq: remove interrupt count restriction Sinan Kaya
2015-12-09 16:59   ` Andy Shevchenko
2015-12-09 17:09     ` Sinan Kaya
2015-12-09 17:14       ` Christopher Covington
2015-12-30 13:23         ` Sinan Kaya
2015-12-30 13:28           ` Andy Shevchenko
2015-12-30 19:17             ` Sinan Kaya
2015-12-30 19:55               ` Andy Shevchenko
2016-01-01  0:48                 ` Rafael J. Wysocki [this message]
2016-01-04  9:01                   ` Andy Shevchenko
2016-01-04 13:50                     ` Rafael J. Wysocki
2016-01-04 13:34                       ` Andy Shevchenko
2015-12-09 16:18 ` [PATCH V9 2/2] ACPI, PCI, irq: remove interrupt number restriction Sinan Kaya
2016-01-03  0:35 ` [PATCH V9 0/2] ACPI, PCI, irq: remove interrupt limitations Rafael J. Wysocki

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=6338540.F7x0ET9vtV@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=andy.shevchenko@gmail.com \
    --cc=cov@codeaurora.org \
    --cc=helgaas@kernel.org \
    --cc=jcm@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okaya@codeaurora.org \
    --cc=timur@codeaurora.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