[Mlir-commits] [mlir] a3b5ccd - Update DialectConversion.md

[llvmlistbot at llvm.org]

Author: Tharindu Rusira
Date: 2020-05-26T15:24:54+02:00
New Revision: a3b5ccddcc3512432fc386b9197e6f103e190894

URL: https://github.com/llvm/llvm-project/commit/a3b5ccddcc3512432fc386b9197e6f103e190894
DIFF: https://github.com/llvm/llvm-project/commit/a3b5ccddcc3512432fc386b9197e6f103e190894.diff

LOG: Update DialectConversion.md

line 164: typo? baz.add should be bar.add.
`bar.add` -> `foo.add`

Added: 
    

Modified: 
    mlir/docs/DialectConversion.md

Removed: 
    


################################################################################
diff  --git a/mlir/docs/DialectConversion.md b/mlir/docs/DialectConversion.md
index 0835527ae201..1f9ec14b6a96 100644
--- a/mlir/docs/DialectConversion.md
+++ b/mlir/docs/DialectConversion.md
@@ -161,7 +161,7 @@ a set of legal ones.
 As an example, say you define a target that supports one operation: `foo.add`.
 When providing the following patterns: [`bar.add` -> `baz.add`, `baz.add` ->
 `foo.add`], the framework will automatically detect that it can legalize
-`baz.add` -> `foo.add` even though a direct conversion does not exist. This
+`bar.add` -> `foo.add` even though a direct conversion does not exist. This
 means that you don’t have to define a direct legalization pattern for `bar.add`
 -> `foo.add`.