All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
	"Zhou, Jingting" <zhoujt@ti.com>
Subject: Re: [PATCH] added mounting debugfs recipe
Date: Fri, 3 May 2013 13:26:22 -0400	[thread overview]
Message-ID: <20130503172621.GI9213@edge> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED101595346E5@DLEE11.ent.ti.com>

On Fri, May 03, 2013 at 04:22:59PM +0000, Maupin, Chase wrote:
> > Hey Chase, thanks for the comments. Here's the patch.
> > 
> > From a1684ac257292855c03e58f3fee60232ed039b81 Mon Sep 17 00:00:00
> > 2001
> > From: Jingting Zhou <a0221004@ares-ubuntu>

^^^^


> > Date: Fri, 3 May 2013 11:56:05 -0400
> > Subject: [PATCH] using inherit update-rc.d in the initscript-
> > debugfs recipe
> 
> 
> You need to use a proper commit message here.  See 
> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

Correct. Also make sure your From line is valid. Please configure your git 
properly - git-config.


> This should probably be squashed with the commit that adds the recipe

Heh, and this time it's a patch over patch on top of a patch... :) Don't do 
this, send a version 3 of the original patch.


> > diff --git a/meta-arago-extras/recipes-bsp/initscript-
> > debugfs/initscript-debugfs.bb b/meta-arago-extras/recipes-
> > bsp/initscript-debugfs/initscript-debugfs.bb
> > index eaf316a..0137214 100755
> > --- a/meta-arago-extras/recipes-bsp/initscript-
> > debugfs/initscript-debugfs.bb
> > +++ b/meta-arago-extras/recipes-bsp/initscript-
> > debugfs/initscript-debugfs.bb
> > @@ -1,18 +1,20 @@
> >  DESCRIPTION = "Initscripts for debugfs"
> >  LICENSE = "BSD"
> > 
> > -LIC_FILES_CHKSUM =
> > "file://LICENSE;md5=3c1998754d846b48ba935ea0b7ada19a"
> > +LIC_FILES_CHKSUM =
> > "file://debugfs.sh;md5=a530203f3f8bf332686f4abf1e434e21"
> 
> Do your checksum of only the license lines.  This prevents a script change 
> from changing your license checksum.  Like 
> meta-ti/recipes-connectivity/uim/uim_git.bb.  Notice the startline and end 
> line fields.

I'd suggest initscript-telnetd here again :)


> >  PR ="r0"
> > 
> > -SRC_URI = "file://debugfs.sh \
> > -		   file://LICENSE"
> > +SRC_URI = "file://debugfs.sh"
> > +
> > +INITSCRIPT_NAME = "debugfs.sh"
> > +INITSCRIPT_PARAMS = "defaults 10"
> > +
> > +inherit update-rc.d
> > 
> >  S = "${WORKDIR}"
> > 
> >  do_install () {
> > -	install -d ${D}${sysconfdir}/init.d/
> > -	install -d ${D}${sysconfdir}/rcS.d/
> > -	install -c -m 755 ${WORKDIR}/debugfs.sh
> > ${D}${sysconfdir}/init.d/debugfs.sh
> > -	ln -sf ../init.d/debugfs.sh
> > ${D}${sysconfdir}/rcS.d/S09debugfs
> > +	install -d ${D}${sysconfdir}/init.d/
> > +	install -c -m 755 ${WORKDIR}/debugfs.sh
> > ${D}${sysconfdir}/init.d/debugfs.sh
> 
> Just a nitpick but there is no need to specify debugfs.sh in the destination 
> path.  Also, most init scripts don't bother with the .sh extension.  BTW, 
> using "defaults" for update-rc.d will put this script in run levels 2345.  
> If you want it in rcS then you need to change your INITSCRIPT_PARAMS 
> setting.  Do a man of update-rc.d to find out how that utility works.

Learning on update-rc.d in general is beneficial for you and your future 
recipes, so you may want to allocate some "training" time for that.

And for now the quickest approach would be to just copy the usage from 
initscript-telnetd - it is after all a very similar initscript...

-- 
Denys


  reply	other threads:[~2013-05-03 17:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 18:36 [PATCH] added mounting debugfs recipe zhoujt
2013-05-02 19:54 ` Maupin, Chase
2013-05-02 21:33   ` Zhou, Jingting
2013-05-03 11:54     ` Maupin, Chase
2013-05-03 15:58       ` Zhou, Jingting
2013-05-03 16:22         ` Maupin, Chase
2013-05-03 17:26           ` Denys Dmytriyenko [this message]
2013-05-03 17:16       ` Denys Dmytriyenko
2013-05-03 16:48     ` Denys Dmytriyenko
2013-05-03 16:43   ` Denys Dmytriyenko

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=20130503172621.GI9213@edge \
    --to=denys@ti.com \
    --cc=chase.maupin@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=zhoujt@ti.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 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.