From: Michael Walle
Sent: Monday, April 7, 2025 7:28 AM
> Hi,
> > > > > I wouldn't mind printing the pointer for %p[mMI], but %pa prints the
> > > > > *content* of the pointer which is really confusing. I.e. in
> > > > > pinctrl-single.c the reg value pairs are printed like
> > > > >
> > > > > d
Hi,
> > > > I wouldn't mind printing the pointer for %p[mMI], but %pa prints the
> > > > *content* of the pointer which is really confusing. I.e. in
> > > > pinctrl-single.c the reg value pairs are printed like
> > > >
> > > > dev_dbg(dev, "reg/val %pa/0x%08x\n", ®, val);
> > > >
> > > > with r
On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
If tiny printf is used with 0x%08X (upper case X) the output is
always 0x. It could be confusing if upper case instead
of lower case is used intentionally or accidentally because the
actual value is not output. To avoid this confusion, tin
Hi Marek,
On 3/20/25 12:49 PM, Marek Vasut wrote:
On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
If tiny printf is used with 0x%08X (upper case X) the output is
always 0x. It could be confusing if upper case instead
of lower case is used intentionally or accidentally because the
actu
On Fri, Apr 04, 2025 at 10:33:25AM +0200, Michael Walle wrote:
> Hi,
>
> > > I wouldn't mind printing the pointer for %p[mMI], but %pa prints the
> > > *content* of the pointer which is really confusing. I.e. in
> > > pinctrl-single.c the reg value pairs are printed like
> > >
> > > dev_dbg(dev
Hi,
> > I wouldn't mind printing the pointer for %p[mMI], but %pa prints the
> > *content* of the pointer which is really confusing. I.e. in
> > pinctrl-single.c the reg value pairs are printed like
> >
> > dev_dbg(dev, "reg/val %pa/0x%08x\n", ®, val);
> >
> > with reg being a pointer to a phy
From: Michael Walle
Sent: Wednesday, April 2, 2025 9:02 AM
The issue is that disabling TINY_PRINTF may not be possible (size
constraints) and some code is compiled for different stages and people
typically don't check whether the format used in printf is valid with
tiny_printf.
Hi,
> The issue is that disabling TINY_PRINTF may not be possible (size
> constraints) and some code is compiled for different stages and people
> typically don't check whether the format used in printf is valid with
> tiny_printf. I've had this issue already in the past, I vaguely recall
> "c
Hi,
> >> The issue is that disabling TINY_PRINTF may not be possible (size
> >> constraints) and some code is compiled for different stages and people
> >> typically don't check whether the format used in printf is valid with
> >> tiny_printf. I've had this issue already in the past, I vaguely rec
From: Michael Walle
Sent: Tuesday, April 1, 2025 10:56 AM
>
> Hi,
>
>> The issue is that disabling TINY_PRINTF may not be possible (size
>> constraints) and some code is compiled for different stages and people
>> typically don't check whether the format used in printf is valid with
>> tiny_prin
On Thu, Mar 20, 2025 at 05:58:56PM +, Christoph Niedermaier wrote:
> From: Tom Rini
> Sent: Thursday, March 20, 2025 3:19 PM
> > On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> > > On 3/20/25 3:00 PM, Quentin Schulz wrote:
> > > > Hi Marek,
> > > >
> > > > On 3/20/25 12:49 PM, M
From: Tom Rini
Sent: Thursday, March 20, 2025 7:28 PM
> On Thu, Mar 20, 2025 at 05:58:56PM +, Christoph Niedermaier wrote:
> > From: Tom Rini
> > Sent: Thursday, March 20, 2025 3:19 PM
> > > On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> > > > On 3/20/25 3:00 PM, Quentin Schul
From: Tom Rini
Sent: Thursday, March 20, 2025 3:19 PM
> On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> > On 3/20/25 3:00 PM, Quentin Schulz wrote:
> > > Hi Marek,
> > >
> > > On 3/20/25 12:49 PM, Marek Vasut wrote:
> > > > On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > > > >
On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> On 3/20/25 3:00 PM, Quentin Schulz wrote:
> > Hi Marek,
> >
> > On 3/20/25 12:49 PM, Marek Vasut wrote:
> > > On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > > > If tiny printf is used with 0x%08X (upper case X) the output is
> >
On 3/20/25 3:00 PM, Quentin Schulz wrote:
Hi Marek,
On 3/20/25 12:49 PM, Marek Vasut wrote:
On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
If tiny printf is used with 0x%08X (upper case X) the output is
always 0x. It could be confusing if upper case instead
of lower case is used int
On Thu, Mar 20, 2025 at 12:49:17PM +0100, Marek Vasut wrote:
> On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > If tiny printf is used with 0x%08X (upper case X) the output is
> > always 0x. It could be confusing if upper case instead
> > of lower case is used intentionally or accident
16 matches
Mail list logo
