linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Zac Storer <zac.3.14159@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 31/31] Drivers: pci: probe: fixed a brace coding style issue
Date: Mon, 5 Dec 2011 11:07:05 -0800	[thread overview]
Message-ID: <20111205110705.401d2a3d@jbarnes-desktop> (raw)
In-Reply-To: <1321596469-11180-1-git-send-email-zac.3.14159@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

On Thu, 17 Nov 2011 23:07:49 -0700
Zac Storer <zac.3.14159@gmail.com> wrote:

> Fixed a brace coding style issue.
> 
> Signed-off-by: Zac Storer <zac.3.14159@gmail.com>
> ---
>  drivers/pci/probe.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 04e74f4..d5d0ab8 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1534,7 +1534,7 @@ struct pci_bus * pci_create_bus(struct device *parent,
>  		return NULL;
>  
>  	dev = kzalloc(sizeof(*dev), GFP_KERNEL);
> -	if (!dev){
> +	if (!dev) {
>  		kfree(b);
>  		return NULL;
>  	}

Applied to linux-next, thanks.  Would be even better if you found a
32/31 with an actual bug fix in it though. :)

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2011-12-05 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18  6:07 [PATCH 31/31] Drivers: pci: probe: fixed a brace coding style issue Zac Storer
2011-12-05 19:07 ` Jesse Barnes [this message]

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=20111205110705.401d2a3d@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=zac.3.14159@gmail.com \
    /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).