Re: [PATCH] remove fullflush and nofullflush in IOMMU generic option

[Joerg Roedel]

On Tue, Sep 23, 2008 at 12:25:24AM +0900, FUJITA Tomonori wrote:
> 
> I'm not sure we can because he has a quite different opinion on this,
> he thinks that the IOMMU parameters are unimportant and minor issue.
> 

Stop your personal attacks and come down. I've never said that iommu
parameters are unimportant. The _move_ of the iommu=[no]fullflush to
generic code is a minor issue in my opinion. For the user it changes
nothing. There was an iommu=fullflush parameter before and now there is
also an iommu=fullflush parameter. The only difference is that it now
affects AMD IOMMU too.

> I'm against adding new generic IOMMU parameters without serious
> consideration. Joerg thinks that we can clean up the parameters like
> adding some for 2.6.28, then add some for 2.6.X, then rename some, in
> an ad-hoc way.

Again. Stop your personal attacks.

Joerg

-- 
           |           AMD Saxony Limited Liability Company & Co. KG
 Operating |         Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 System    |                  Register Court Dresden: HRA 4896
 Research  |              General Partner authorized to represent:
 Center    |             AMD Saxony LLC (Wilmington, Delaware, US)
           | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/