From: Rob Herring <robh+dt@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>,
kbuild test robot <fengguang.wu@intel.com>
Cc: christopher.lee.bostic@gmail.com,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Michael Turquette <mturquette@baylibre.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Joel Stanley <joel@jms.id.au>, Jeremy Kerr <jk@ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>,
Alistair Popple <alistair@popple.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Chris Bostic <cbostic@us.ibm.com>
Subject: Re: [PATCH v2 18/18] insert build break
Date: Wed, 18 Jan 2017 16:06:05 -0600 [thread overview]
Message-ID: <CAL_JsqL-yQD=oFQW0YfB9JnSpDVcOcUG0GM8NgLCB1nsFQsrEQ@mail.gmail.com> (raw)
In-Reply-To: <20170113071545.GB12441@kroah.com>
On Fri, Jan 13, 2017 at 1:15 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> 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:
Seems like this would be an easy check to add to 0-day. And perhaps
missing S-o-B, too.
Rob
prev parent reply other threads:[~2017-01-18 22:08 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
2017-01-13 14:22 ` Christopher Bostic
2017-01-18 22:06 ` Rob Herring [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='CAL_JsqL-yQD=oFQW0YfB9JnSpDVcOcUG0GM8NgLCB1nsFQsrEQ@mail.gmail.com' \
--to=robh+dt@kernel.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=fengguang.wu@intel.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--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 \
/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).