Caught up on Outreachy patches

Caught up on Outreachy patches

[Greg KH]

Hi all,

I've now caught up on all submitted outreachy kernel patches.

So if you have not gotten an email from my automated patch scripts
saying your patch has been applied, consider it rejected or lost.
Please resend anything that you think is ready to be merged.

Note, I'm using my staging-testing branch of staging.git right now to
hold patches in.  I can't merge this to my staging-next to go into
linux-next until after 4.11-rc1 is out, in a little over a week.  If
anyone has any questions about this, please let me know.

thanks,

greg k-h

Re: Caught up on Outreachy patches

[SIMRAN SINGHAL]

[-- Attachment #1.1: Type: text/plain, Size: 1216 bytes --]



On Friday, February 24, 2017 at 11:23:23 PM UTC+5:30, gregkh wrote:
>
> Hi all, 
>
> I've now caught up on all submitted outreachy kernel patches. 
>
> So if you have not gotten an email from my automated patch scripts 
> saying your patch has been applied, consider it rejected or lost. 
> Please resend anything that you think is ready to be merged. 
>

    Greg, as for some of my patches I didn't get reply.
    So, now how am I supposed to send them i.e as next version
    of that patch or as a completely new patch.
   
    And those patches also include some patches which are acked by 
    Julia, so sending them as completely new patch seems pointless.
    
    So, I request you to please explain how we are supposed to send them
    and sorry for asking this, but can you please explain the reason of, if
    those patches are present in the mailing list then why you are calling
    them lost.
 

> Note, I'm using my staging-testing branch of staging.git right now to 
> hold patches in.  I can't merge this to my staging-next to go into 
> linux-next until after 4.11-rc1 is out, in a little over a week.  If 
> anyone has any questions about this, please let me know. 
>
> thanks, 
>
> greg k-h 
>

[-- Attachment #1.2: Type: text/html, Size: 1708 bytes --]

Re: [Outreachy kernel] Re: Caught up on Outreachy patches

[Julia Lawall]

[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]



On Fri, 24 Feb 2017, SIMRAN SINGHAL wrote:

>
>
> On Friday, February 24, 2017 at 11:23:23 PM UTC+5:30, gregkh wrote:
>       Hi all,
>
>       I've now caught up on all submitted outreachy kernel patches.
>
>       So if you have not gotten an email from my automated patch
>       scripts
>       saying your patch has been applied, consider it rejected or
>       lost.
>       Please resend anything that you think is ready to be merged.
>
>
>     Greg, as for some of my patches I didn't get reply.
>     So, now how am I supposed to send them i.e as next version
>     of that patch or as a completely new patch.
>    
>     And those patches also include some patches which are acked by 
>     Julia, so sending them as completely new patch seems pointless.
>     
>     So, I request you to please explain how we are supposed to send them
>     and sorry for asking this, but can you please explain the reason of, if
>     those patches are present in the mailing list then why you are calling
>     them lost.

It could be helpful to indicate which patches you are concerned about.

julia

>  
>       Note, I'm using my staging-testing branch of staging.git right
>       now to
>       hold patches in.  I can't merge this to my staging-next to go
>       into
>       linux-next until after 4.11-rc1 is out, in a little over a week.
>        If
>       anyone has any questions about this, please let me know.
>
>       thanks,
>
>       greg k-h
>
> --
> You received this message because you are subscribed to the Google Groups
> "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visithttps://groups.google.com/d/msgid/outreachy-kernel/605876fe-cfb0-4389-9ca9-
> aa88a3b4e1ea%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>

Re: [Outreachy kernel] Re: Caught up on Outreachy patches

[SIMRAN SINGHAL]

[-- Attachment #1.1: Type: text/plain, Size: 2351 bytes --]



On Saturday, February 25, 2017 at 2:18:13 AM UTC+5:30, Julia Lawall wrote:
>
>
>
> On Fri, 24 Feb 2017, SIMRAN SINGHAL wrote: 
>
> > 
> > 
> > On Friday, February 24, 2017 at 11:23:23 PM UTC+5:30, gregkh wrote: 
> >       Hi all, 
> > 
> >       I've now caught up on all submitted outreachy kernel patches. 
> > 
> >       So if you have not gotten an email from my automated patch 
> >       scripts 
> >       saying your patch has been applied, consider it rejected or 
> >       lost. 
> >       Please resend anything that you think is ready to be merged. 
> > 
> > 
> >     Greg, as for some of my patches I didn't get reply. 
> >     So, now how am I supposed to send them i.e as next version 
> >     of that patch or as a completely new patch. 
> >     
> >     And those patches also include some patches which are acked by  
> >     Julia, so sending them as completely new patch seems pointless. 
> >      
> >     So, I request you to please explain how we are supposed to send them 
> >     and sorry for asking this, but can you please explain the reason of, 
> if 
> >     those patches are present in the mailing list then why you are 
> calling 
> >     them lost. 
>
> It could be helpful to indicate which patches you are concerned about. 
>  
>
    https://groups.google.com/forum/#!topic/outreachy-kernel/2uHHwQmOHec 
 

> julia 
>
> >   
> >       Note, I'm using my staging-testing branch of staging.git right 
> >       now to 
> >       hold patches in.  I can't merge this to my staging-next to go 
> >       into 
> >       linux-next until after 4.11-rc1 is out, in a little over a week. 
> >        If 
> >       anyone has any questions about this, please let me know. 
> > 
> >       thanks, 
> > 
> >       greg k-h 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "outreachy-kernel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to outreachy-kern...@googlegroups.com <javascript:>. 
> > To post to this group, send email to outreach...@googlegroups.com 
> <javascript:>. 
> > To view this discussion on the web visithttps://
> groups.google.com/d/msgid/outreachy-kernel/605876fe-cfb0-4389-9ca9- 
> > aa88a3b4e1ea%40googlegroups.com. 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
> >


[-- Attachment #1.2: Type: text/html, Size: 4447 bytes --]

Re: [Outreachy kernel] Re: Caught up on Outreachy patches

[Julia Lawall]

[-- Attachment #1: Type: text/plain, Size: 4004 bytes --]



On Fri, 24 Feb 2017, SIMRAN SINGHAL wrote:

>
>
> On Saturday, February 25, 2017 at 2:18:13 AM UTC+5:30, Julia Lawall wrote:
>
>
>       On Fri, 24 Feb 2017, SIMRAN SINGHAL wrote:
>
>       >
>       >
>       > On Friday, February 24, 2017 at 11:23:23 PM UTC+5:30, gregkh
>       wrote:
>       >       Hi all,
>       >
>       >       I've now caught up on all submitted outreachy kernel
>       patches.
>       >
>       >       So if you have not gotten an email from my automated
>       patch
>       >       scripts
>       >       saying your patch has been applied, consider it rejected
>       or
>       >       lost.
>       >       Please resend anything that you think is ready to be
>       merged.
>       >
>       >
>       >     Greg, as for some of my patches I didn't get reply.
>       >     So, now how am I supposed to send them i.e as next version
>       >     of that patch or as a completely new patch.
>       >    
>       >     And those patches also include some patches which are
>       acked by 
>       >     Julia, so sending them as completely new patch seems
>       pointless.
>       >     
>       >     So, I request you to please explain how we are supposed to
>       send them
>       >     and sorry for asking this, but can you please explain the
>       reason of, if
>       >     those patches are present in the mailing list then why you
>       are calling
>       >     them lost.
>
>       It could be helpful to indicate which patches you are concerned
>       about.
>        
>
>     https://groups.google.com/forum/#!topic/outreachy-kernel/2uHHwQmOHec 

I think that in this case something strange happened, where Gargi Sharma
did part of your change after you.  I replied to her saying that the
change had already been done, and she agreed.  But Greg responded saying
that he didn't see the earlier patch, so he was going to go ahead and
apply hers.  So you can't resend the original patch, because at least part
of the change has already been made.  You made two changes: one for pBA
andone for skb.  To my recollection, she only changed skb, so you might be
able to resend the pBA part.  If that change has not already been done,
then a new patch would be fine.

julia


>  
>       julia
>
>       >  
>       >       Note, I'm using my staging-testing branch of staging.git
>       right
>       >       now to
>       >       hold patches in.  I can't merge this to my staging-next
>       to go
>       >       into
>       >       linux-next until after 4.11-rc1 is out, in a little over
>       a week.
>       >        If
>       >       anyone has any questions about this, please let me know.
>       >
>       >       thanks,
>       >
>       >       greg k-h
>       >
>       > --
>       > You received this message because you are subscribed to the
>       Google Groups
>       > "outreachy-kernel" group.
>       > To unsubscribe from this group and stop receiving emails from
>       it, send an
>       > email to outreachy-kern...@googlegroups.com.
>       > To post to this group, send email to
>       outreach...@googlegroups.com.
>       > To view this discussion on the webvisithttps://groups.google.com/d/msgid/outreachy-kernel/605876fe-cfb0-4389-
>       9ca9-
>       > aa88a3b4e1ea%40googlegroups.com.
>       > For more options, visit https://groups.google.com/d/optout.
>       >
>       >
>
> --
> You received this message because you are subscribed to the Google Groups
> "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visithttps://groups.google.com/d/msgid/outreachy-kernel/f0134e34-0536-4cd2-ae63-
> 84916b77d6f0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>

Re: [Outreachy kernel] Re: Caught up on Outreachy patches

[Greg KH]

On Fri, Feb 24, 2017 at 12:35:58PM -0800, SIMRAN SINGHAL wrote:
> 
> 
> On Friday, February 24, 2017 at 11:23:23 PM UTC+5:30, gregkh wrote:
> 
>     Hi all,
> 
>     I've now caught up on all submitted outreachy kernel patches.
> 
>     So if you have not gotten an email from my automated patch scripts
>     saying your patch has been applied, consider it rejected or lost.
>     Please resend anything that you think is ready to be merged.
> 
> 
> � � Greg, as for some of my patches I didn't get reply.
> � � So, now how am I supposed to send them i.e as next version
> � � of that patch or as a completely new patch.

Very odd quoting style, please fix up your email client to do this
properly.

Resend anything I missed as a new version of the patch, saying you have
fixed up whatever kept it from being accepted the first time (if I had
commented on it), or just a 'resend' if I happened to miss it.

But first rebase your patches on my staging-testing branch to ensure
that they do work properly, otherwise you are just wasting time redoing
something I will have to reject again :)

> � � And those patches also include some patches which are acked by�
> � � Julia, so sending them as completely new patch seems pointless.

Nope, that's just how it goes, but keep Julia's ack on it when you
resend.

> � � So, I request you to please explain how we are supposed to send them
> � � and sorry for asking this, but can you please explain the reason of, if
> � � those patches are present in the mailing list then why you are calling
> � � them lost.

I don't know, I need specifics here.  Did I say something about them, or
just ignore them completly?  Did I say something like "redo all of your
outstanding patches"?  Remember, I get over 1000 emails a day, and just
had to review over 500 patches submitted for the staging subsystem in
the past 5 days.  I can't remember anything specifically, and neither
could anyone else with that kind of workload :)

thanks,

greg k-h