From: DEEPAK VARMA <mh12gx2825@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
daniel.baluta@gmail.com, kieran.bingham@ideasonboard.com,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] media: staging/intel-ipu3: Remove extra blank lines
Date: Wed, 25 Mar 2020 23:10:28 +0530 [thread overview]
Message-ID: <20200325174027.GB28246@deeUbuntu> (raw)
In-Reply-To: <20200325072839.GA22460@kekkonen.localdomain>
On Wed, Mar 25, 2020 at 09:28:39AM +0200, Sakari Ailus wrote:
> Deepak,
>
> On Wed, Mar 25, 2020 at 01:08:05AM +0530, DEEPAK VARMA wrote:
> > On Mon, Mar 23, 2020 at 09:10:25AM +0200, Sakari Ailus wrote:
> > > Hi Deepak,
> > >
> > > On Mon, Mar 23, 2020 at 02:30:10AM +0530, Deepak R Varma wrote:
> > > > Remove extra blank lines from the code blocks.
> > > >
> > > > Signed-off-by: Deepak R Varma <mh12gx2825@gmail.com>
> > >
> > > Thanks for the patches. They seem fine to me, but could you send them to
> > > the linux-media list, please? That's where the media patches are reviewed,
> > > including the staging tree.
> > >
> > Hello Sakari,
> > Thank you for your comments. There are 2 patches for ipu3 that are
> > reviewed, but yet to be accepted by Greg. A couple of them have already
> > been accepted in the recent past.
> >
> > Do you want me to forward the current open patches list OR all the past
> > patches as well OR just the future ones?
>
> Unmerged patches and future ones, please.
Sure, I will do. Thank you.
Deepak.
>
> --
> Kind regards,
>
> Sakari Ailus
next prev parent reply other threads:[~2020-03-25 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 21:00 [PATCH] media: staging/intel-ipu3: Remove extra blank lines Deepak R Varma
2020-03-23 0:50 ` [Outreachy kernel] " Stefano Brivio
2020-03-23 7:10 ` Sakari Ailus
2020-03-24 19:38 ` DEEPAK VARMA
2020-03-25 7:28 ` Sakari Ailus
2020-03-25 17:40 ` DEEPAK VARMA [this message]
2020-03-25 20:56 Deepak R Varma
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=20200325174027.GB28246@deeUbuntu \
--to=mh12gx2825@gmail.com \
--cc=daniel.baluta@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=mchehab@kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sakari.ailus@linux.intel.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.