All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Fariya <fariyaf@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>, backports@vger.kernel.org
Subject: Re: Procedure to make the driver into the backports project
Date: Fri, 06 Jun 2014 08:09:22 +0200	[thread overview]
Message-ID: <1402034962.4158.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAG+h2qi4b7OJwj+0X=M1sFC3GzfZ70EMc2tLTHW9YKoPw7gAeg@mail.gmail.com> (sfid-20140606_015911_268556_8849B381)

On Fri, 2014-06-06 at 05:29 +0530, Fariya wrote:

> Considering that my driver doesn't compile on kernel versions < the
> latest one, I wanted to submit a patch/patches to handle all kernel
> versions. My question was relating to this - do I need to submit a
> patch [which handles kernel versions from 3.0 to 3.14] or patches for
> each kernel version from 3.0 to 3.14, which when applied on the latest
> driver of mine, would make it compilable for all kernel versions?

You need a single patch - hopefully much is already handled by the
backports project?

Ideally, you don't patch your driver at all, but extend the backport
(include files, compat.ko module) to provide the APIs that your driver
needs but that don't exist on older kernels. Sometimes, patching (the)
driver(s) is unavoidable, in which case semantic patches would be
preferred.

However, you can start with a patch and we can help you disentangle it.

johannes


  reply	other threads:[~2014-06-06  6:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  9:47 Procedure to make the driver into the backports project Fariya
2014-05-26 13:44 ` Arend van Spriel
2014-05-26 14:15   ` Arend van Spriel
2014-05-29 10:03     ` Fariya
2014-05-29 14:39       ` Arend van Spriel
     [not found]         ` <CAG+h2qjirPQYDnajR-3VBvZgr+TxBkMwS3q5xXUrNC+YQmfuog@mail.gmail.com>
2014-06-05 21:30           ` Fariya
2014-06-05 21:55             ` Arend van Spriel
2014-06-05 23:59               ` Fariya
2014-06-06  6:09                 ` Johannes Berg [this message]
2014-06-06  8:09                 ` Arend van Spriel

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=1402034962.4158.1.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=fariyaf@gmail.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.