From: Randy Dunlap <rdunlap@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] serial: imx: Fix build breakage
Date: Fri, 11 Jul 2014 19:39:50 -0700 [thread overview]
Message-ID: <53C09FF6.8020507@infradead.org> (raw)
In-Reply-To: <20140712021635.GB17548@kroah.com>
On 07/11/14 19:16, Greg Kroah-Hartman wrote:
> On Fri, Jul 11, 2014 at 07:00:48PM -0700, Randy Dunlap wrote:
>> On 07/11/14 17:42, Greg Kroah-Hartman wrote:
>>> On Thu, Jul 10, 2014 at 10:36:46PM -0400, Peter Hurley wrote:
>>>> Fix breakage introduced by
>>>> commit c557d392fbf5badd693ea1946a4317c87a26a716,
>>>> 'serial: Test for no tx data on tx restart'.
>>>>
>>>> Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
>>>
>>> You forgot a "Reported-by:" tag.
>>>
>>> I'll go add it...
>>
>> It's not clear to me that Peter forgot it.
>
> Why? Stephen pointed out the problem, in a public place, so I gave him
> credit for it.
SubmittingPatches does not give you permission to do that,
but Stephen just did so.
--
~Randy
next prev parent reply other threads:[~2014-07-12 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 1:21 linux-next: build failure after merge of the tty.current tree Stephen Rothwell
2014-07-11 2:36 ` [PATCH] serial: imx: Fix build breakage Peter Hurley
2014-07-12 0:42 ` Greg Kroah-Hartman
2014-07-12 2:00 ` Randy Dunlap
2014-07-12 2:09 ` Stephen Rothwell
2014-07-12 2:16 ` Greg Kroah-Hartman
2014-07-12 2:39 ` Randy Dunlap [this message]
2014-07-12 13:11 ` Peter Hurley
2014-07-11 15:06 ` linux-next: build failure after merge of the tty.current tree Peter Hurley
2014-07-12 1:20 ` Stephen Rothwell
2014-07-12 13:02 ` Peter Hurley
2014-07-15 17:49 ` Peter Hurley
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=53C09FF6.8020507@infradead.org \
--to=rdunlap@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=sfr@canb.auug.org.au \
/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).