All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <sean.anderson@seco.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org,
	Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH 6/6] u-boot: Rework signing to remove interdependencies
Date: Thu, 10 Nov 2022 10:19:01 -0500	[thread overview]
Message-ID: <459cc433-e112-4dfa-8faf-5811ce20e6cd@seco.com> (raw)
In-Reply-To: <Y2wyumeMw77ATwDl@mail.local>

On 11/9/22 18:07, Alexandre Belloni wrote:
> Hi,
> 
> On 01/11/2022 13:54:18-0400, Sean Anderson wrote:
>> > That would result in a lot of messages on the mailing list and ends up
>> > being a lot of work for the maintainers as well.
>> 
>> If you use a tool like b4 [1] it can automatically generate a summary thank-you message.
>> As an example, [2]. This keeps the number of messages down and is not terribly
>> burdensome for maintainers (since it fits into the usual patch workflow),
>> 
> 
> I was also surprised to not receive confirmation that my patches were
> applied. However, unfortunately, b4 is not working with our current
> workflow as I am applying the patches and providing tested branches to
> Richard that he is cherry-picking from.
> 
>> You can set up something like pwbot [3], which integrates with patchwork
>> and your repository. It produces messages like [4] automatically when it
>> notices they have been merged into the repositiry, and marks them as
>> "Accepted" in patchwork. This is even lower effort for your maintainers.
>> 
> 
> This would integrate better but I4m not sure we have a pw instace for
> every repository that compose poky.

I think even incremental changes are good here. We can start just e.g.
openembedded-core and see how that goes.

--Sean



  reply	other threads:[~2022-11-10 15:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 23:37 [PATCH 0/6] u-boot: Rework signing process to remove interdependencies Sean Anderson
2022-10-21 23:37 ` [PATCH 1/6] uboot-sign: Fix using wrong KEY_REQ_ARGS Sean Anderson
2022-10-21 23:37 ` [PATCH 2/6] kernel: Clear SYSROOT_DIRS instead of replacing sysroot_stage_all Sean Anderson
2022-10-21 23:37 ` [PATCH 3/6] kernel-fitimage: Use KERNEL_OUTPUT_DIR where appropriate Sean Anderson
2022-10-21 23:37 ` [PATCH 4/6] uboot-sign: Use bitbake variables directly Sean Anderson
2022-10-21 23:37 ` [PATCH 5/6] uboot-sign: Split off kernel-fitimage variables Sean Anderson
2022-10-21 23:37 ` [PATCH 6/6] u-boot: Rework signing to remove interdependencies Sean Anderson
     [not found]   ` <f8039bfc391404e83464c6894ce3ebf5496f1da1.camel@linuxfoundation.org>
2022-10-26 16:49     ` Sean Anderson
2022-10-26 17:00       ` Richard Purdie
2022-10-26 17:21         ` Sean Anderson
2022-10-28 15:09           ` Richard Purdie
2022-10-28 15:29             ` Sean Anderson
2022-10-28 15:37               ` Richard Purdie
2022-11-01 16:14                 ` Sean Anderson
2022-11-01 17:29                   ` Richard Purdie
2022-11-01 17:40                     ` Sean Anderson
2022-11-01 17:44                       ` Richard Purdie
2022-11-01 17:54                         ` Sean Anderson
2022-11-01 18:02                           ` [OE-core] " Alexander Kanavin
2022-11-01 18:29                             ` Sean Anderson
2022-11-01 18:40                               ` Alexander Kanavin
     [not found]                           ` <172387EDE52D4BA6.10252@lists.openembedded.org>
2022-11-01 18:24                             ` Alexander Kanavin
2022-11-09 23:07                           ` Alexandre Belloni
2022-11-10 15:19                             ` Sean Anderson [this message]
2022-11-01 21:01                       ` [OE-core] " Ross Burton

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=459cc433-e112-4dfa-8faf-5811ce20e6cd@seco.com \
    --to=sean.anderson@seco.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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.