All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raju Rangoju <rajur@chelsio.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	rahul.lakkireddy@chelsio.com
Subject: Re: [PATCH net-next] cxgb4: Add new T6 PCI device id 0x6092
Date: Thu, 4 Feb 2021 16:18:54 +0530	[thread overview]
Message-ID: <20210204104852.GA10526@chelsio.com> (raw)
In-Reply-To: <20210203182337.3a77480a@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Wednesday, February 02/03/21, 2021 at 18:23:37 -0800, Jakub Kicinski wrote:
> On Tue,  2 Feb 2021 23:55:11 +0530 Raju Rangoju wrote:
> > Signed-off-by: Raju Rangoju <rajur@chelsio.com>
> 
> Does this device require any code which only exists in net-next?
> 

No code dependency exists in net-next

> Pure device id patches are okay for net.

Sure, it can go net tree.

  reply	other threads:[~2021-02-04 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 18:25 [PATCH net-next] cxgb4: Add new T6 PCI device id 0x6092 Raju Rangoju
2021-02-04  2:23 ` Jakub Kicinski
2021-02-04 10:48   ` Raju Rangoju [this message]
2021-02-05  2:20 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210204104852.GA10526@chelsio.com \
    --to=rajur@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rahul.lakkireddy@chelsio.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.