From: 함명주 <myungjoo.ham@samsung.com>
To: anish kumar <anish198519851985@gmail.com>
Cc: 최찬우 <cw00.choi@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Extcon: Minor change in the declaration of cable_names
Date: Mon, 20 Aug 2012 06:56:39 +0000 (GMT) [thread overview]
Message-ID: <28057486.209671345445798709.JavaMail.weblogic@epml13> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1699 bytes --]
> From: anish kumar <anish198519851985@gmail.com>
>
> Instead of "const char **supported_cable" it is better to have
> it as "const char *const *supported_cable".
>
> Signed-off-by: anish kumar <anish198519851985@gmail.com>
Could you please elaborate on why it's better?
(Is this fixing the using the standard naming issue Mark mentioned before?)
Cheers!
MyungJoo
> ---
> include/linux/extcon.h | 2 +-
> include/linux/extcon/extcon-adc-jack.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/extcon.h b/include/linux/extcon.h
> index cdd4014..a6bcc29 100644
> --- a/include/linux/extcon.h
> +++ b/include/linux/extcon.h
> @@ -111,7 +111,7 @@ struct extcon_cable;
> struct extcon_dev {
> /* --- Optional user initializing data --- */
> const char *name;
> - const char **supported_cable;
> + const char *const *supported_cable;
> const u32 *mutually_exclusive;
>
> /* --- Optional callbacks to override class functions --- */
> diff --git a/include/linux/extcon/extcon-adc-jack.h b/include/linux/extcon/extcon-adc-jack.h
> index 20e9eef..f27f2e8 100644
> --- a/include/linux/extcon/extcon-adc-jack.h
> +++ b/include/linux/extcon/extcon-adc-jack.h
> @@ -60,7 +60,7 @@ struct adc_jack_pdata {
> /*
> * The last entry should be NULL
> */
> - const char **cable_names;
> + const char *const *cable_names;
> /* The last entry's state should be 0 */
> struct adc_jack_cond *adc_conditions;
>
> --
> 1.7.1
>
>
>
>
>
>
>
>
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2012-08-20 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 6:56 함명주 [this message]
2012-08-20 7:27 ` [PATCH] Extcon: Minor change in the declaration of cable_names anish kumar
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 8:19 anish kumar
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=28057486.209671345445798709.JavaMail.weblogic@epml13 \
--to=myungjoo.ham@samsung.com \
--cc=anish198519851985@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@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.