Skip to contentSkip to conversation

MAINTAINERS: Add staging branch for HyperBus

PATCH Applied Vignesh Raghavendra 3 participants 5 messages Feb 27, 2020 – Mar 13, 2020 Memory technology devices (MTD)

lore
Share & tools
lore

Vignesh Raghavendra

author maintainer
#0 lore raw

PATCH v2 1/1 MAINTAINERS: Add staging branch for HyperBus

Update HyperBus entry with branch used to stage patches under mtd.git. Also, add mailing list and patchwork queue information.

---
v2: Update commit desc to include all changes being made

 MAINTAINERS | 3 +++
 1 file changed, 3 insertions(+)
MAINTAINERS +3 -0
index a0d86490c2c6..4b9930263dc7 100644
@@ -7769,6 +7769,9 @@ F:	Documentation/ABI/testing/debugfs-hyperv
 
 HYPERBUS SUPPORT
 M:	Vignesh Raghavendra <[email protected]>
+L:	[email protected]
+Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git cfi/next
 S:	Supported
 F:	drivers/mtd/hyperbus/
 F:	include/linux/mtd/hyperbus.h
Signature · 6 lines
2.25.1


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
maintainer Applied
#1 lore raw
Quoted 5 lines · Vignesh Raghavendra

Update HyperBus entry with branch used to stage patches under mtd.git. Also, add mailing list and patchwork queue information.

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.

Miquel

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

author maintainer
#2 lore raw
In reply to Vignesh Raghavendra

Hi Stephen,

Quoted 16 lines · Vignesh Raghavendra

Update HyperBus entry with branch used to stage patches under mtd.git. Also, add mailing list and patchwork queue information.

---
v2: Update commit desc to include all changes being made

 MAINTAINERS | 3 +++
 1 file changed, 3 insertions(+)
MAINTAINERS +0 -0
index a0d86490c2c6..4b9930263dc7 100644

MAINTAINERS F: Documentation/ABI/testing/debugfs-hyperv · line 7774

Quoted 6 lines
MAINTAINERS +3 -0
@@ -7769,6 +7769,9 @@ F:	Documentation/ABI/testing/debugfs-hyperv
 
 HYPERBUS SUPPORT
 M:	Vignesh Raghavendra <[email protected]>
+L:	[email protected]
+Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git cfi/next

Could you add CFI branch of mtd.git to linux-next:

git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git

branch: cfi/next

I am planning to use this branch to stage patches for CFI flashes and for newly added HyperBus framework.

Miquel has already applied this patch to mtd/next

Signature · 6 lines
Regards
Vignesh

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
#3 lore raw

Hi Vignesh,

Quoted 28 lines · On Thu, 12 Mar 2020 14:41:19 +0530 Vignesh Raghavendra <[email protected]> wrote:
Quoted 16 lines · Vignesh Raghavendra

Update HyperBus entry with branch used to stage patches under mtd.git. Also, add mailing list and patchwork queue information.

---
v2: Update commit desc to include all changes being made

 MAINTAINERS | 3 +++
 1 file changed, 3 insertions(+)
MAINTAINERS +0 -0
index a0d86490c2c6..4b9930263dc7 100644

MAINTAINERS F: Documentation/ABI/testing/debugfs-hyperv · line 7774

Quoted 6 lines
MAINTAINERS +3 -0
@@ -7769,6 +7769,9 @@ F:	Documentation/ABI/testing/debugfs-hyperv
 
 HYPERBUS SUPPORT
 M:	Vignesh Raghavendra <[email protected]>
+L:	[email protected]
+Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git cfi/next  

Could you add CFI branch of mtd.git to linux-next:

Quoted 8 lines

git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git

branch: cfi/next

I am planning to use this branch to stage patches for CFI flashes and for newly added HyperBus framework.

Miquel has already applied this patch to mtd/next

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Signature · 3 lines
Cheers,
Stephen Rothwell 
[email protected]

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

author maintainer
#4 lore raw

Hi Stephen,

Quoted 2 lines · Stephen Rothwell

Hi Vignesh,

[...]

Quoted 4 lines
Quoted 4 lines

Could you add CFI branch of mtd.git to linux-next:

git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git

Quoted 9 lines
Quoted 6 lines

branch: cfi/next

I am planning to use this branch to stage patches for CFI flashes and for newly added HyperBus framework.

Miquel has already applied this patch to mtd/next

Added from today.

Thanks!

Quoted 14 lines

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Quoted 3 lines

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Understood.

Signature · 6 lines
Regards
Vignesh

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/