All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Rabin Vincent <rabin.vincent-VrBV9hrLPhE@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: pl022: don't use uninitialized variable
Date: Thu, 6 Apr 2017 19:12:16 +0100	[thread overview]
Message-ID: <20170406181216.m4rke6smv2bajdqv@sirena.org.uk> (raw)
In-Reply-To: <20170406113924.GA7801-VrBV9hrLPhE@public.gmane.org>

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

On Thu, Apr 06, 2017 at 01:39:24PM +0200, Rabin Vincent wrote:

> Yes, I could add something like:

>  By setting the default value to zero, we ensure that the probe fails if
>  the num-cs property is missing.

> But I noticed that you already applied this and your automated email says:

>  If any updates are required or you are submitting further changes they should
>  be sent as incremental updates against current git, existing patches will not
>  be replaced.

> So I guess it's too late to submit a new changelog?

Yes, this is more for future reference - I already did the checking to
figure out that this does the right thing.

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

  parent reply	other threads:[~2017-04-06 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:16 [PATCH] spi: pl022: don't use uninitialized variable Rabin Vincent
     [not found] ` <1491466583-6121-1-git-send-email-rabin.vincent-VrBV9hrLPhE@public.gmane.org>
2017-04-06 10:55   ` Mark Brown
     [not found]     ` <20170406105502.baaj4c2xcetp5z6p-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-04-06 11:39       ` Rabin Vincent
     [not found]         ` <20170406113924.GA7801-VrBV9hrLPhE@public.gmane.org>
2017-04-06 18:12           ` Mark Brown [this message]
2017-04-06 10:58   ` Applied "spi: pl022: don't use uninitialized variable" to the spi tree Mark Brown

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=20170406181216.m4rke6smv2bajdqv@sirena.org.uk \
    --to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rabin.vincent-VrBV9hrLPhE@public.gmane.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.