linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Phil Elwell <phil@raspberrypi.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Umang Jain <umang.jain@ideasonboard.com>,
	linux-staging@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	"Ricardo B . Marliere" <ricardo@marliere.net>
Subject: Re: [PATCH V2 0/3] staging: vchiq_arm: move state dump to debugfs
Date: Wed, 22 Nov 2023 12:23:00 +0000	[thread overview]
Message-ID: <2023112238-acting-removing-50bd@gregkh> (raw)
In-Reply-To: <8351ddaf-c63e-4527-809f-d002bd79ad14@gmx.net>

On Wed, Nov 22, 2023 at 01:17:07PM +0100, Stefan Wahren wrote:
> Hi Greg,
> 
> Am 29.10.23 um 13:48 schrieb Stefan Wahren:
> > Hello,
> > 
> > since recent discussion raised the question about the future of debugfs
> > for vchiq [1], i want to submit this cleanup patch series as part of the
> > discussion and a small Halloween present ;-)
> > 
> > Best regards
> > 
> > Changes in V2:
> > - rebase on top of current staging-next
> > - address suggestion from Laurent Pinchart in patch 1
> > - fix checkpatch issue (too long line) in patch 2
> > 
> > [1] - https://lore.kernel.org/lkml/7ea529c2-3da6-47df-9b09-28d4ab36c4ef@kadam.mountain/T/
> > 
> > Stefan Wahren (3):
> >    staging: vchiq_core: Make vchiq_dump_service_state static
> >    staging: vchiq_core: Shorten bulk TX/RX pending dump
> >    staging: vchiq_arm: move state dump to debugfs
> 
> should i resend incl. the received Reviewed-by tags?

No, just wait for me to catch up with staging patches.  Should be a week
or so...

tjhanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-11-22 12:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 12:48 [PATCH V2 0/3] staging: vchiq_arm: move state dump to debugfs Stefan Wahren
2023-10-29 12:48 ` [PATCH V2 1/3] staging: vchiq_core: Make vchiq_dump_service_state static Stefan Wahren
2023-10-29 23:44   ` Laurent Pinchart
2023-10-29 12:48 ` [PATCH V2 2/3] staging: vchiq_core: Shorten bulk TX/RX pending dump Stefan Wahren
2023-10-29 23:46   ` Laurent Pinchart
2023-10-29 12:48 ` [PATCH V2 3/3] staging: vchiq_arm: move state dump to debugfs Stefan Wahren
2023-10-29 15:03   ` Ricardo B. Marliere
2023-11-22 12:17 ` [PATCH V2 0/3] " Stefan Wahren
2023-11-22 12:23   ` Greg Kroah-Hartman [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=2023112238-acting-removing-50bd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=phil@raspberrypi.com \
    --cc=ricardo@marliere.net \
    --cc=umang.jain@ideasonboard.com \
    --cc=wahrenst@gmx.net \
    /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).