Hi Vignesh, On Thu, 12 Mar 2020 14:41:19 +0530 Vignesh Raghavendra wrote: > > On 27/02/20 10:42 am, Vignesh Raghavendra wrote: > > Update HyperBus entry with branch used to stage patches under > > mtd.git. Also, add mailing list and patchwork queue information. > > > > Signed-off-by: Vignesh Raghavendra > > Acked-by: Miquel Raynal > > --- > > v2: Update commit desc to include all changes being made > > > > MAINTAINERS | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index a0d86490c2c6..4b9930263dc7 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -7769,6 +7769,9 @@ F: Documentation/ABI/testing/debugfs-hyperv > > > > HYPERBUS SUPPORT > > M: Vignesh Raghavendra > > +L: linux-mtd@lists.infradead.org > > +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 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. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au