All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: raj.khem@gmail.com, ricardo.salveti@oss.qualcomm.com
Cc: patchtest@automation.yoctoproject.org,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Patchtest results for [PATCH 2/2] systemd: remove custom rootlibexecdir and replace with nonarch_base_libdir
Date: Sat, 30 Nov 2024 07:59:44 +0000	[thread overview]
Message-ID: <aed2fa753aa344a75fce5a73d7e7cfa7e679a369.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sqAQb37_SggTcKqij7Bj8NgXra_kYB4ttb5DXL3fA_szw@mail.gmail.com>

On Fri, 2024-11-29 at 18:23 -0800, Khem Raj via lists.openembedded.org
wrote:
> 
> 
> On Fri, Nov 29, 2024 at 10:58 AM Ricardo Salveti via
> lists.openembedded.org
> <ricardo.salveti=oss.qualcomm.com@lists.openembedded.org> wrote:
> > On Fri, Nov 29, 2024 at 12:46 AM
> > <patchtest@automation.yoctoproject.org> wrote:
> > > 
> > > Thank you for your submission. Patchtest identified one
> > > or more issues with the patch. Please see the log below for
> > > more information:
> > > 
> > > ---
> > > Testing patch /home/patchtest/share/mboxes/2-2-systemd-remove-
> > > custom-rootlibexecdir-and-replace-with-nonarch_base_libdir.patch
> > > 
> > > FAIL: test max line length: Patch line too long (current length
> > > 224, maximum is 200)
> > > (test_metadata.TestMetadata.test_max_line_length)
> > 
> > Caused by:
> > 
> > -               $INTERCEPT_DIR/postinst_intercept update_udev_hwdb
> > ${PKG} mlprefix=${MLPREFIX} binprefix=${MLPREFIX}
> > rootlibexecdir="${rootlibexecdir}"
> > PREFERRED_PROVIDER_udev="${PREFERRED_PROVIDER_udev}"
> > base_bindir="${base_bindir}"
> > +               $INTERCEPT_DIR/postinst_intercept update_udev_hwdb
> > ${PKG} mlprefix=${MLPREFIX} binprefix=${MLPREFIX}
> > rootlibexecdir="${nonarch_base_libdir}"
> > PREFERRED_PROVIDER_udev="${PREFERRED_PROVIDER_udev}"
> > base_bindir="${base_bindir}"
> > 
> > Didn't want to break that line as part of the change as this is
> > basically a sed.
> > 
> > Can break and send a v2 if needed.
> > 
> 
> 
> Perhaps send a separate patch since it’s a formatting improvement 
> 

I think it is fine. The check is there to stop people introducing
really long lines if we can help it but this already exists and
personally, I find it hard to get worked up about line length...

Cheers,

Richard



  reply	other threads:[~2024-11-30  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29  3:36 [PATCH 1/2] systemd: drop deprecated rootlibdir, rootprefix and split-usr options Ricardo Salveti
2024-11-29  3:36 ` [PATCH 2/2] systemd: remove custom rootlibexecdir and replace with nonarch_base_libdir Ricardo Salveti
2024-11-29  3:46   ` Patchtest results for " patchtest
2024-11-29 18:57     ` Ricardo de Araujo (Salveti)
2024-11-30  2:23       ` [OE-core] " Khem Raj
2024-11-30  7:59         ` Richard Purdie [this message]
2024-12-02  8:40 ` [OE-core] [PATCH 1/2] systemd: drop deprecated rootlibdir, rootprefix and split-usr options Mathieu Dubois-Briand
2024-12-02 19:49 ` Peter Kjellerstedt
2024-12-03  2:41   ` Ricardo de Araujo (Salveti)

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=aed2fa753aa344a75fce5a73d7e7cfa7e679a369.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchtest@automation.yoctoproject.org \
    --cc=raj.khem@gmail.com \
    --cc=ricardo.salveti@oss.qualcomm.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.