From: Mark Brown <broonie@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Baolin Wang <baolin.wang@linaro.org>,
Felipe Balbi <balbi@kernel.org>,
Badhri Jagan Sridharan <Badhri@google.com>,
USB <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: gadget: Add uevent to notify userspace
Date: Thu, 22 Sep 2016 17:36:26 +0100 [thread overview]
Message-ID: <20160922163626.GO7994@sirena.org.uk> (raw)
In-Reply-To: <20160922133830.GA20931@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Thu, Sep 22, 2016 at 03:38:30PM +0200, Greg KH wrote:
> On Thu, Sep 22, 2016 at 08:41:09PM +0800, Baolin Wang wrote:
> > OK. I will talk with Badhri if I can upstream these.
> That's not an issue, you can keep the "From:" line on it, if you got it
> in a legal way, and then just have your signed off by on it, go read the
> DCO for the specifics. I don't know why someone else told you
> otherwise.
Given the weakness people have in understanding the legal part of
signoffs it seems very unwise to just trust that they've actually
got everything clearly lined up and IME when they're missing they've
often just been removed or sometimes there's a very good reason why the
original author didn't provide a signoff. It seems safer for everyone
to query what's going on and it's been fairly unusual that it's anything
other than a mistake.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-22 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 11:43 Baolin Wang
2016-09-22 12:23 ` Greg KH
2016-09-22 12:41 ` Baolin Wang
2016-09-22 12:53 ` Felipe Balbi
2016-09-23 2:17 ` Baolin Wang
2016-09-22 13:38 ` Greg KH
2016-09-22 16:36 ` Mark Brown [this message]
2016-09-22 20:50 ` Badhri Jagan Sridharan
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=20160922163626.GO7994@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Badhri@google.com \
--cc=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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
all inboxes | Powered by JetHome®