[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <260a005d-a1bb-48d7-89ec-ed1b6b151b4a@stanley.mountain>
Date: Tue, 22 Apr 2025 11:04:13 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Hardevsinh Palaniya <hardevsinh.palaniya@...iconsignals.io>
Cc: andy@...nel.org, sakari.ailus@...ux.intel.com,
Hans de Goede <hdegoede@...hat.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
linux-staging@...ts.linux.dev
Subject: Re: [PATCH 2/2] media: atomisp: Remove unused
atomisp_compat_ioctl32() declaration
On Fri, Apr 18, 2025 at 12:48:18PM +0530, Hardevsinh Palaniya wrote:
> Since its definition was deleted in a previous patch[1]
> and there are no remaining users of this function in
> the codebase.
>
> Link[1]:https://lore.kernel.org/linux-media/20210614103409.3154127-7-arnd@kernel.org/
Instead of a link to lore it should be:
The atomisp_compat_ioctl32() function was deleted in commit b4c650f1af68
("media: atomisp: remove compat_ioctl32 code") so delete the declaration
from the header.
Please don't say "it's" to refer to something mentioned in the subject.
When people are writing commit messages they sometimes treat the subject
as the first sentence of the commit message but the subject and the body
of the commit message should make sense independently. Look at the lore
link you posted above. Can you even find the subject? Most of the time
when people see a link to lore they'll just read the body of the email.
regards,
dan carpenter
Powered by blists - more mailing lists