mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: mathieu.poirier@linaro.org, coresight@lists.linaro.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] coresight changes for v5.18
Date: Thu, 10 Mar 2022 22:44:11 +0100	[thread overview]
Message-ID: <YipxKx+P7Dyc70vS@kroah.com> (raw)
In-Reply-To: <20220303230301.255049-1-suzuki.poulose@arm.com>

On Thu, Mar 03, 2022 at 11:03:01PM +0000, Suzuki K Poulose wrote:
> Hi Greg
> 
> Please find the pull request for coresight subsystem for v5.18.
> 
> Suzuki
> 
> The following changes since commit dfd42facf1e4ada021b939b4e19c935dcdd55566:
> 
>   Linux 5.17-rc3 (2022-02-06 12:20:50 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v5.18
> 
> for you to fetch changes up to b54f53bc11a584713f79a704c70c488489f524b8:
> 
>   coresight: Drop unused 'none' enum value for each component (2022-02-28 09:51:40 -0700)

I have the following errors when pulling this tree and having the
scripts check the commits:

Commit 5340bf5df9d2 ("coresight: syscfg: Fix memleak on registration failure in cscfg_create_device")
	committer Signed-off-by missing
	author email:    linmq006@gmail.com
	committer email: suzuki.poulose@arm.com
	Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
	Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

Commit 91a2f2941df2 ("coresight: Fix TRCCONFIGR.QE sysfs interface")
	committer Signed-off-by missing
	author email:    james.clark@arm.com
	committer email: suzuki.poulose@arm.com
	Signed-off-by: James Clark <james.clark@arm.com>
	Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

Commit 7f4cd3375906 ("coresight: trbe: Work around the trace data corruption")
	committer Signed-off-by missing
	author email:    anshuman.khandual@arm.com
	committer email: suzuki.poulose@arm.com
	Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
	Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

Commit 0ecf2c747437 ("coresight: trbe: Work around the invalid prohibited states")
	committer Signed-off-by missing
	author email:    anshuman.khandual@arm.com
	committer email: suzuki.poulose@arm.com
	Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
	Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

Commit 8b6927d0adad ("coresight: trbe: Work around the ignored system register writes")
	committer Signed-off-by missing
	author email:    anshuman.khandual@arm.com
	committer email: suzuki.poulose@arm.com
	Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
	Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>


What went wrong???

linux-next didn't complain about this already?

greg k-h

  reply	other threads:[~2022-03-10 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 23:03 Suzuki K Poulose
2022-03-10 21:44 ` Greg KH [this message]
2022-03-11  0:09   ` Mathieu Poirier
2022-03-11 10:25     ` Suzuki Kuruppassery Poulose
2022-03-11 10:45 ` [GIT PULL] [v2] coresight: Changes " Suzuki K Poulose
2022-03-18 11:49   ` Greg KH

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=YipxKx+P7Dyc70vS@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=coresight@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=suzuki.poulose@arm.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®