Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC] treewide: cleanup unreachable breaks
Date: Sun, 18 Oct 2020 07:43:32 +0200	[thread overview]
Message-ID: <20201018054332.GB593954@kroah.com> (raw)
In-Reply-To: <20201017160928.12698-1-trix@redhat.com>

On Sat, Oct 17, 2020 at 09:09:28AM -0700, trix at redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
> 
> This is a upcoming change to clean up a new warning treewide.
> I am wondering if the change could be one mega patch (see below) or
> normal patch per file about 100 patches or somewhere half way by collecting
> early acks.

Please break it up into one-patch-per-subsystem, like normal, and get it
merged that way.

Sending us a patch, without even a diffstat to review, isn't going to
get you very far...

thanks,

greg k-h

  parent reply	other threads:[~2020-10-18  5:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 16:09 [Intel-wired-lan] [RFC] treewide: cleanup unreachable breaks trix
2020-10-17 16:24 ` Joe Perches
2020-10-17 18:21   ` [Intel-wired-lan] [Cocci] " Julia Lawall
2020-10-17 19:00     ` Joe Perches
2020-10-17 21:01 ` [Intel-wired-lan] " Dan Williams
2020-10-18  5:43 ` Greg KH [this message]
2020-10-18 14:04   ` Tom Rix
2020-10-19 19:42   ` Nick Desaulniers
2020-10-19 23:05     ` Jason Gunthorpe
2020-10-20 14:09       ` Tom Rix
2020-10-20  8:47     ` [Intel-wired-lan] [Ocfs2-devel] " John Haxby
2020-10-20 13:55     ` [Intel-wired-lan] " Tom Rix
2020-10-20 18:42     ` Joe Perches
2020-10-18  9:29 ` Hans de Goede
2020-10-18 18:59 ` [Intel-wired-lan] [Ocfs2-devel] " Matthew Wilcox
2020-10-18 19:06   ` Joe Perches
2020-10-18 19:13   ` James Bottomley
2020-10-18 19:16     ` Matthew Wilcox
2020-10-18 19:17       ` James Bottomley

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=20201018054332.GB593954@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=intel-wired-lan@osuosl.org \
    /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