From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Bergh <bergh.jonathan@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Roshan Khatri <topofeverest8848@gmail.com>,
Dipendra Khadka <kdipendra88@gmail.com>,
Sergio de Almeida Cipriano Junior <sergiosacj@riseup.net>,
Kent Overstreet <kent.overstreet@linux.dev>,
Kartik Kulkarni <kartik.koolks@gmail.com>,
Kathara Sasikumar <katharasasikumar007@gmail.com>,
Tchadel Icard <hello@tchadelicard.fr>,
Kate Hsuan <hpa@redhat.com>,
Colin Ian King <colin.i.king@gmail.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 1/1] media: atomisp: Remove License information boilerplate
Date: Mon, 23 Sep 2024 14:08:04 +0300 [thread overview]
Message-ID: <ZvFMFO3EjmV0BFp5@smile.fi.intel.com> (raw)
In-Reply-To: <20240923105539.3569110-1-andriy.shevchenko@linux.intel.com>
On Mon, Sep 23, 2024 at 01:53:06PM +0300, Andy Shevchenko wrote:
> We have the respective SPDX identifiers that are already being applied
> to the files in question. Remove the License information boilerplate.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>
> Here to fix one of the missed TODO item before moving from staging.
> This depends on 20240923085652.3457117-1-andriy.shevchenko@linux.intel.com.
> But can be applied before that (it's trivial to adjust).
Also worth to mention that this reduces a burden with all scripts running over
the driver code base, besides the improving the build performance (when it
makes files dropped by page size boundary, meaning one less page to map during
compilation) and reduced all Git operations for the developers.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-23 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 10:53 [PATCH v1 1/1] media: atomisp: Remove License information boilerplate Andy Shevchenko
2024-09-23 11:08 ` Andy Shevchenko [this message]
2024-11-04 11:57 ` Hans de Goede
2024-11-04 12:30 ` Andy Shevchenko
2024-11-04 12:51 ` Hans de Goede
2024-11-04 13:11 ` Andy Shevchenko
2024-11-07 11:32 ` Mauro Carvalho Chehab
2024-11-07 11:42 ` Mauro Carvalho Chehab
2024-11-07 11:45 ` Hans de Goede
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=ZvFMFO3EjmV0BFp5@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bergh.jonathan@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hello@tchadelicard.fr \
--cc=hpa@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kartik.koolks@gmail.com \
--cc=katharasasikumar007@gmail.com \
--cc=kdipendra88@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lorenzo.stoakes@oracle.com \
--cc=mchehab@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sergiosacj@riseup.net \
--cc=topofeverest8848@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox