* Git repo to use for submitting patches
@ 2015-07-10 11:42 Giuseppe Barba
2015-07-10 11:51 ` Daniel Baluta
0 siblings, 1 reply; 4+ messages in thread
From: Giuseppe Barba @ 2015-07-10 11:42 UTC (permalink / raw
To: linux-iio
Hi,
sorry I'm new in this list.
I wold like to submit some patches to add support for new sensor.
I'm not sure what repo I have to use for code rebasing. I've found:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
is it the correct one?
Thanks in advance,
Giuseppe Barba.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Git repo to use for submitting patches
2015-07-10 11:42 Git repo to use for submitting patches Giuseppe Barba
@ 2015-07-10 11:51 ` Daniel Baluta
2015-07-11 17:46 ` Jonathan Cameron
0 siblings, 1 reply; 4+ messages in thread
From: Daniel Baluta @ 2015-07-10 11:51 UTC (permalink / raw
To: Giuseppe Barba; +Cc: linux-iio@vger.kernel.org
On Fri, Jul 10, 2015 at 2:42 PM, Giuseppe Barba
<giuseppe.barba@gmail.com> wrote:
> Hi,
>
> sorry I'm new in this list.
> I wold like to submit some patches to add support for new sensor.
> I'm not sure what repo I have to use for code rebasing. I've found:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>
> is it the correct one?
Yes. Please use 'testing' branch.
thanks,
Daniel.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Git repo to use for submitting patches
2015-07-10 11:51 ` Daniel Baluta
@ 2015-07-11 17:46 ` Jonathan Cameron
2015-07-14 9:07 ` Giuseppe Barba
0 siblings, 1 reply; 4+ messages in thread
From: Jonathan Cameron @ 2015-07-11 17:46 UTC (permalink / raw
To: Daniel Baluta, Giuseppe Barba; +Cc: linux-iio@vger.kernel.org
On 10/07/15 12:51, Daniel Baluta wrote:
> On Fri, Jul 10, 2015 at 2:42 PM, Giuseppe Barba
> <giuseppe.barba@gmail.com> wrote:
>> Hi,
>>
>> sorry I'm new in this list.
>> I wold like to submit some patches to add support for new sensor.
>> I'm not sure what repo I have to use for code rebasing. I've found:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>>
>> is it the correct one?
>
> Yes. Please use 'testing' branch.
Actually that's a bit risky unless you need something in it.
It does get rebased. I've been rather snowed under with day job stuff
last couple of weeks so haven't kept things as clean as they should be
but in theory:
1) togreg branch gets pushed out first as testing, but that's to let
the autobuilders play with it rather than as an official branch to
base anything on.
2) I fix up issues in testing found by the autobuilders and push it as
as the togreg branch.
3) When enough stuff has built up I send a pull request to Greg KH
and following that fastforward my tree.
Just to confuse things, fixes go via the fixes-togreg branch and make
it into the togreg branch only during the fastforward after Greg
has pulled in the previous patches to his tree.
So general principle is the togreg branch. Actually for new sensors
that are unlikely to interact much with recent patches, staging/staging-next
is also usually fine, or even use Linus' mainline tree.
Jonathan
>
> thanks,
> Daniel.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Git repo to use for submitting patches
2015-07-11 17:46 ` Jonathan Cameron
@ 2015-07-14 9:07 ` Giuseppe Barba
0 siblings, 0 replies; 4+ messages in thread
From: Giuseppe Barba @ 2015-07-14 9:07 UTC (permalink / raw
To: Jonathan Cameron; +Cc: Daniel Baluta, linux-iio@vger.kernel.org
Thanks. It's much more clear now.
2015-07-11 19:46 GMT+02:00 Jonathan Cameron <jic23@kernel.org>:
> On 10/07/15 12:51, Daniel Baluta wrote:
>> On Fri, Jul 10, 2015 at 2:42 PM, Giuseppe Barba
>> <giuseppe.barba@gmail.com> wrote:
>>> Hi,
>>>
>>> sorry I'm new in this list.
>>> I wold like to submit some patches to add support for new sensor.
>>> I'm not sure what repo I have to use for code rebasing. I've found:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>>>
>>> is it the correct one?
>>
>> Yes. Please use 'testing' branch.
> Actually that's a bit risky unless you need something in it.
> It does get rebased. I've been rather snowed under with day job stuff
> last couple of weeks so haven't kept things as clean as they should be
> but in theory:
>
> 1) togreg branch gets pushed out first as testing, but that's to let
> the autobuilders play with it rather than as an official branch to
> base anything on.
> 2) I fix up issues in testing found by the autobuilders and push it as
> as the togreg branch.
> 3) When enough stuff has built up I send a pull request to Greg KH
> and following that fastforward my tree.
>
> Just to confuse things, fixes go via the fixes-togreg branch and make
> it into the togreg branch only during the fastforward after Greg
> has pulled in the previous patches to his tree.
>
> So general principle is the togreg branch. Actually for new sensors
> that are unlikely to interact much with recent patches, staging/staging-next
> is also usually fine, or even use Linus' mainline tree.
>
> Jonathan
>>
>> thanks,
>> Daniel.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-07-14 9:07 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-10 11:42 Git repo to use for submitting patches Giuseppe Barba
2015-07-10 11:51 ` Daniel Baluta
2015-07-11 17:46 ` Jonathan Cameron
2015-07-14 9:07 ` Giuseppe Barba
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.