All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: "Opensource [Anthony Olech]" <anthony.olech.opensource@diasemi.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [NEW DRIVER V4 2/7] DA9058 ADC driver
Date: Tue, 16 Apr 2013 17:44:55 +0200	[thread overview]
Message-ID: <516D71F7.3020006@metafoo.de> (raw)
In-Reply-To: <24DF37198A1E704D9811D8F72B87EB514191E442@NB-EX-MBX02.diasemi.com>

On 04/16/2013 04:22 PM, Opensource [Anthony Olech] wrote:
>> [...]
>> please always test your drivers against the latest upstream version before submitting them.
>> [...]
> 
> Hi Lars,
> 
> The driver was tested against linux mainline tag v3.9-rc6, because that was the most recent
> tagged commit in git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git on the day
> that I sent in the patches.
> 
> What exactly do you mean by "latest upstream version" ?
> Did I use the correct repository ?

So, there are usually subsystem specific trees. You can usually find them in
the MAINTAINERS file. E.g. for the IIO subsystem it is
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
The subsystem trees can be up to 3 months (one release) ahead of Linus'
tree. If in doubt place your changes ontop of the next tree, which should
have all the changes from the subsystem trees.

- Lars

      reply	other threads:[~2013-04-16 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 13:05 [NEW DRIVER V4 2/7] DA9058 ADC driver Anthony Olech
2013-04-12 16:13 ` Lars-Peter Clausen
2013-04-16 14:22   ` Opensource [Anthony Olech]
2013-04-16 15:44     ` Lars-Peter Clausen [this message]

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=516D71F7.3020006@metafoo.de \
    --to=lars@metafoo.de \
    --cc=anthony.olech.opensource@diasemi.com \
    --cc=linux-kernel@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 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.