From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: holzheu@linux.vnet.ibm.com
Cc: kosaki.motohiro@jp.fujitsu.com,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
James Bottomley <James.Bottomley@suse.de>,
linux-scsi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] strstrip incorrectly marked __must_check
Date: Tue, 24 Nov 2009 17:55:44 +0900 (JST) [thread overview]
Message-ID: <20091124175338.AFB6.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1258981499.11269.6.camel@holzheu-laptop>
> Hi,
>
> I have several places in my code where the new __must_check of strstrip
> will introduce unnecessary dummy variables to avoid the warnings.
>
> Therefore I would like to have the suggested new strim() or
> strstip_tail() function. Any chance to have this upstream soon?
strim() is in mmotm now. I expect it will merge mainline soon.
Thanks.
>
> Michael
>
> On Wed, 2009-11-04 at 04:58 +0900, KOSAKI Motohiro wrote:
> > 2009/11/4 Alan Cox <alan@lxorguk.ukuu.org.uk>:
> > >> static inline void strsrip_tail(char *str)
> > >> {
> > >> char *x __used;
> > >> x = strstrip(str);
> > >> }
> > >
> > > Bikeshed time but its cleaner to do
> > >
> > > static inline __must_check void strstrip(char *str)
> > > {
> > > return strim(str);
> > > }
> > >
> > > and make strim() the old strstrip function without the check requirement
> >
> > Okey...
> >
> > [quick hack and compile check]
> >
> > done :)
> > sorry for attached file. I'm under poor mail environment now.
>
next prev parent reply other threads:[~2009-11-24 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 18:38 [PATCH] strstrip incorrectly marked __must_check James Bottomley
2009-11-03 18:59 ` Andrew Morton
2009-11-03 19:04 ` Matthew Wilcox
2009-11-03 19:06 ` KOSAKI Motohiro
2009-11-03 19:10 ` Alan Cox
2009-11-03 19:11 ` James Bottomley
2009-11-03 19:10 ` James Bottomley
2009-11-03 19:12 ` Alan Cox
2009-11-03 19:58 ` KOSAKI Motohiro
2009-11-23 13:04 ` Michael Holzheu
2009-11-24 8:55 ` KOSAKI Motohiro [this message]
2009-11-24 9:09 ` Michael Holzheu
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=20091124175338.AFB6.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox