mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Pierre Gondois <pierre.gondois@arm.com>,
	Yong-Xuan Wang <yongxuan.wang@sifive.com>,
	Vincent Chen <vincent.chen@sifive.com>,
	Greentime Hu <greentime.hu@sifive.com>,
	linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v2 1/1] drivers: base: cacheinfo: fix shared_cpu_map
Date: Fri, 20 Jan 2023 12:59:12 +0100	[thread overview]
Message-ID: <Y8qCEK1yCPtbn7dl@kroah.com> (raw)
In-Reply-To: <20230120113155.nsq3ufwlel3lznfl@bogus>

On Fri, Jan 20, 2023 at 11:31:55AM +0000, Sudeep Holla wrote:
> Hi Greg,
> 
> On Fri, Jan 20, 2023 at 12:27:26PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Dec 21, 2022 at 10:00:39AM +0100, Pierre Gondois wrote:
> 
> [...]
> 
> > >
> > > It seems there are 2 ';' above (same in the block below).
> >
> > Yes, the kernel test robot complains about this as well.
> >
> > It needs to be fixed before this change can be accepted.
> >
> 
> Just FYI, v3 and v4 was posted and I have pulled v4 which includes all
> the suggested changes. I will send a pull request with all cacheinfo and
> associated changes later today. They have been in the next for a while, need
> to tag them and send it to you.

Ah, good, sorry, I missed that.  Am catching up on old patches in my
queue...

  reply	other threads:[~2023-01-20 11:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 10:51 [PATCH v2 0/1] " Yong-Xuan Wang
2022-12-19 10:51 ` [PATCH v2 1/1] " Yong-Xuan Wang
2022-12-21  9:00   ` Pierre Gondois
2023-01-20 11:27     ` Greg Kroah-Hartman
2023-01-20 11:31       ` Sudeep Holla
2023-01-20 11:59         ` Greg Kroah-Hartman [this message]
2022-12-24 17:57   ` kernel test robot

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=Y8qCEK1yCPtbn7dl@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=greentime.hu@sifive.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.gondois@arm.com \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=vincent.chen@sifive.com \
    --cc=yongxuan.wang@sifive.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

all inboxes | Powered by JetHome®