All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Aman Sharma <amanharitsh123@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/5] pci: handled return value of platform_get_irq correctly
Date: Wed, 11 Mar 2020 15:57:23 -0500	[thread overview]
Message-ID: <20200311205723.GA177532@google.com> (raw)
In-Reply-To: <d12a15f496ca472e100798ac2cd256fbfc1de15d.1583952276.git.amanharitsh123@gmail.com>

Hi Aman,

1) Check your mailer config.  These messages had no "To:" header, so
replying didn't work correctly.  I added "Cc: linux-pci" manually, but
on the mailing lists, the convention is to "reply-all" so everybody
can participate.

2) The cc list is a little bit overboard.
"$ ./scripts/get_maintainer.pl -f drivers/pci/controller/pci-v3-semi.c"
shows Linus W, Lorenzo, Andrew, myself, linux-pci, linux-kernel.
That's plenty.

3) Study "git log drivers/pci" and make your commit subjects and
logs match the convention in capitalization, sentence structure, verb
tense, etc.

4) Every commit must have non-empty log, even if the commit seems
trivial.  The log message should be independent of the subject.  The
subject is like an essay title; the log message is like the essay
body.  The body is separate from the title, not a continuation of it.

5) Function names in subjects and logs have "()" after them.

6) Cite previous similar work, e.g., mention ef75369a5b9a ("PCI:
altera: Fix platform_get_irq() error handling"), which is one of many
similar patches.

7) You mentioned similar issues with platform_get_irq_byname().
Please add patches in this series to fix them as well.

8) You asked about dev_err() usage.  See 6c9050a73469 ("irqchip:
Remove dev_err() usage after platform_get_irq()") and feel free to do
the same here.  If you do, cite that commit in your commit log.

I think the patches themselves look OK, and the series is correctly
structured with a cover letter and patches as responses to the cover.

When you post a revised series, make sure it's labeled "PATCH v2 0/5".

Thanks,
  Bjorn

On Thu, Mar 12, 2020 at 12:49:02AM +0530, Aman Sharma wrote:
> Signed-off-by: Aman Sharma <amanharitsh123@gmail.com>
> ---
>  drivers/pci/controller/pci-v3-semi.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/pci/controller/pci-v3-semi.c b/drivers/pci/controller/pci-v3-semi.c
> index bd05221f5a22..a5bf945d2eda 100644
> --- a/drivers/pci/controller/pci-v3-semi.c
> +++ b/drivers/pci/controller/pci-v3-semi.c
> @@ -777,9 +777,9 @@ static int v3_pci_probe(struct platform_device *pdev)
>  
>  	/* Get and request error IRQ resource */
>  	irq = platform_get_irq(pdev, 0);
> -	if (irq <= 0) {
> +	if (irq < 0) {
>  		dev_err(dev, "unable to obtain PCIv3 error IRQ\n");
> -		return -ENODEV;
> +		return irq;
>  	}
>  	ret = devm_request_irq(dev, irq, v3_irq, 0,
>  			"PCIv3 error", v3);
> -- 
> 2.20.1
> 

  reply	other threads:[~2020-03-11 20:57 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 19:19 [PATCH 0/5] Handled return value of platform_get_irq correctly Aman Sharma
2020-03-11 19:19 ` Aman Sharma
2020-03-11 19:19 ` Aman Sharma
2020-03-11 19:19 ` [PATCH 1/5] pci: handled " Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 20:57   ` Bjorn Helgaas [this message]
2020-04-06 21:28     ` Bjorn Helgaas
2020-03-12 14:07   ` Linus Walleij
2020-03-12 14:07     ` Linus Walleij
2020-03-12 14:07     ` Linus Walleij
2020-03-12 19:02     ` Bjorn Helgaas
2020-03-12 19:02       ` Bjorn Helgaas
2020-03-12 19:02       ` Bjorn Helgaas
2020-03-12 22:45       ` Linus Walleij
2020-03-12 22:45         ` Linus Walleij
2020-03-12 22:45         ` Linus Walleij
2020-03-11 19:19 ` [PATCH 2/5] pci: added check for return value of platform_get_irq Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19 ` [PATCH 3/5] pci: handled return value of platform_get_irq correctly Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19 ` [PATCH 4/5] " Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-12  9:53   ` Marc Gonzalez
2020-03-12  9:53     ` Marc Gonzalez
2020-03-12  9:53     ` Marc Gonzalez
2020-03-12 14:11     ` Bjorn Helgaas
2020-03-12 14:11       ` Bjorn Helgaas
2020-03-12 14:11       ` Bjorn Helgaas
2020-03-12 15:53       ` Marc Gonzalez
2020-03-12 15:53         ` Marc Gonzalez
2020-03-12 15:53         ` Marc Gonzalez
2020-03-13 21:05       ` Thomas Gleixner
2020-03-13 21:05         ` Thomas Gleixner
2020-03-13 21:05         ` Thomas Gleixner
2020-03-13 21:56         ` Bjorn Helgaas
2020-03-13 21:56           ` Bjorn Helgaas
2020-03-13 21:56           ` Bjorn Helgaas
2020-03-17 22:03           ` Bjorn Helgaas
2020-03-17 22:03             ` Bjorn Helgaas
2020-03-17 22:03             ` Bjorn Helgaas
2020-03-18 13:42             ` Thomas Gleixner
2020-03-18 13:42               ` Thomas Gleixner
2020-03-18 13:42               ` Thomas Gleixner
2020-03-18 22:22               ` Bjorn Helgaas
2020-03-18 22:22                 ` Bjorn Helgaas
2020-03-18 22:22                 ` Bjorn Helgaas
2020-03-19  8:47                 ` Thomas Gleixner
2020-03-19  8:47                   ` Thomas Gleixner
2020-03-19  8:47                   ` Thomas Gleixner
2020-03-19 21:35                   ` Bjorn Helgaas
2020-03-19 21:35                     ` Bjorn Helgaas
2020-03-19 21:35                     ` Bjorn Helgaas
2020-03-11 19:19 ` [PATCH 5/5] pci: added check for return value of platform_get_irq Aman Sharma
2020-03-11 19:19   ` Aman Sharma
2020-03-11 19:19   ` Aman Sharma

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=20200311205723.GA177532@google.com \
    --to=helgaas@kernel.org \
    --cc=amanharitsh123@gmail.com \
    --cc=linux-pci@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 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.