linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Ross Maynard <bids.7405@bigpond.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Networking <netdev@vger.kernel.org>,
	Linux USB <linux-usb@vger.kernel.org>,
	Oliver Neukum <oneukum@suse.com>
Subject: Re: Fwd: 3 more broken Zaurii - SL-5600, A300, C700
Date: Sat, 8 Jul 2023 22:49:00 +0200	[thread overview]
Message-ID: <05a229e8-b0b6-4d29-8561-70d02f6dc31b@lunn.ch> (raw)
In-Reply-To: <14fd48c8-3955-c933-ab6f-329e54da090f@bigpond.com>

> Could someone please submit the patch for me?

You are not far from it yourself.

I've not followed the history here. Did it never work, or has it
worked in the past, and then at some point broke?

If it never worked, this would be classed as new development, and so
the patch should be for net-next. If it did work, but at some point in
time it stopped working, then it is for net.

Take a read of:

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html

And produce a patch based on net, or net-next.

Also read:

https://www.kernel.org/doc/html/latest/process/submitting-patches.html

Please ask questions if anything is not clear.

	Andrew

  reply	other threads:[~2023-07-08 21:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  2:09 Fwd: 3 more broken Zaurii - SL-5600, A300, C700 Bagas Sanjaya
2023-07-06  3:08 ` Bagas Sanjaya
2023-07-06 11:45   ` Thorsten Leemhuis
2023-07-06 16:41     ` Dave Jones
2023-07-07 12:28       ` Ross Maynard
2023-07-08 12:17         ` Ross Maynard
2023-07-08 20:49           ` Andrew Lunn [this message]
2023-07-09  4:36             ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 16:55               ` Jakub Kicinski
2023-07-10 17:09                 ` Linux regression tracking (Thorsten Leemhuis)

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=05a229e8-b0b6-4d29-8561-70d02f6dc31b@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=bagasdotme@gmail.com \
    --cc=bids.7405@bigpond.com \
    --cc=davej@codemonkey.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).