[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230612102124.6d7c31e1@kernel.org>
Date: Mon, 12 Jun 2023 10:21:24 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Wei Hu <weh@...rosoft.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>, Long Li
<longli@...rosoft.com>, Ajay Sharma <sharmaajay@...rosoft.com>,
"jgg@...pe.ca" <jgg@...pe.ca>, "leon@...nel.org" <leon@...nel.org>, KY
Srinivasan <kys@...rosoft.com>, Haiyang Zhang <haiyangz@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>, Dexuan Cui
<decui@...rosoft.com>, "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>, "pabeni@...hat.com"
<pabeni@...hat.com>, "vkuznets@...hat.com" <vkuznets@...hat.com>,
"ssengar@...ux.microsoft.com" <ssengar@...ux.microsoft.com>,
"shradhagupta@...ux.microsoft.com" <shradhagupta@...ux.microsoft.com>
Subject: Re: [PATCH v2 1/1] RDMA/mana_ib: Add EQ interrupt support to mana
ib driver.
On Mon, 12 Jun 2023 04:44:44 +0000 Wei Hu wrote:
> If the patch also needs to go through the NETDEV branch, does it mean two subsystems will pull its own part? A few follow-up questions about generating a PR, since I have never done such before.
>
> 1. Which repo should I clone and create the branch from?
The main tree of Linus Torvalds. Check which tags are present in both
netdev and rdma trees and use the newest common tag between the trees
as a base.
> 2. From the example you provided, I see these people has their own branches on kernel.org, for example something like:
> git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-updates-2023-06-06.
> I am not Linux maintainer. I just have repo on Github. How do I
> create or fork on kernel.org? Do I need an account to do so? Or I can
> use my own repo on Github?
GitHub is fine.
> 3. How to create PR in this case? Should I follow this link:
> https://docs.kernel.org/maintainer/pull-requests.html?
Sort of. But still post the patches, so you'd want to use these
commands somewhere along the way:
git format-patch [...] -o $path --cover-letter
git request-pull [...] >> $path/0000-cover-letter.patch
Powered by blists - more mailing lists