public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Updated FarSync driver
Date: Mon, 29 Jul 2013 11:10:06 +0000	[thread overview]
Message-ID: <20130729111006.GE5053@mwanda> (raw)
In-Reply-To: <E603DC592C92B54A89CEF6B0919A0B1CA86BBBD5E2@SOLO.hq.farsitecommunications.com>

So the main and worst news that I have is that this patch is going
to need to be broken up into about 10-20 little patches that each do
one thing and have description of what they are doing.  The kernel
still has to compile and work correctly after each little patch is
applied (we call that bisectability because it helps "git bisect" to
work).

I know that breaking the patch up into tons of little patches is a
lot of work.  Also you should know that I don't maintain any network
drivers so if you want you could try sending a huge patch and maybe
they will apply it, but probably there is no way.  Anyway, sorry to
be the bearer of bad news here.

> The drivers have been derived from a version that we distribute
> with our cards and these drivers were originally written to
> support all known kernel versions.

Obviously, it's important for hardware vendors to care about
supporting older code, but for the mainline kernel we don't care
about that.  We do have linux-backports-modules (have you looked at
this?  It's the modern way of supporting new hardware with old
kernels.)  Anyway, I haven't looked through the code enough to say
how much is compat layers for older kernels, it's just that I don't
want you to be surprised if the compat code is not accepted.

Next, the format of the patch needs to be something which "git am"
can apply automatically.  The subject needs to be:
[patch 1/xx] farsync: blah blah blah.
There needs to be a patch description and a signed off by.  The
patch needs to be inline instead of as an attachment.  Verify that
it applies correctly before you send it to the list.  Email it to
yourself, save the raw email as text, cat it to "git am".

There are a lot of scripts/checkpatch.pl warnings which will all
need to be fixed.
total: 692 errors, 907 warnings, 17158 lines checked
These are trivial formatting things so they are easy to fix.

I will look through the diff as well and see if I spot anything
obvious.  I'm not a networking guy so I will miss a lot of things.

regards,
dan carpenter


  parent reply	other threads:[~2013-07-29 11:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  7:20 [patch] farsync: fix support for over 30 cards Dan Carpenter
2012-10-09 17:55 ` David Miller
2013-07-26 10:13 ` Updated FarSync driver Kevin Curtis
2013-07-26 23:41   ` Dan Carpenter
2013-07-27 20:39     ` govind
2013-07-29 11:10   ` Dan Carpenter [this message]
2013-07-29 11:42   ` Dan Carpenter
2013-07-29 12:58   ` Kevin Curtis
2013-07-31 13:55   ` Kevin Curtis
2013-07-31 14:50   ` Dan Carpenter
2013-08-30 20:53   ` Dan Carpenter
2013-08-30 21:05   ` Dan Carpenter

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=20130729111006.GE5053@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.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