From: Greg KH <greg@kroah.com>
To: Jason Baron <jbaron@redhat.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
joe@perches.com, nick@nick-andrew.net
Subject: Re: [PATCH 1/7] dynamic debug v2 - infrastructure
Date: Tue, 12 Aug 2008 13:09:08 -0700 [thread overview]
Message-ID: <20080812200908.GA444@kroah.com> (raw)
In-Reply-To: <20080812194817.GD6056@redhat.com>
On Tue, Aug 12, 2008 at 03:48:17PM -0400, Jason Baron wrote:
> On Mon, Aug 11, 2008 at 03:33:09PM -0700, Greg KH wrote:
> > On Mon, Aug 11, 2008 at 01:36:16PM -0400, Jason Baron wrote:
> > > On Fri, Aug 08, 2008 at 07:38:51PM -0700, Randy Dunlap wrote:
> > > > On Fri, 8 Aug 2008 17:51:53 -0400 Jason Baron wrote:
> > > >
> > > > > Few notes...there is still one control file: <debugfs>/dynamic_printk/modules
> > > > > We can split this up now or later, but I kind of like being able to see all
> > > > > the controls in one file. Also, i've used a djb2 hash function in the code,
> > > > > which i'm not sure is under the correct license/copyright, so i just wanted
> > > > > to point that out as well. see: scripts/basic/hash.c. If its an issue, i can
> > > > > find another hash function.
> > > >
> > > > What license does it have? I don't see one.
> > > >
> > >
> > > hmmm...a search for djb2 finds a number of users, for example, i found this one
> > > which is covered by GPL2, http://www.telegraphics.com.au/svn/dpa/trunk/symtab.c
> > > is that sufficient to say its ok?
> >
> > That's a tough call. I'd run that through the license board of your
> > employer if you have any questions about this, as it is your name with
> > their domain that is going to have the "signed-off-by:" pointing back
> > to.
> >
>
> We're ok with the patch as is...i'm including an updated version below, which
> contains some documentation improvements...as you mentioned before, perhaps
> you can include this patch through the driver tree. It should apply with
> minimal munging, but please point me at a tree, if there are any issues.
>
> thanks,
>
> -Jason
>
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
So close, can I have a good changelog comment with the patch so people
know what it is when they look in the logs?
Care to resend it with that?
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-12 20:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 21:31 [PATCH 1/7] dynamic debug v2 - infrastructure Jason Baron
2008-07-17 7:01 ` Greg KH
2008-07-17 21:20 ` Jason Baron
2008-07-17 22:32 ` Greg KH
2008-07-17 22:56 ` Dominik Brodowski
2008-07-17 23:35 ` Greg KH
2008-07-18 6:37 ` Dominik Brodowski
2008-07-18 14:39 ` Jason Baron
2008-08-08 21:51 ` Jason Baron
2008-08-09 1:07 ` Greg KH
2008-08-11 14:12 ` Jason Baron
2008-08-11 16:45 ` Greg KH
2008-08-09 2:38 ` Randy Dunlap
2008-08-11 17:36 ` Jason Baron
2008-08-11 22:33 ` Greg KH
2008-08-12 19:48 ` Jason Baron
2008-08-12 20:09 ` Greg KH [this message]
2008-08-12 20:46 ` Jason Baron
2008-08-13 1:08 ` Greg KH
2008-08-13 1:16 ` Andrew Morton
2008-08-13 3:38 ` Greg KH
2008-08-13 20:00 ` Sam Ravnborg
2008-08-13 22:49 ` jbaron
2008-08-13 23:54 ` Greg KH
2008-08-14 1:25 ` Greg KH
2008-08-13 19:05 ` Jason Baron
2008-08-14 14:53 ` Greg KH
2008-08-14 21:05 ` Jason Baron
2008-09-16 0:03 ` Rusty Russell
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=20080812200908.GA444@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=jbaron@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--cc=randy.dunlap@oracle.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