All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Khan, Sabeeh" <sabeeh-khan@ti.com>
Cc: meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [RFC][master/scarthgap][PATCH 4/4] cc33xx-target-scripts: add cc33xx scripts to control TI cc33xx WLAN device
Date: Thu, 20 Jun 2024 21:17:52 -0400	[thread overview]
Message-ID: <20240621011752.GG18231@denix.org> (raw)
In-Reply-To: <224a7234-e455-44a1-971d-326761968609@ti.com>

On Thu, Jun 20, 2024 at 03:37:12PM -0500, Khan, Sabeeh wrote:
> 
> On 6/20/2024 3:27 PM, Denys Dmytriyenko wrote:
> >On Wed, Jun 19, 2024 at 10:22:02PM -0500, Sabeeh Khan via lists.yoctoproject.org wrote:
> >>[...]
> >>
> >>diff --git a/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb b/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> >>new file mode 100644
> >>index 00000000..2f13f911
> >>--- /dev/null
> >>+++ b/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> >>@@ -0,0 +1,22 @@
> >>+DESCRIPTION = "Scripts and configuration files for TI cc33xx wireless drivers"
> >SUMMARY
> 
> Apologies for not being familiar, but are you suggesting here
> 
> to have "SUMMARY" variable instead of "DESCRIPTION", or in addition to?
> 
> Can I please have some more context over the ask here?
> 
> I don't see "SUMMARY" variable in other meta-ti recipes, so I'm
> looking for a reference.

https://docs.yoctoproject.org/ref-manual/variables.html#term-SUMMARY
https://docs.yoctoproject.org/ref-manual/variables.html#term-DESCRIPTION

SUMMARY is a shorter version of the package description (one-line under 72 
characters), while DESCRIPTION can be a longer multi-line description.

DESCRIPTION can be omitted and will be derived from SUMMARY, but not the other 
way around.

In the very old days only the DESCRIPTION was used, hence old recipes still 
don't set SUMMARY, but newly added recipes should not do that.

Here's one of the many recipes in meta-ti that properly uses/sets both:
https://git.yoctoproject.org/meta-ti/tree/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc


> >>[...]
> >>+
> >>+do_install() {
> >>+	install -d ${D}${datadir}/cc33xx/
> >>+
> >>+	scripts=`find ./* -type f -name "*.*"`
> >Is this find command necessary?
> 
> The recipe should install .sh and .conf files from the git repo only.
> 
> This was done to ignore any README or license files and not have
> them installed.

I believe you can use globs directly with install, unless there's a 
directory hierarchy:

install -m 0755 *.* ${D}${datadir}/cc33xx/

-- 
Denys


  reply	other threads:[~2024-06-21  1:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  3:21 [RFC][master/scarthgap][PATCH 0/4] add FW and utilities for cc33xx wireless driver Sabeeh Khan
2024-06-20  3:21 ` [RFC][master/scarthgap][PATCH 1/4] cc33conf: add new cc33conf tool for cc33xx devices Sabeeh Khan
2024-06-20 20:20   ` [meta-ti] " Denys Dmytriyenko
2024-06-20 20:40     ` Khan, Sabeeh
2024-06-24 20:21       ` Denys Dmytriyenko
2024-06-24 21:19         ` Khan, Sabeeh
2024-06-20  3:22 ` [RFC][master/scarthgap][PATCH 2/4] cc33calibrator: add new cc33calibrator " Sabeeh Khan
2024-06-20 20:22   ` [meta-ti] " Denys Dmytriyenko
2024-06-20  3:22 ` [RFC][master/scarthgap][PATCH 3/4] cc33xx-fw: install cc33xx firmware Sabeeh Khan
2024-06-20 16:33   ` [meta-ti] " Ryan Eatmon
2024-06-20 16:52     ` Khan, Sabeeh
2024-06-20 18:35   ` Denys Dmytriyenko
2024-06-20 18:39     ` Khan, Sabeeh
2024-06-20  3:22 ` [RFC][master/scarthgap][PATCH 4/4] cc33xx-target-scripts: add cc33xx scripts to control TI cc33xx WLAN device Sabeeh Khan
2024-06-20 20:27   ` [meta-ti] " Denys Dmytriyenko
2024-06-20 20:37     ` Khan, Sabeeh
2024-06-21  1:17       ` Denys Dmytriyenko [this message]
2024-06-21  1:24         ` Khan, Sabeeh
2024-06-20  3:26 ` [RFC][master/scarthgap][PATCH 0/4] add FW and utilities for cc33xx wireless driver Sabeeh Khan
2024-06-20  5:59 ` [EXTERNAL] [meta-ti] " Chirag Shilwant
2024-06-20 13:31   ` Khan, Sabeeh

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=20240621011752.GG18231@denix.org \
    --to=denis@denix.org \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=sabeeh-khan@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.