All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>
Cc: outreachy@lists.linux.dev, mchehab@kernel.org,
	gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media:av7110:av7110_av.c remove blank line
Date: Tue, 29 Mar 2022 13:10:21 -0700	[thread overview]
Message-ID: <20220329201021.GA1171096@alison-desk> (raw)
In-Reply-To: <20220329190133.6243-1-eng.alaamohamedsoliman.am@gmail.com>

On Tue, Mar 29, 2022 at 09:01:33PM +0200, Alaa Mohamed wrote:
> according to checkpatch.pl results
> "CHECK: Please don't use multiple blank lines"
> after lines 73 and 78 ,I removed the blank lines
> 
> Signed-off-by: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>
> ---
>  drivers/staging/media/av7110/av7110_av.c | 2 --

Hi Alaa,

We are not taking cleanup patches in drivers/staging/media.
It's documented in here https://kernelnewbies.org/Outreachyfirstpatch
and I will repost the restriction on this list as the discussion
occurred a few days before the contribution period began.

If you look at the git history on this file, you'll see it is
on it's way out of the kernel, not on it's way in!

Please look at my feedback to Rebecca and Sevinj recent checkpatch
cleanups as guidance for your next (non-media) cleanup patch.

Thanks!
Alison





>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/staging/media/av7110/av7110_av.c b/drivers/staging/media/av7110/av7110_av.c
> index 91f4866c7e59..1544f120e8b1 100644
> --- a/drivers/staging/media/av7110/av7110_av.c
> +++ b/drivers/staging/media/av7110/av7110_av.c
> @@ -70,12 +70,10 @@
>  #define PIECE_RATE	 0x40
>  #define SEAM_SPLICE	 0x20
>  
> -
>  static void p_to_t(u8 const *buf, long int length, u16 pid,
>  		   u8 *counter, struct dvb_demux_feed *feed);
>  static int write_ts_to_decoder(struct av7110 *av7110, int type, const u8 *buf, size_t len);
>  
> -
>  int av7110_record_cb(struct dvb_filter_pes2ts *p2t, u8 *buf, size_t len)
>  {
>  	struct dvb_demux_feed *dvbdmxfeed = (struct dvb_demux_feed *) p2t->priv;
> -- 
> 2.35.1
> 
> 

      reply	other threads:[~2022-03-29 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 19:01 [PATCH] media:av7110:av7110_av.c remove blank line Alaa Mohamed
2022-03-29 20:10 ` Alison Schofield [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=20220329201021.GA1171096@alison-desk \
    --to=alison.schofield@intel.com \
    --cc=eng.alaamohamedsoliman.am@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=outreachy@lists.linux.dev \
    /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.