On Fri, Sep 04, 2020 at 08:47:04PM +, Fenghua Yu wrote:
> Please let me know any comments and I'll address them ASAP. I'm just
> eager to see the patches upstreamed:)
Why are you eager to see them upstream? What's with all that hurry
everytime?
--
Regards/Gruss,
Boris.
Hi, Boris,
On Fri, Sep 04, 2020 at 09:45:19PM +0200, Borislav Petkov wrote:
> On Fri, Sep 04, 2020 at 04:06:13PM +, Fenghua Yu wrote:
> > Thank you very much for your review!
>
> I'm not done with my review yet.
>
> > Could you please consider to commit the series?
>
> Fenghua, how long
On Fri, Sep 04, 2020 at 04:06:13PM +, Fenghua Yu wrote:
> Thank you very much for your review!
I'm not done with my review yet.
> Could you please consider to commit the series?
Fenghua, how long are you doing kernel development? When do patches get
considered for inclusion? I'm sure you
Hi, Boris,
On Fri, Sep 04, 2020 at 12:46:14PM +0200, Borislav Petkov wrote:
> Just a nitpick in case you have to send a new version or the committer
> of this one can fixup the prefix here:
>
> > Subject: Re: [PATCH v7 1/9] iommu: Change type of pasid to u32
>
>
Just a nitpick in case you have to send a new version or the committer
of this one can fixup the prefix here:
> Subject: Re: [PATCH v7 1/9] iommu: Change type of pasid to u32
drm, iommu: Change type ...
On Thu, Aug 27, 2020 at 08:06:26AM -0700, Fenghua Yu wrote:
>
PASID is defined as a few different types in iommu including "int",
"u32", and "unsigned int". To be consistent and to match with uapi
definitions, define PASID and its variations (e.g. max PASID) as "u32".
"u32" is also shorter and a little more explicit than "unsigned int".
No PASID type change
