Skip to contentSkip to conversation

kgdb-next not pushed to Linus for 3.19

DISCUSSION Daniel Thompson 4 participants 5 messages Jan 6, 2015 – Jan 7, 2015

lore
Share & tools
lore
#0 lore raw

Hi Jason

I'm trying to figure out what to do with my long-outstanding kgdb/kdb patches in preparation for the 3.20 merge window.

As of now I have five pending patch sets some of which are well over six months old (and none have nay outstanding review comments).

When I raised this with you a couple of months ago, two of the patch sets did land in your kgdb-next tree. However nothing seems to have happened since then and I couldn't find any messages from you during the 3.19 merge window.

I'm afraid I don't know what else I need to do to progress things.

I do plan to do routine rebasing and resending of my patchsets but, based on the past experience, that seems unlikely to be enough to get the code delivered in 3.20.

Do you think I would be better sending these patches via someone else? In any case, advice would be very welcome.

Daniel.

#1 lore raw
Quoted 13 lines · Daniel Thompson

Hi Jason

I'm trying to figure out what to do with my long-outstanding kgdb/kdb patches in preparation for the 3.20 merge window.

As of now I have five pending patch sets some of which are well over six months old (and none have nay outstanding review comments).

When I raised this with you a couple of months ago, two of the patch sets did land in your kgdb-next tree. However nothing seems to have happened since then and I couldn't find any messages from you during the 3.19 merge window.

Quoted 8 lines

I'm afraid I don't know what else I need to do to progress things.

I do plan to do routine rebasing and resending of my patchsets but, based on the past experience, that seems unlikely to be enough to get the code delivered in 3.20.

Do you think I would be better sending these patches via someone else? In any case, advice would be very welcome.

Andrew?

I think Daniel's kgdb patches are bug fixes.

Can you please pick them up?

#2 lore raw
Quoted 20 lines · On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches <[email protected]> wrote:
Quoted 19 lines · Daniel Thompson

Hi Jason

I'm trying to figure out what to do with my long-outstanding kgdb/kdb patches in preparation for the 3.20 merge window.

As of now I have five pending patch sets some of which are well over six months old (and none have nay outstanding review comments).

When I raised this with you a couple of months ago, two of the patch sets did land in your kgdb-next tree. However nothing seems to have happened since then and I couldn't find any messages from you during the 3.19 merge window.

I'm afraid I don't know what else I need to do to progress things.

I do plan to do routine rebasing and resending of my patchsets but, based on the past experience, that seems unlikely to be enough to get the code delivered in 3.20.

Quoted 8 lines
Quoted 2 lines

Do you think I would be better sending these patches via someone else? In any case, advice would be very welcome.

Andrew?

I think Daniel's kgdb patches are bug fixes.

Can you please pick them up?

yup. Merging patches which are already in -next is a bit of a pain, but I'll cope.

Daniel, can you please resend everything in a nice clean coherent stream?

#3 lore raw
Quoted 26 lines · Andrew Morton
Quoted 24 lines · On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches <[email protected]> wrote:
Quoted 13 lines · Daniel Thompson

Hi Jason

I'm trying to figure out what to do with my long-outstanding kgdb/kdb patches in preparation for the 3.20 merge window.

As of now I have five pending patch sets some of which are well over six months old (and none have nay outstanding review comments).

When I raised this with you a couple of months ago, two of the patch sets did land in your kgdb-next tree. However nothing seems to have happened since then and I couldn't find any messages from you during the 3.19 merge window.

Quoted 8 lines

I'm afraid I don't know what else I need to do to progress things.

I do plan to do routine rebasing and resending of my patchsets but, based on the past experience, that seems unlikely to be enough to get the code delivered in 3.20.

Do you think I would be better sending these patches via someone else? In any case, advice would be very welcome.

Andrew?

Quoted 9 lines
Quoted 3 lines

I think Daniel's kgdb patches are bug fixes.

Can you please pick them up?

yup. Merging patches which are already in -next is a bit of a pain, but I'll cope.

Daniel, can you please resend everything in a nice clean coherent stream?

I did not mean to miss the merge window, but I ended up being out the majority of December -> yesterday.

Now that I am back, I don't think you have to burden Andrew here. I'll send a pull request for what is in kgdb-next since it is cleanups and fixes, and regression test anything else Daniel has left.

Cheers,
Jason.

#4 lore raw
Quoted 37 lines · Jason Wessel
Quoted 26 lines · Andrew Morton
Quoted 24 lines · On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches <[email protected]> wrote:
Quoted 13 lines · Daniel Thompson

Hi Jason

I'm trying to figure out what to do with my long-outstanding kgdb/kdb patches in preparation for the 3.20 merge window.

As of now I have five pending patch sets some of which are well over six months old (and none have nay outstanding review comments).

When I raised this with you a couple of months ago, two of the patch sets did land in your kgdb-next tree. However nothing seems to have happened since then and I couldn't find any messages from you during the 3.19 merge window.

Quoted 8 lines

I'm afraid I don't know what else I need to do to progress things.

I do plan to do routine rebasing and resending of my patchsets but, based on the past experience, that seems unlikely to be enough to get the code delivered in 3.20.

Do you think I would be better sending these patches via someone else? In any case, advice would be very welcome.

Andrew?

Quoted 9 lines
Quoted 3 lines

I think Daniel's kgdb patches are bug fixes.

Can you please pick them up?

yup. Merging patches which are already in -next is a bit of a pain, but I'll cope.

Daniel, can you please resend everything in a nice clean coherent stream?

Quoted 6 lines

I did not mean to miss the merge window, but I ended up being out the majority of December -> yesterday.

Now that I am back, I don't think you have to burden Andrew here. I'll send a pull request for what is in kgdb-next since it is cleanups and fixes, and regression test anything else Daniel has left.

Ok.

I'm working on the rebase-and-resends now.

Thanks.