All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Milo Kim <milo.kim@ti.com>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] mfd: lp8788-irq: uninitialized variable in irq handler
Date: Mon, 21 Mar 2016 18:50:13 +0000	[thread overview]
Message-ID: <20160321185012.GJ4140@x1> (raw)
In-Reply-To: <20160321123013.GW5273@mwanda>

On Mon, 21 Mar 2016, Dan Carpenter wrote:

> Gar, the truth is I'm never going to remember to capitalize patches for
> you.  No one else has that rule.  Plus the last two times we had this

It's an awesome rule.  Everyone should have that rule. ;)

> discussion the patches I was fixing were not capitalized either.
> 
> git log -p --author="Dan Carpenter" drivers/mfd | grep Fixes | head
> -n 2

Not sure what you think the output of this command is meant to show,
but I get this: 

$ git log -p --author="Dan Carpenter" drivers/mfd | grep Fixes | head -n 2
    Fixes: c013f0a56c56 ('mfd: Add pm8xxx irq support')

... which seems to go against your statement.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Milo Kim <milo.kim@ti.com>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] mfd: lp8788-irq: uninitialized variable in irq handler
Date: Mon, 21 Mar 2016 18:50:13 +0000	[thread overview]
Message-ID: <20160321185012.GJ4140@x1> (raw)
In-Reply-To: <20160321123013.GW5273@mwanda>

On Mon, 21 Mar 2016, Dan Carpenter wrote:

> Gar, the truth is I'm never going to remember to capitalize patches for
> you.  No one else has that rule.  Plus the last two times we had this

It's an awesome rule.  Everyone should have that rule. ;)

> discussion the patches I was fixing were not capitalized either.
> 
> git log -p --author="Dan Carpenter" drivers/mfd | grep Fixes | head
> -n 2

Not sure what you think the output of this command is meant to show,
but I get this: 

$ git log -p --author="Dan Carpenter" drivers/mfd | grep Fixes | head -n 2
    Fixes: c013f0a56c56 ('mfd: Add pm8xxx irq support')

... which seems to go against your statement.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2016-03-21 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  8:11 [patch] mfd: lp8788-irq: uninitialized variable in irq handler Dan Carpenter
2016-03-11  8:11 ` Dan Carpenter
2016-03-13 23:08 ` Kim, Milo
2016-03-13 23:08   ` Kim, Milo
2016-03-21 11:54 ` Lee Jones
2016-03-21 11:54   ` Lee Jones
2016-03-21 12:30   ` Dan Carpenter
2016-03-21 12:30     ` Dan Carpenter
2016-03-21 18:50     ` Lee Jones [this message]
2016-03-21 18:50       ` Lee Jones

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=20160321185012.GJ4140@x1 \
    --to=lee.jones@linaro.org \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milo.kim@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.