From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH 0/3] staging: media: cleanup
Date: Tue, 6 Mar 2018 09:03:54 -0800 [thread overview]
Message-ID: <20180306170354.GA19252@kroah.com> (raw)
In-Reply-To: <a814ccac-7afb-4ab0-a5b0-c6c4a4330485@googlegroups.com>
On Tue, Mar 06, 2018 at 08:18:27AM -0800, Arushi Singhal wrote:
>
>
> On Sunday, March 4, 2018 at 9:24:15 PM UTC+5:30, Julia Lawall wrote:
> >
> >
> >
> > On Sun, 4 Mar 2018, Arushi Singhal wrote:
> >
> > > Spellcheck the comments.
> > > Remove the repeated, consecutive words with single word.
> >
> > For the series:
> > Acked-by: Julia Lawall <julia....@lip6.fr <javascript:>>
> >
> > But please look out for things to change in the code, not just in the
> > comments.
> >
> > Hello Greg
>
> This is patch series is not Added.
I can not parse this :(
patches for drivers/staging/media/ go through the maintainer of that
tree, not me, if that is what you are concerned about.
thanks,
greg k-h
prev parent reply other threads:[~2018-03-06 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 15:48 [PATCH 0/3] staging: media: cleanup Arushi Singhal
2018-03-04 15:48 ` Arushi Singhal
2018-03-04 15:48 ` [PATCH 1/3] staging: media: Replace "be be" with "be" Arushi Singhal
2018-03-04 15:48 ` Arushi Singhal
2018-03-04 15:48 ` [PATCH 2/3] staging: media: Replace "cant" with "can't" Arushi Singhal
2018-03-04 15:48 ` Arushi Singhal
2018-03-04 15:48 ` [PATCH 3/3] staging: media: Replace "dont" with "don't" Arushi Singhal
2018-03-04 15:48 ` Arushi Singhal
2018-03-04 15:54 ` [Outreachy kernel] [PATCH 0/3] staging: media: cleanup Julia Lawall
2018-03-04 15:54 ` Julia Lawall
2018-03-06 16:18 ` Arushi Singhal
2018-03-06 17:03 ` Greg KH [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=20180306170354.GA19252@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arushisinghal19971997@gmail.com \
--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.