All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Anushka Badhe <anushkabadhe@gmail.com>
Cc: andriy.shevchenko@intel.com, andy@kernel.org, hansg@kernel.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-staging@lists.linux.dev, mchehab@kernel.org,
	sakari.ailus@linux.intel.com
Subject: Re: [PATCH v2] staging: atomisp: pci: fix block comment style and merge split declaration
Date: Wed, 25 Mar 2026 09:45:30 +0100	[thread overview]
Message-ID: <2026032514-floral-preachy-bdb4@gregkh> (raw)
In-Reply-To: <20260324180821.42084-1-anushkabadhe@gmail.com>

On Tue, Mar 24, 2026 at 11:38:21PM +0530, Anushka Badhe wrote:
> Signed-off-by: Anushka Badhe <anushkabadhe@gmail.com>
> ---
> Changes in v2:
> - Fix block comment style (move closing */ to its own line)
> - Merge split GP_TIMER_BASE declaration onto a single line
> 
> Checked the rest of the file for similar issues; no others found.
> 
> Thank you so much for your guidance on improving the patch.

For obvious reasons, we can't take patches without any changelog text.

thanks,

greg k-h

  parent reply	other threads:[~2026-03-25  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24  8:10 [PATCH] staging: atomisp: pci: remove leading whitespace at the start of the line Anushka Badhe
2026-03-24 11:50 ` Andy Shevchenko
2026-03-24 11:51   ` Andy Shevchenko
2026-03-24 18:08     ` [PATCH v2] staging: atomisp: pci: fix block comment style and merge split declaration Anushka Badhe
2026-03-24 19:43       ` [PATCH v3] staging: media: " Anushka Badhe
2026-03-25 12:08         ` Andy Shevchenko
2026-03-25 13:24           ` [PATCH v4] staging: media: atomisp: pci: fix split GP_TIMER_BASE declaration Anushka Badhe
2026-03-26 10:48             ` Andy Shevchenko
2026-03-25  8:45       ` Greg KH [this message]
2026-03-25  9:12         ` [PATCH v2] staging: atomisp: pci: fix block comment style and merge split declaration Anushka B

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=2026032514-floral-preachy-bdb4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=anushkabadhe@gmail.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --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.