linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@kernel.org
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Marc Zyngier <maz@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Felipe Balbi <balbi@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Scott Branden <sbranden@broadcom.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Ray Jui <rjui@broadcom.com>,
	coresight@lists.linaro.org, linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Trivial warning fixes
Date: Tue, 27 Oct 2020 10:51:55 +0200	[thread overview]
Message-ID: <20201027085157.1964906-1-balbi@kernel.org> (raw)

From: Felipe Balbi <balbi@kernel.org>

Hi,

here's a couple build warning fixes that I just caught with
allmodconfig on AArch64.

cheers

Felipe Balbi (2):
  hwtracing: coresight: add missing MODULE_LICENSE()
  irqchip: bcm2836: fix section mismatch warning

 drivers/hwtracing/coresight/coresight-core.c | 1 +
 drivers/irqchip/irq-bcm2836.c                | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.29.1


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

             reply	other threads:[~2020-10-27  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27  8:51 balbi [this message]
2020-10-27  8:51 ` [PATCH 1/2] hwtracing: coresight: add missing MODULE_LICENSE() balbi
2020-10-27 10:35   ` Suzuki K Poulose
2020-10-27 15:29   ` Mathieu Poirier
2020-10-27  8:51 ` [PATCH 2/2] irqchip: bcm2836: fix section mismatch warning balbi
2020-10-27  9:03   ` Marc Zyngier

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=20201027085157.1964906-1-balbi@kernel.org \
    --to=balbi@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=coresight@lists.linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=maz@kernel.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tglx@linutronix.de \
    /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).