All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] firmware: socfpga: Add necessary dependency to Kconfig
Date: Wed, 15 Apr 2015 07:16:48 +0200	[thread overview]
Message-ID: <20150415051648.GI9742@pengutronix.de> (raw)
In-Reply-To: <CAHQ1cqFU1waM3z8D1ZKDb3zqPyP2GtYAovZo-RZ9Ag2=sCywow@mail.gmail.com>

On Tue, Apr 14, 2015 at 12:47:46PM -0700, Andrey Smirnov wrote:
> On Tue, Apr 14, 2015 at 11:39 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Mon, Apr 13, 2015 at 05:11:30AM -0700, Andrey Smirnov wrote:
> >> ---
> >>  drivers/firmware/Kconfig | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > This patch lacks a signed-off-by. Could you resend it?
> 
> I figured tat since this was just a one line in a build configuration
> file it would be too trivial for copyright assignment, but I can add
> the signed-off-by line in the next version of the patch.

Indeed it's trivial and nobody will doubt this was your work, but where
should I draw the line? Always insisting on the signed-off-by helps us
not thinking about this topic anymore.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-04-15  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 12:11 [PATCH] firmware: socfpga: Add necessary dependency to Kconfig Andrey Smirnov
2015-04-14 18:39 ` Sascha Hauer
2015-04-14 19:47   ` Andrey Smirnov
2015-04-15  5:16     ` Sascha Hauer [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=20150415051648.GI9742@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.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.