On 2024-03-04 16:28, Tom Rini wrote:
On Tue, Feb 06, 2024 at 12:00:04PM +0100, Dragan Simic wrote:
Prevent the error messages produced by which(1), such as the one
quoted
below, from being visible in the build outputs.
which: no dtc in (./scripts/dtc)
This makes the build outputs look a
On Tue, Feb 06, 2024 at 12:00:04PM +0100, Dragan Simic wrote:
> Prevent the error messages produced by which(1), such as the one quoted
> below, from being visible in the build outputs.
>
> which: no dtc in (./scripts/dtc)
>
> This makes the build outputs look a tiny bit cleaner.
>
>
On 2024-02-15 15:21, Dragan Simic wrote:
On 2024-02-15 14:13, Tom Rini wrote:
On Wed, Feb 14, 2024 at 04:48:52AM +0100, Dragan Simic wrote:
On 2024-02-06 12:00, Dragan Simic wrote:
> Prevent the error messages produced by which(1), such as the one quoted
> below, from being visible in the
On 2024-02-15 14:13, Tom Rini wrote:
On Wed, Feb 14, 2024 at 04:48:52AM +0100, Dragan Simic wrote:
On 2024-02-06 12:00, Dragan Simic wrote:
> Prevent the error messages produced by which(1), such as the one quoted
> below, from being visible in the build outputs.
>
> which: no dtc in
On Wed, Feb 14, 2024 at 04:48:52AM +0100, Dragan Simic wrote:
> On 2024-02-06 12:00, Dragan Simic wrote:
> > Prevent the error messages produced by which(1), such as the one quoted
> > below, from being visible in the build outputs.
> >
> > which: no dtc in (./scripts/dtc)
> >
> > This makes
On 2024-02-06 12:00, Dragan Simic wrote:
Prevent the error messages produced by which(1), such as the one quoted
below, from being visible in the build outputs.
which: no dtc in (./scripts/dtc)
This makes the build outputs look a tiny bit cleaner.
Just checking, is there something that
Prevent the error messages produced by which(1), such as the one quoted
below, from being visible in the build outputs.
which: no dtc in (./scripts/dtc)
This makes the build outputs look a tiny bit cleaner.
Signed-off-by: Dragan Simic
Reviewed-by: Quentin Schulz
---
Notes:
Version 2
7 matches
Mail list logo