From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Rikard Falkeborn <rikard.falkeborn@gmail.com>,
Robert Jones <rjones@gateworks.com>,
Tim Harvey <tharvey@gateworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mfd: gateworks-gsc: Constify static struct attribute_group
Date: Mon, 1 Mar 2021 22:11:53 +0100 [thread overview]
Message-ID: <YD1Ymbdxv0GCZchQ@rikard> (raw)
In-Reply-To: <20210301095645.GG641347@dell>
On Mon, Mar 01, 2021 at 09:56:45AM +0000, Lee Jones wrote:
> On Sun, 31 Jan 2021, Rikard Falkeborn wrote:
>
> > The only usage of attr_group is to pass its address to
> > sysfs_create_group() and sysfs_remove_group(), both which takes pointers
> > to const attribute_group structs. Make it const to allow the compiler to
> > put it in read-only memory.
> >
> > Done with the help of coccinelle.
> >
> > Signed-off-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>
> > ---
> > drivers/mfd/gateworks-gsc.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> These patches do not seem to be on LKML.
>
> Do you know if they were rejected for some reason?
>
I did not recieve any bounce or rejection emails. I have a vague memory
that I saw someone mentioning in another mail that there was some
problems with LKML and that patches were lost, but I can't find it now,
and I'm not sure if it was around the same time as these patches were
sent.
Should I resend the series?
/Rikard
next prev parent reply other threads:[~2021-03-02 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210131133644.8834-1-rikard.falkeborn@gmail.com>
[not found] ` <20210131133644.8834-2-rikard.falkeborn@gmail.com>
2021-03-01 9:56 ` [PATCH 1/3] mfd: gateworks-gsc: Constify static struct attribute_group Lee Jones
2021-03-01 21:11 ` Rikard Falkeborn [this message]
2021-03-02 9:34 ` 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=YD1Ymbdxv0GCZchQ@rikard \
--to=rikard.falkeborn@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjones@gateworks.com \
--cc=tharvey@gateworks.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