Introduce explicit oot mode in backport script#282
Introduce explicit oot mode in backport script#282pravalikagurram1 wants to merge 1 commit intointel-gpu:kernel-backport/mainfrom
Conversation
CI Bug Log - changes from xkb-221-5d4774a0011436a86e630421adb62addbe83e47a_BAT -> xkb-pr-main-282-493-f1a4aec83ca2a2fbba3e371c0254073a27625d5c_BATSummarySUCCESS No regressions found. Participating hosts (8 -> 9)Additional (1): bat-bmg-3 Known issuesHere are the changes found in xkb-pr-main-282-493-f1a4aec83ca2a2fbba3e371c0254073a27625d5c_BAT that come from known issues: IGT changesIssues hit
Build changes
igt-xkb-104-c142aab3a: c142aab3a |
backport.sh
Outdated
| ;; | ||
| -k|--create-dkms-tree) | ||
| is_oot_tree=1 | ||
| shift |
There was a problem hiding this comment.
oot_tree and DKMS are two different naming, we should have uniformity
README.md
Outdated
| backport/patches/ | ||
| ├── base/ # All fixes and patches merged in drm-tip | ||
| ├── dkms/ # DKMS-specific patches | ||
| └── features/ # Feature patches under review |
There was a problem hiding this comment.
dkms/ additional patches needed for oot modules
There was a problem hiding this comment.
I suggest lets use oot modules instead of dkms
README.md
Outdated
| |3. |reset-tree| Delete the existing tree and re-create it| | ||
| |4. |override| Overrides existing tree| | ||
| |2. |-k, --create-oot| Create DKMS tree and apply all patches including oot patches| | ||
| |3. |delete-tree| Delete the tree| |
There was a problem hiding this comment.
DKMS reference is confusing
Create Tree for OOT modules
CI Bug Log - changes from xkb-223-cb5cf3e176472744c6f8258c194708e2c101a93a_BAT -> xkb-pr-main-282-506-246b79d8780c5439c6ccd56ae786cffd3c128d44_BATSummarySUCCESS No regressions found. Participating hosts (9 -> 9)No changes in participating hosts Known issuesHere are the changes found in xkb-pr-main-282-506-246b79d8780c5439c6ccd56ae786cffd3c128d44_BAT that come from known issues: IGT changesIssues hit
Possible fixes
Build changes
igt-xkb-104-c142aab3a: c142aab3a |
CI Bug Log - changes from xkb-223-cb5cf3e176472744c6f8258c194708e2c101a93a_BAT -> xkb-pr-main-282-507-026769fc95092f2acf1cd4979af5a6715499d251_BATSummarySUCCESS No regressions found. Participating hosts (9 -> 9)No changes in participating hosts Known issuesHere are the changes found in xkb-pr-main-282-507-026769fc95092f2acf1cd4979af5a6715499d251_BAT that come from known issues: IGT changesIssues hit
Possible fixes
Build changes
igt-xkb-104-c142aab3a: c142aab3a |
ayazahma
left a comment
There was a problem hiding this comment.
-c has next Argument, which can base/features/ which should add "oot"
default is features
| echo " -r, --reset-tree Delete the existing tree and re-create it" | ||
| echo " -o, --override Overrides the existing tree" | ||
| echo " -k, --create-oot Create oot tree (includes oot patches)" | ||
| exit 1 |
There was a problem hiding this comment.
Create kernel for OOT XEKMD Modules creation, include addition patches.
backport.sh
Outdated
| # Ignore comments/blank lines from series | ||
| case "$p" in | ||
| ""|\#*) | ||
| continue |
48f58d7 to
2dbb7b0
Compare
Introduce -o (--out-of-tree) as a secondary option that can be combined with the default -c (--create-tree) option to control patch application - Default behavior: ./backport.sh -c creates tree excluding OOT patches - OOT mode: ./backport.sh -c -o creates tree with all patches including OOT This allows other components to maintain full-kernel integration workflows instead of being restricted to OOT-only mode. Update script usage documentation and README with examples of the new -c -o option syntax and behavioral differences. Signed-off-by: Pravalika Gurram <pravalika.gurram@intel.com>
./backport.sh -m
integration instead of being forced into DKMS-only flow.
Signed-off-by: Pravalika Gurram pravalika.gurram@intel.com