OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: opensbi@lists.infradead.org
Subject: [PATCH 0/3] CArray improvements
Date: Fri, 10 May 2024 16:56:23 +0100	[thread overview]
Message-ID: <35c73d38-0a00-44a1-bcab-99baced367de@gmail.com> (raw)
In-Reply-To: <CAAhSdy1=BBensr-Z2a8dTP_=Fpa0j+xOqFuxCb3hB56x1sciXA@mail.gmail.com>

On 5/7/24 07:06, Anup Patel wrote:
> Hi Ivan,
> 
> On Tue, Apr 2, 2024 at 3:04?AM Ivan Orlov <ivan.orlov0322@gmail.com> wrote:
>>
>> Currently, there are a few inconveniences the developer may face when
>> using CArrays, including:
>>
>> - Unability to regenerate the carray-related .c files reliably without
>> removing the `build/` directory
>> - Confusion caused by source (.c) files in the `build/` directory (the
>> fact that some file was generated by carray.sh is not obvious)
>>
>> This patch series fixes them.
>>
>> Ivan Orlov (3):
>>    Makefile: clean auto-generated *.c files properly
>>    scripts/carray.sh: Add comment to generated files
>>    docs: writing tests: update cleaning instructions
> 
> I assume you (or someone else) will be sending v2 of this series ?
> 

Hi Anup,

Sorry for the late reply. I believe Ben Dooks 
<ben.dooks@codethink.co.uk> is going to send the V2 with the updated 
carray cleanup :)

Thank you!

-- 
Kind regards,
Ivan Orlov



      reply	other threads:[~2024-05-10 15:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 21:34 [PATCH 0/3] CArray improvements Ivan Orlov
2024-04-01 21:34 ` [PATCH 1/3] Makefile: clean auto-generated *.c files properly Ivan Orlov
2024-04-22 15:19   ` Andrew Jones
2024-04-23 14:58     ` Ivan Orlov
2024-04-23 15:15       ` Ben Dooks
2024-04-23 15:18       ` Andrew Jones
2024-04-23 15:20       ` Ben Dooks
2024-04-23 15:24         ` Ben Dooks
2024-04-23 15:26         ` Ben Dooks
2024-04-23 15:41           ` Ivan Orlov
2024-04-26 16:25             ` Ben Dooks
2024-04-29  8:52               ` Andrew Jones
2024-04-29 12:16                 ` Ben Dooks
2024-04-29 13:11                 ` Ben Dooks
2024-04-01 21:34 ` [PATCH 2/3] scripts/carray.sh: Add comment to generated files Ivan Orlov
2024-04-22 15:21   ` Andrew Jones
2024-04-23 15:25   ` Ben Dooks
2024-04-01 21:34 ` [PATCH 3/3] docs: writing tests: update cleaning instructions Ivan Orlov
2024-04-22 15:22   ` Andrew Jones
2024-05-07  6:06 ` [PATCH 0/3] CArray improvements Anup Patel
2024-05-10 15:56   ` Ivan Orlov [this message]

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=35c73d38-0a00-44a1-bcab-99baced367de@gmail.com \
    --to=ivan.orlov0322@gmail.com \
    --cc=opensbi@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox