From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: Enable module aliases for vio on sparc/sparc64
Date: Thu, 14 Apr 2016 13:30:45 +0000 [thread overview]
Message-ID: <20160414133045.GA5847@ravnborg.org> (raw)
In-Reply-To: <570B52AE.8080603@physik.fu-berlin.de>
Hi Adrian.
> >> Date: Thu, 14 Apr 2016 01:16:14 +0200
> >> Subject: [PATCH 1/2] sparc: Implement and wire up modalias_show for vio.
> >
> > It would be nice if you could add here the effect this patch has - that
> > it fixes the debian installer.
>
> Hmm, I'm not sure whether this belongs here. I thought it was obvious
> what these two changes are for due to the canonical function names.
Just a suggestion - skip it as you prefer.
> >> +static ssize_t modalias_show(struct device *dev, struct device_attribute *attr,
> >> + char *buf)
> > Please use tabs and the appropriate number of spaces to indent.
>
> I used the same indentation that is used for modalias_show in
> arch/powerpc/kernel/vio.c but I wasn't sure what the proper
> indentation would be in this case.
>
> Can you suggest the right indentation?
You shall uses tabs and the necessary number of spaces so the
arguments are aligned with the first argument.
So the alignment is fine - just replace preceeding spaces with tabs.
Like this:
static ssize_t modalias_show(struct device *dev, struct device_attribute *attr,
char *buf)
Three leading tabs, then 5 spaces.
> >
> > At sparclinux we usually submit one patch per mail.
> > And patches which are specific for either sparc32 or sparc64 are prefixed so.
> >
> > Like this
> > [PATCH 1/2] sparc64: ...
> > [PATCH 2/2] sparc64: ...
>
> Yeah, I know. I can re-send them with git send-email if that's desired,
> I just wanted to avoid cluttering the discussion too much.
It is my understanding that this is simpler for davem when applying patches.
But maybe patchwork makes things easier with respect to attached patches.
Anyway - if you follow the normal pattern then everything should just works.
Most important, document what was changed from v1 to v2 -
so when davem and other looks at this they know what was changed.
Sam
next prev parent reply other threads:[~2016-04-14 13:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 7:30 Enable module aliases for vio on sparc/sparc64 John Paul Adrian Glaubitz
2016-04-11 19:04 ` David Miller
2016-04-12 9:29 ` John Paul Adrian Glaubitz
2016-04-13 15:33 ` John Paul Adrian Glaubitz
2016-04-13 22:23 ` David Miller
2016-04-13 22:35 ` John Paul Adrian Glaubitz
2016-04-13 22:36 ` David Miller
2016-04-13 22:37 ` David Miller
2016-04-13 22:44 ` John Paul Adrian Glaubitz
2016-04-13 23:01 ` David Miller
2016-04-13 23:04 ` John Paul Adrian Glaubitz
2016-04-13 23:22 ` John Paul Adrian Glaubitz
2016-04-14 1:52 ` David Miller
2016-04-14 1:52 ` David Miller
2016-04-14 1:53 ` David Miller
2016-04-14 9:00 ` John Paul Adrian Glaubitz
2016-04-14 9:10 ` John Paul Adrian Glaubitz
2016-04-14 10:27 ` Sam Ravnborg
2016-04-14 10:52 ` John Paul Adrian Glaubitz
2016-04-14 13:30 ` Sam Ravnborg [this message]
2016-04-14 16:00 ` John Paul Adrian Glaubitz
2016-04-14 16:02 ` David Miller
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=20160414133045.GA5847@ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.