All of lore.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map()
Date: Mon, 30 Oct 2017 19:41:07 +0000	[thread overview]
Message-ID: <f306e5fb-e36b-0dae-d863-df57f7cd1ce4@users.sourceforge.net> (raw)
In-Reply-To: <CAMuHMdUH8NgkumbjjOZZrkbD2sdHfVzLwM47U4DUrVC0F7ojDw@mail.gmail.com>

>> Are you looking for a limitation of such source code search patterns?
> 
> Exactly.

Would you like to explain your view a bit more?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Rob Herring <robh@kernel.org>, Barry Song <baohua@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Linus Walleij <linus.walleij@linaro.org>,
	kernel-janitors@vger.kernel.org,
	Patrice Chotard <patrice.chotard@st.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map()
Date: Mon, 30 Oct 2017 20:41:07 +0100	[thread overview]
Message-ID: <f306e5fb-e36b-0dae-d863-df57f7cd1ce4@users.sourceforge.net> (raw)
In-Reply-To: <CAMuHMdUH8NgkumbjjOZZrkbD2sdHfVzLwM47U4DUrVC0F7ojDw@mail.gmail.com>

>> Are you looking for a limitation of such source code search patterns?
> 
> Exactly.

Would you like to explain your view a bit more?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-arm-kernel@lists.infradead.org
Subject: pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map()
Date: Mon, 30 Oct 2017 20:41:07 +0100	[thread overview]
Message-ID: <f306e5fb-e36b-0dae-d863-df57f7cd1ce4@users.sourceforge.net> (raw)
In-Reply-To: <CAMuHMdUH8NgkumbjjOZZrkbD2sdHfVzLwM47U4DUrVC0F7ojDw@mail.gmail.com>

>> Are you looking for a limitation of such source code search patterns?
> 
> Exactly.

Would you like to explain your view a bit more?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Barry Song <baohua@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	Patrice Chotard <patrice.chotard@st.com>,
	Rob Herring <robh@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map()
Date: Mon, 30 Oct 2017 20:41:07 +0100	[thread overview]
Message-ID: <f306e5fb-e36b-0dae-d863-df57f7cd1ce4@users.sourceforge.net> (raw)
In-Reply-To: <CAMuHMdUH8NgkumbjjOZZrkbD2sdHfVzLwM47U4DUrVC0F7ojDw@mail.gmail.com>

>> Are you looking for a limitation of such source code search patterns?
> 
> Exactly.

Would you like to explain your view a bit more?

Regards,
Markus

  reply	other threads:[~2017-10-30 19:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 18:36 [PATCH] pinctrl: sirf: Use common error handling code in sirfsoc_dt_node_to_map() SF Markus Elfring
2017-10-30 18:36 ` SF Markus Elfring
2017-10-30 18:36 ` SF Markus Elfring
2017-10-30 19:15 ` Geert Uytterhoeven
2017-10-30 19:15   ` Geert Uytterhoeven
2017-10-30 19:15   ` Geert Uytterhoeven
2017-10-30 19:32   ` SF Markus Elfring
2017-10-30 19:32     ` SF Markus Elfring
2017-10-30 19:32     ` SF Markus Elfring
2017-10-30 19:32     ` SF Markus Elfring
2017-10-30 19:34     ` Geert Uytterhoeven
2017-10-30 19:34       ` Geert Uytterhoeven
2017-10-30 19:34       ` Geert Uytterhoeven
2017-10-30 19:41       ` SF Markus Elfring [this message]
2017-10-30 19:41         ` SF Markus Elfring
2017-10-30 19:41         ` SF Markus Elfring
2017-10-30 19:41         ` SF Markus Elfring
2017-11-01 10:33   ` [PATCH] " Dan Carpenter
2017-11-01 10:33     ` Dan Carpenter
2017-11-01 10:33     ` Dan Carpenter
2017-11-01 10:33     ` Dan Carpenter

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=f306e5fb-e36b-0dae-d863-df57f7cd1ce4@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=linux-arm-kernel@lists.infradead.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.