public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Umang Jain <umang.jain@ideasonboard.com>
To: Stefan Wahren <wahrenst@gmx.net>,
	linux-staging@lists.linux.dev,
	linux-rpi-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Dan Carpenter <error27@gmail.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	"Ricardo B . Marliere" <ricardo@marliere.net>
Subject: Re: [PATCH v3 1/4] staging: vc04_services: Drop vchiq_log_error() in favour of dev_err
Date: Thu, 7 Dec 2023 14:11:36 +0530	[thread overview]
Message-ID: <855cd4ee-86db-ca46-ce91-17303941ff82@ideasonboard.com> (raw)
In-Reply-To: <3920385c-3c10-471a-ba82-8e48ba34f6a5@gmx.net>

Hi Stefan

On 12/7/23 3:04 AM, Stefan Wahren wrote:
> Hi Umang,
>
> Am 06.12.23 um 06:27 schrieb Umang Jain:
>> Hi Stefan
>>
>> On 12/6/23 1:02 AM, Stefan Wahren wrote:
>>> Hi Umang,
>>>
>>> Am 05.12.23 um 09:41 schrieb Umang Jain:
>>>> Drop vchiq_log_error() macro which wraps dev_dbg(). Introduce the 
>>>> usage
>>>> of dev_err() directly.
>>> sorry, i missed to review the last change. So the change won't be that
>>> trivial.
>>
>> All the changes you said are valid and I have taken a note of it.
>>
>> However, I think it would best that if we can address them in a
>> separate series on top of this (and I will do it). It would seem to be
>> streamlined on top of this.
> i would address the comments as separate patches and then finally
> convert the trivial rest with such a patch within one series. This
> avoids unnecessary changes and reviewes. But that's just my opinion.
>

Series is merged by Greg KH (Thank you).

Do you have more comments on 3/4 and 4/4 or are they waiting on your 
review queue. Let me know so that I can prepare a follow up series in 
-one- go.

thanks!
> Best regards


  reply	other threads:[~2023-12-07  8:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  8:41 [PATCH v3 0/4] staging: vc04_services: Drop custom logging Umang Jain
2023-12-05  8:41 ` [PATCH v3 1/4] staging: vc04_services: Drop vchiq_log_error() in favour of dev_err Umang Jain
2023-12-05 19:32   ` Stefan Wahren
2023-12-06  5:27     ` Umang Jain
2023-12-06 21:34       ` Stefan Wahren
2023-12-07  8:41         ` Umang Jain [this message]
2023-12-07 22:28           ` Stefan Wahren
2023-12-07  2:39       ` Greg Kroah-Hartman
2023-12-05  8:41 ` [PATCH v3 2/4] staging: vc04_services: Drop vchiq_log_warning() in favour of dev_warn Umang Jain
2023-12-05 19:37   ` Stefan Wahren
2023-12-05  8:41 ` [PATCH v3 3/4] staging: vc04_services: Drop vchiq_log_trace() in favour of dev_dbg Umang Jain
2023-12-08 12:08   ` Stefan Wahren
2023-12-09  6:27     ` Dan Carpenter
2023-12-09  9:33       ` Stefan Wahren
2023-12-05  8:41 ` [PATCH v3 4/4] staging: vc04_services: Drop vchiq_log_debug() " Umang Jain
2023-12-08 13:00   ` Stefan Wahren

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=855cd4ee-86db-ca46-ce91-17303941ff82@ideasonboard.com \
    --to=umang.jain@ideasonboard.com \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=ricardo@marliere.net \
    --cc=stefan.wahren@i2se.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