Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Simon Rowe <simon.rowe@nutanix.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/lvm2: enable package with musl
Date: Tue, 21 Mar 2023 14:54:55 +0100	[thread overview]
Message-ID: <20230321145455.7dce4271@windsurf> (raw)
In-Reply-To: <DM8PR02MB81219477CD31D864F078BC8493819@DM8PR02MB8121.namprd02.prod.outlook.com>

Hello Simon,

On Tue, 21 Mar 2023 13:39:12 +0000
Simon Rowe <simon.rowe@nutanix.com> wrote:

> I am not the author of these patches, which is why I didn’t add a
> ‘Signed-off-by:’. I followed what I thought the process was for
> patches originating from elsewhere by adding a ‘Fetch from:’ to each
> patch as mentioned in 19.4 of the manual. I can regenerate them if
> that’s the correct approach.

A Signed-off-by is not only an indication of the author, but also an
indication of the chain of people through which the patch traveled. For
example in the Linux kernel, patches have a SoB from the author, then a
SoB from the maintainer taking the patch, and possibly another SoB from
yet another maintainer taking the patch from that previous maintainer.

In Buildroot, we therefore have patches with two SoB: one from the
original author, and one from the developer bringing the patch into
Buildroot. Or alternatively patches with only one SoB, from the
developer bringing the patch into Buildroot (you in this case) when the
original patch lacks an SoB.

> I’ve not got a use case for multipath myself by I’ll check if I can
> get it to build with these patches.

Good!

> > Another question is the upstream status of the Gentoo patches? Have
> > they been submitted for inclusion by the upstream lvm2 project?  
> 
> There seems to be a suggestion that was attempted on the ticket
> 
> https://bugs.gentoo.org/549506
> 
> but that was some time ago and there’s no sign of them being accepted.

It's been a while ago. Perhaps time to do another attempt at
upstreaming those patches?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-03-21 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 11:36 [Buildroot] [PATCH 1/1] package/lvm2: enable package with musl Simon Rowe
2023-03-19 16:25 ` Thomas Petazzoni via buildroot
2023-03-21 13:39   ` Simon Rowe
2023-03-21 13:54     ` Thomas Petazzoni via buildroot [this message]
2023-03-23 12:36       ` Simon Rowe
2023-03-23 13:15         ` Thomas Petazzoni via buildroot
2023-03-23 14:13 ` [Buildroot] [PATCH v2 1/2] " Simon Rowe
2023-03-23 14:13   ` [Buildroot] [PATCH v2 2/2] package/multipath-tools: enable " Simon Rowe
2023-03-26 21:11     ` Thomas Petazzoni via buildroot
2023-03-26 21:10   ` [Buildroot] [PATCH v2 1/2] package/lvm2: enable package " Thomas Petazzoni via buildroot

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=20230321145455.7dce4271@windsurf \
    --to=buildroot@buildroot.org \
    --cc=simon.rowe@nutanix.com \
    --cc=thomas.petazzoni@bootlin.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