From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Lee Jones <lee@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v1 1/1] mfd: vexpress-sysreg: Fix resource compound literal assignments
Date: Mon, 14 Nov 2022 11:37:44 +0200 [thread overview]
Message-ID: <Y3IMaHg3Nbp1R5Zi@smile.fi.intel.com> (raw)
In-Reply-To: <Y3IECjcu4IjHySnA@kroah.com>
On Mon, Nov 14, 2022 at 10:02:02AM +0100, Greg Kroah-Hartman wrote:
> On Sun, Nov 13, 2022 at 09:10:27PM +0200, Andy Shevchenko wrote:
> > Since DEFINE_RES_*() macros were converted to provide a compound literal
> > the user doesn't need to repeat it. Moreover, it may not be compiled.
> >
> > Fixes: 9c973ce7f9cf ("resource: Convert DEFINE_RES_NAMED() to be compound literal")
>
> Wrong git id, I have no idea where that came from :(
Pfhh... I think it's my local one since it was never in Linux Next and
I forgot to specify your branch explicitly.
> I'll go fix this up...
Thank you!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-14 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 19:10 [PATCH v1 1/1] mfd: vexpress-sysreg: Fix resource compound literal assignments Andy Shevchenko
2022-11-14 9:02 ` Greg Kroah-Hartman
2022-11-14 9:37 ` Andy Shevchenko [this message]
2022-11-14 10:07 ` Sudeep Holla
2022-11-14 11:06 ` Lee Jones
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=Y3IMaHg3Nbp1R5Zi@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lkp@intel.com \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@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