public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: vijai kumar <vijaikumar.kanagarajan@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>,
	Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: Re: [PATCH v2] linux-custom: Install config and map file to /boot
Date: Mon, 23 Mar 2020 11:40:30 +0100	[thread overview]
Message-ID: <20200323114030.0d641afa@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CALLGG_KJwhvcvN9r4Xm3RDX5UKDxRTp5q8vQvm1iaiuuSmxZXg@mail.gmail.com>

On Mon, 23 Mar 2020 14:54:05 +0530
vijai kumar <vijaikumar.kanagarajan@gmail.com> wrote:

> On Mon, Mar 23, 2020 at 2:43 PM Henning Schild
> <henning.schild@siemens.com> wrote:
> >
> > On Mon, 23 Mar 2020 07:55:58 +0100
> > Jan Kiszka <jan.kiszka@siemens.com> wrote:
> >  
> > > On 23.03.20 07:53, Henning Schild wrote:  
> > > > On Mon, 23 Mar 2020 07:12:00 +0100
> > > > "[ext] Jan Kiszka" <jan.kiszka@siemens.com> wrote:
> > > >  
> > > >> On 18.03.20 14:21, Vijai Kumar K wrote:  
> > > >>> Align with upstream debian linux-image package. Install the
> > > >>> config and System.map file to /boot directory. Skip
> > > >>> installation for User Mode Linux.
> > > >>>
> > > >>> Signed-off-by: Vijai Kumar K
> > > >>> <Vijaikumar_Kanagarajan@mentor.com> ---
> > > >>> Changes in v2:
> > > >>>       - Moved um condition check as per Henning's comment
> > > >>>
> > > >>>    .../linux/files/debian/isar/install.tmpl             | 12
> > > >>> ++++++++++++ 1 file changed, 12 insertions(+)
> > > >>>
> > > >>> diff --git
> > > >>> a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl
> > > >>> b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl
> > > >>> index 12d592d..849da5e 100644 ---
> > > >>> a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl +++
> > > >>> b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl @@
> > > >>> -37,6 +37,10 @@ do_install() { set -x
> > > >>>        install_image
> > > >>> +    if [ "${ARCH}" != "um" ]; then
> > > >>> +        install_config
> > > >>> +        install_map
> > > >>> +    fi
> > > >>>        install_hooks
> > > >>>        install_dtbs
> > > >>>        install_kmods
> > > >>> @@ -69,6 +73,14 @@ install_image() {
> > > >>>        install_image_debug
> > > >>>    }
> > > >>>
> > > >>> +install_config() {
> > > >>> +    cp ${O}/.config ${deb_img_dir}/$(dirname
> > > >>> ${kimage_path})/config-${krel} +}
> > > >>> +
> > > >>> +install_map() {
> > > >>> +    cp ${O}/System.map ${deb_img_dir}/$(dirname
> > > >>> ${kimage_path})/System.map-${krel}  
> > > >>
> > > >> I think those cp calls should be install with proper modes,
> > > >> no?  
> > > >
> > > > I wanted to say that as well, but in fact the whole scripts
> > > > seems to use a mix of cp and install and this one does not make
> > > > things worse.  
> > >
> > > Yes, there are 2 other cases that should be fixed, separately.  
> >
> > I would suggest we ask Vijai to do all on top, instead of changing
> > here and forgetting the 2 cases?
> >
> > Or maybe just the two on top as part of the series? Vijai what do
> > you think?  
> 
> Hi Henning,
> 
> We could address the two cases here and rest two cases as a separate
> patch. I could update this patch(v3) and can send a separate patch for
> the remaining two cases.
> 
> Is this okay for all?

If you are willing to do the fix i would suggest to include it into
your series instead of sending it alone.

Henning

> Thanks,
> Vijai Kumar K
> 
> >
> > Henning
> >  
> > > Jan
> > >  
> >  


  reply	other threads:[~2020-03-23 10:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 17:14 [PATCH] " Vijai Kumar K
2020-03-17 17:19 ` vijai kumar
2020-03-17 17:39   ` Jan Kiszka
2020-03-25  7:07     ` cedric_hombourger
2020-04-03  7:28       ` vijai kumar
2020-04-03  7:29         ` vijai kumar
2020-03-17 17:32 ` Jan Kiszka
2020-03-18  5:53   ` vijai kumar
2020-03-18  7:34     ` Henning Schild
2020-03-18 13:03       ` vijai kumar
2020-03-18 13:21       ` [PATCH v2] " Vijai Kumar K
2020-03-23  6:12         ` Jan Kiszka
2020-03-23  6:53           ` Henning Schild
2020-03-23  6:55             ` Jan Kiszka
2020-03-23  7:49               ` vijai kumar
2020-03-23  9:13               ` Henning Schild
2020-03-23  9:24                 ` vijai kumar
2020-03-23 10:40                   ` Henning Schild [this message]
2020-03-23 13:40                     ` [PATCH v3 1/2] " Vijai Kumar K
2020-03-23 13:40                       ` [PATCH v3 2/2] meta/recipes-kernel: Replace cp with install Vijai Kumar K
2020-04-17 15:05                       ` [PATCH v3 1/2] linux-custom: Install config and map file to /boot Baurzhan Ismagulov
2020-04-17 18:44                         ` vijai kumar
2020-04-17 18:59                           ` vijai kumar
2020-04-20  9:28                             ` Baurzhan Ismagulov
2020-04-20 10:07                               ` vijai kumar
2020-04-20 16:03                                 ` Baurzhan Ismagulov
2020-04-20 19:46                                   ` Henning Schild
2020-04-20 19:51                                 ` Henning Schild

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=20200323114030.0d641afa@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=Vijaikumar_Kanagarajan@mentor.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=vijaikumar.kanagarajan@gmail.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