Linux-NVME Archive on lore.kernel.org
 help / color / Atom feed
* How to submit a patch to linux-nvme
@ 2021-04-14 19:16 Belanger, Martin
  2021-04-14 19:56 ` Keith Busch
  0 siblings, 1 reply; 2+ messages in thread
From: Belanger, Martin @ 2021-04-14 19:16 UTC (permalink / raw)
  To: linux-nvme

I would like to add a new functionality to the linux-nvme driver. I read the "submitting-patches" document (https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html), but I have a few questions.

The document recommends asking maintainers which tree to use. The file "linux/MAINTAINERS" shows that the tree "git://git.infradead.org/nvme.git" exists. Is that what I should use to make my changes or should I use the mainline tree "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"?

It is my understanding that patches should be submitted to this email list. Is that the only thing I need to do, or should I also submit a pull request?

Thanks,
Martin


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: How to submit a patch to linux-nvme
  2021-04-14 19:16 How to submit a patch to linux-nvme Belanger, Martin
@ 2021-04-14 19:56 ` Keith Busch
  0 siblings, 0 replies; 2+ messages in thread
From: Keith Busch @ 2021-04-14 19:56 UTC (permalink / raw)
  To: Belanger, Martin; +Cc: linux-nvme

On Wed, Apr 14, 2021 at 07:16:42PM +0000, Belanger, Martin wrote:
> I would like to add a new functionality to the linux-nvme driver. I read the "submitting-patches" document (https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html), but I have a few questions.
> 
> The document recommends asking maintainers which tree to use. The file "linux/MAINTAINERS" shows that the tree "git://git.infradead.org/nvme.git" exists. Is that what I should use to make my changes or should I use the mainline tree "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"?

As long as your patch series is isolated to the nvme subsystem, you
should develop nvme patches against the nvme tree,
git.infradead.org/nvme.git, with the branch that targets the desired
kernel release.

Our branch naming convention is 'nvme-X.Y', where X.Y represent the
targeted kernel version (currently nvme-5.13).

New features should always be based on the newest kernel release target.
Bug fixes may target the current RC kernel if we're outside the merge
window.
 
The 'master' branch is not our development branch, so don't use that for
anything.

> It is my understanding that patches should be submitted to this email list. Is that the only thing I need to do, or should I also submit a pull request?

Don't send pull requests please. Just email the patches. There are
various tools that can facilitate the process, but 'git format-patch'
and 'git send-email' will ensure patches are sent correctly for mailing
list consumption.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-14 19:16 How to submit a patch to linux-nvme Belanger, Martin
2021-04-14 19:56 ` Keith Busch

Linux-NVME Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nvme/0 linux-nvme/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nvme linux-nvme/ https://lore.kernel.org/linux-nvme \
		linux-nvme@lists.infradead.org
	public-inbox-index linux-nvme

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-nvme


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git