All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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: Sat, 12 Jul 2014 09:11:26 -0400	[thread overview]
Message-ID: <53C133FE.7020603@hurleysoftware.com> (raw)
In-Reply-To: <53C096D0.3000005@infradead.org>

On 07/11/2014 10:00 PM, 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.

Yeah, it was an oversight. I was rushing to get the patch done because
I was embarrassed about breaking the build.

The kbuild test robot actually notified me first though :)

> Someone else brought this up -- it seems to me that
> Documentation/SubmittingPatches is a little too strong about needing
> permission to use Reported-by:
>
> If this patch fixes a problem reported by somebody else, consider adding a
> Reported-by: tag to credit the reporter for their contribution.  Please
> note that this tag should not be added without the reporter's permission,
> especially if the problem was not reported in a public forum.  That said,
> if we diligently credit our bug reporters, they will, hopefully, be
> inspired to help us again in the future.

I wish the Reported-by tag (and some others) was picked up by git send-email
automatically.

> Sure, if a problem was reported privately, then we need to have permission
> to use Reported-by, but if it was reported in a public forum, that should be
> implicit permission (IMHO).
>
> eh?

I agree.

Regards,
Peter Hurley

  parent reply	other threads:[~2014-07-12 13:11 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
2014-07-12 13:11       ` Peter Hurley [this message]
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=53C133FE.7020603@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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 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.