[rtems commit] MAINAINERS: Add rule for BSP-specific patches

[Sebastian Huber]

Module:    rtems
Branch:    master
Commit:    e40c5896bd6ac9ef46c23b9c81ecf389cdccb9d2
Changeset: http://git.rtems.org/rtems/commit/?id=e40c5896bd6ac9ef46c23b9c81ecf389cdccb9d2

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Tue Mar 20 13:43:07 2018 +0100

MAINAINERS: Add rule for BSP-specific patches

---

 MAINTAINERS | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 2d91ecb..2732d77 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20,12 +20,13 @@ who can be trusted to distinguish between changes which require
 others to review, require a problem report, or can be safely committed
 with limited review.
 
-Write After Approval is granted to experienced but also trusted 
+Write After Approval is granted to experienced but also trusted
 RTEMS developers.  These developers may be less familiar with
 the breadth of RTEMS.  Developers with write after approval need
-to submit their patches for review. Once the patches have been
-approved by a developer with Blanket Write Privileges, the patches
-may be checked in.  
+to submit their patches for review.  Once the patches have been approved by a
+developer with Blanket Write Privileges, the patches may be checked in.
+A BSP-specific patch may be checked in three work days after sending it to
+devel at rtems.org in case nobody explicitly rejected the patch.
 
 Localized Write Permission is for developers who have primary
 responsibility for a port and all associated BSPs, a BSP, or other