linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com>
Cc: johan@kernel.org, elder@kernel.org,
	linux-staging@lists.linux.dev, greybus-dev@lists.linaro.org
Subject: Re: [PATCH 01/13] staging: greybus: Remove completed GPIO conversion TODO item
Date: Mon, 24 Nov 2025 17:38:43 +0100	[thread overview]
Message-ID: <2025112425-jeeringly-squeezing-afaa@gregkh> (raw)
In-Reply-To: <20251117181818.118139-2-ayaanmirzabaig85@gmail.com>

On Mon, Nov 17, 2025 at 11:48:06PM +0530, Ayaan Mirza Baig wrote:
> Signed-off-by: Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com>
> ---
>  drivers/staging/greybus/TODO | 3 ---
>  1 file changed, 3 deletions(-)

For obvious reasons I can't take a patch without any changelog text
(hint, you don't want me to do that either...)

thanks,

greg k-h

  reply	other threads:[~2025-11-24 16:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 18:18 [PATCH 00/13] staging: greybus: cleanup, FIXME removals, and driver correctness fixes Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 01/13] staging: greybus: Remove completed GPIO conversion TODO item Ayaan Mirza Baig
2025-11-24 16:38   ` Greg KH [this message]
2025-11-17 18:18 ` [PATCH 02/13] staging: greybus: pwm: move activation into pwm apply and remove request() Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 03/13] staging: greybus: remove empty TODO file Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 04/13] staging: greybus: audio: remove obsolete INPUT_PROP_NO_DUMMY_RELEASE FIXME Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 05/13] staging: greybus: audio: remove obsolete FIXME and document topology ownership Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 06/13] staging: greybus: bootrom: remove obsolete FIXME about SVC parallel event handling Ayaan Mirza Baig
2025-11-18 16:00   ` Johan Hovold
2025-11-17 18:18 ` [PATCH 07/13] staging: greybus: bootrom: remove obsolete FIXME around firmware filename logging Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 08/13] staging: greybus: fw-core: remove obsolete S2 Loader runtime PM FIXME Ayaan Mirza Baig
2025-11-18 16:01   ` Johan Hovold
2025-11-17 18:18 ` [PATCH 09/13] staging: greybus: loopback: remove incorrect FIXME about async wait Ayaan Mirza Baig
2025-11-17 18:18 ` [PATCH 10/13] staging: greybus: raw: handle disconnect while chardev is open Ayaan Mirza Baig
2025-11-18  4:04   ` Abdun Nihaal
2025-11-17 18:18 ` [PATCH 11/13] staging: greybus: uart: clear unsupported termios bits Ayaan Mirza Baig
2025-11-18 15:57   ` Johan Hovold
2025-11-17 18:18 ` [PATCH 12/13] staging: greybus: usb: validate hub control response length Ayaan Mirza Baig
2025-11-18 16:06   ` Johan Hovold
2025-11-17 18:18 ` [PATCH 13/13] staging: greybus: usb: remove obsolete FIXME about bridged-PHY support Ayaan Mirza Baig
2025-11-18 16:04   ` Johan Hovold
2025-11-18 16:11 ` [PATCH 00/13] staging: greybus: cleanup, FIXME removals, and driver correctness fixes Johan Hovold
2025-11-18 18:36   ` Ayaan Mirza Baig

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=2025112425-jeeringly-squeezing-afaa@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ayaanmirzabaig85@gmail.com \
    --cc=elder@kernel.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-staging@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).