linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: christopher.lee.bostic@gmail.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
	mturquette@baylibre.com, geert+renesas@glider.be,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	joel@jms.id.au, jk@ozlabs.org, linux-kernel@vger.kernel.org,
	andrew@aj.id.au, alistair@popple.id.au, benh@kernel.crashing.org,
	Chris Bostic <cbostic@us.ibm.com>
Subject: Re: [PATCH v2 18/18] insert build break
Date: Fri, 13 Jan 2017 08:15:45 +0100	[thread overview]
Message-ID: <20170113071545.GB12441@kroah.com> (raw)
In-Reply-To: <1484260655-80477-1-git-send-email-christopher.lee.bostic@gmail.com>

On Thu, Jan 12, 2017 at 04:37:35PM -0600, christopher.lee.bostic@gmail.com wrote:
> From: Chris Bostic <cbostic@us.ibm.com>
> 
> Signed-off-by: Chris Bostic <cbostic@us.ibm.com>

I can not accept patches that have no changelog text, and this one is
very odd:

> ---
>  drivers/fsi/fsi-core.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/fsi/fsi-core.c b/drivers/fsi/fsi-core.c
> index 28b82d1..db09836 100644
> --- a/drivers/fsi/fsi-core.c
> +++ b/drivers/fsi/fsi-core.c
> @@ -42,6 +42,7 @@
>  
>  static DEFINE_IDA(master_ida);
>  
> +

Huh?

Did something go wrong with your scripts?

greg k-h

  reply	other threads:[~2017-01-13  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 22:37 [PATCH v2 18/18] insert build break christopher.lee.bostic
2017-01-13  7:15 ` Greg KH [this message]
2017-01-13 14:22   ` Christopher Bostic
2017-01-18 22:06   ` Rob Herring

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=20170113071545.GB12441@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alistair@popple.id.au \
    --cc=andrew@aj.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=cbostic@us.ibm.com \
    --cc=christopher.lee.bostic@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@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 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).