From: R Veera Kumar <vkor@vkten.in>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Re: I need feedback on my posted patches
Date: Thu, 19 Mar 2020 14:21:54 +0530 [thread overview]
Message-ID: <20200319085151.GE1723@tulip.local> (raw)
In-Reply-To: <20200319083600.GA3490824@kroah.com>
On Thu, Mar 19, 2020 at 09:36:00AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 19, 2020 at 01:52:54PM +0530, R Veera Kumar wrote:
> > On Thu, Mar 19, 2020 at 09:09:05AM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Mar 19, 2020 at 01:31:52PM +0530, R Veera Kumar wrote:
> > > > Hi,
> > > >
> > > > I posted patches on Saturday. But I did not got a msg from Greg
> > > > about they being accepted. Yesterday Greg posted that he has
> > > > seen all outreachy patches upto now. And if we do not get reply's
> > > > for the patches we should resend. So I resent it yesterday.
> > >
> > > What specific patches did you submit that you did not get a response on?
> > > I do not see any, but I might have missed some. What is the message id
> > > or subject lines?
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
> >
> > They are:
> >
> > Subject: [RESEND PATCH] staging: rtl8188eu: core: Correct a typo in a comment
> > Message-Id: <20200317233020.575-1-vkor@vkten.in>
> >
> > Subject: [RESEND PATCH] staging: rts5208: shorten long line in func call
> > Message-Id: <20200317235413.1656-1-vkor@vkten.in>
>
> I do not see any of these patches in my system at all.
>
> I would suggest resending all patches that you have that I have not
> applied as I am currently caught up on all pending outreachy patches.
>
Oh.
Perhaps the issue is I am sending email patches with
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CC: outreachy-kernel <outreachy-kernel@googlegroups.com>, others
I do not know but should I send all of them with To: field.
Greg, do you only read outreachy-kernel@googlegroups.com msgs for patch
lookup.
Veera
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2020-03-19 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 8:01 I need feedback on my posted patches R Veera Kumar
2020-03-19 8:09 ` Greg Kroah-Hartman
2020-03-19 8:22 ` [Outreachy kernel] " R Veera Kumar
2020-03-19 8:36 ` Greg Kroah-Hartman
2020-03-19 8:51 ` R Veera Kumar [this message]
2020-03-19 8:58 ` Julia Lawall
2020-03-19 8:59 ` Greg Kroah-Hartman
2020-03-19 11:17 ` R Veera Kumar
2020-03-19 12:15 ` Greg Kroah-Hartman
[not found] ` <alpine.DEB.2.21.2003190930420.3010@hadrien>
2020-03-19 8:39 ` R Veera Kumar
2020-03-19 8:42 ` Julia Lawall
2020-03-19 9:04 ` R Veera Kumar
2020-03-19 9:07 ` Julia Lawall
2020-03-19 8:11 ` [Outreachy kernel] " Julia Lawall
2020-03-19 8:20 ` R Veera Kumar
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=20200319085151.GE1723@tulip.local \
--to=vkor@vkten.in \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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.