On Wed, 26 Aug 2020 at 10:55, Philippe Mathieu-Daudé wrote:
>> What tree were you expecting these to go in via? Probably worth
>> being specific about who you're pinging in this kind of case ;-)
>
>
> Ok understood for the next time. In this case you are listed as
> maintainer :)
Oh, so I am, I h
Le mer. 26 août 2020 11:54, Philippe Mathieu-Daudé a
écrit :
> Hi Peter,
>
> Le lun. 24 août 2020 17:01, Peter Maydell a
> écrit :
>
>> On Sat, 22 Aug 2020 at 21:02, Philippe Mathieu-Daudé
>> wrote:
>> >
>> > On 8/12/20 9:02 PM, Philippe Mathieu-Daudé wrote:
>> > > This series aims to ease look
Hi Peter,
Le lun. 24 août 2020 17:01, Peter Maydell a
écrit :
> On Sat, 22 Aug 2020 at 21:02, Philippe Mathieu-Daudé
> wrote:
> >
> > On 8/12/20 9:02 PM, Philippe Mathieu-Daudé wrote:
> > > This series aims to ease looking at the '-d unimp' output reported
> > > by the UnimplementedDevice.
> >
On Sat, 22 Aug 2020 at 21:02, Philippe Mathieu-Daudé wrote:
>
> On 8/12/20 9:02 PM, Philippe Mathieu-Daudé wrote:
> > This series aims to ease looking at the '-d unimp' output reported
> > by the UnimplementedDevice.
> >
> > - read/write accesses are now aligned
> > - the value format width uses t
On 8/12/20 9:02 PM, Philippe Mathieu-Daudé wrote:
> This series aims to ease looking at the '-d unimp' output reported
> by the UnimplementedDevice.
>
> - read/write accesses are now aligned
> - the value format width uses the access size
> - the offset (address) uses the size of the memory region
This series aims to ease looking at the '-d unimp' output reported
by the UnimplementedDevice.
- read/write accesses are now aligned
- the value format width uses the access size
- the offset (address) uses the size of the memory region it belongs
Series fully reviewed.
Since v1:
- Use DIV_ROUND
