From: kernel test robot <lkp@intel.com>
To: "Sean Young" <sean@mess.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Vladimir Zapolskiy" <vz@mleia.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Daire McNamara" <daire.mcnamara@microchip.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Cc: oe-kbuild-all@lists.linux.dev, Sean Young <sean@mess.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context
Date: Sun, 1 Oct 2023 22:43:51 +0800 [thread overview]
Message-ID: <202310012229.ldJwkjOY-lkp@intel.com> (raw)
In-Reply-To: <1bd5241d584ceb4d6b731c4dc3203fb9686ee1d1.1696156485.git.sean@mess.org>
Hi Sean,
kernel test robot noticed the following build errors:
[auto build test ERROR on thierry-reding-pwm/for-next]
[also build test ERROR on shawnguo/for-next atorgue-stm32/stm32-next media-tree/master linus/master v6.6-rc3 next-20230929]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Sean-Young/media-pwm-ir-tx-trigger-edges-from-hrtimer-interrupt-context/20231001-194056
base: https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git for-next
patch link: https://lore.kernel.org/r/1bd5241d584ceb4d6b731c4dc3203fb9686ee1d1.1696156485.git.sean%40mess.org
patch subject: [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context
config: arm-randconfig-002-20231001 (https://download.01.org/0day-ci/archive/20231001/202310012229.ldJwkjOY-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231001/202310012229.ldJwkjOY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310012229.ldJwkjOY-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/cpumask.h:10,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/spinlock.h:63,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/slab.h:16,
from include/linux/resource_ext.h:11,
from include/linux/acpi.h:13,
from include/linux/i2c.h:13,
from drivers/input/misc/da7280.c:12:
include/linux/pwm.h: In function 'pwm_apply_state':
>> include/linux/pwm.h:428:24: error: implicit declaration of function 'pwm_can_sleep'; did you mean 'cant_sleep'? [-Werror=implicit-function-declaration]
428 | might_sleep_if(pwm_can_sleep(pwm));
| ^~~~~~~~~~~~~
include/linux/kernel.h:194:39: note: in definition of macro 'might_sleep_if'
194 | #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
| ^~~~
In file included from drivers/input/misc/da7280.c:16:
include/linux/pwm.h: At top level:
>> include/linux/pwm.h:455:20: error: conflicting types for 'pwm_can_sleep'; have 'bool(struct pwm_device *)' {aka '_Bool(struct pwm_device *)'}
455 | static inline bool pwm_can_sleep(struct pwm_device *pwm)
| ^~~~~~~~~~~~~
include/linux/pwm.h:428:24: note: previous implicit declaration of 'pwm_can_sleep' with type 'int()'
428 | might_sleep_if(pwm_can_sleep(pwm));
| ^~~~~~~~~~~~~
include/linux/kernel.h:194:39: note: in definition of macro 'might_sleep_if'
194 | #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
| ^~~~
cc1: some warnings being treated as errors
vim +428 include/linux/pwm.h
419
420 struct pwm_device *devm_pwm_get(struct device *dev, const char *con_id);
421 struct pwm_device *devm_fwnode_pwm_get(struct device *dev,
422 struct fwnode_handle *fwnode,
423 const char *con_id);
424 #else
425 static inline int pwm_apply_state(struct pwm_device *pwm,
426 const struct pwm_state *state)
427 {
> 428 might_sleep_if(pwm_can_sleep(pwm));
429 return -ENOTSUPP;
430 }
431
432 static inline int pwm_adjust_config(struct pwm_device *pwm)
433 {
434 return -ENOTSUPP;
435 }
436
437 static inline int pwm_config(struct pwm_device *pwm, int duty_ns,
438 int period_ns)
439 {
440 might_sleep_if(pwm_can_sleep(pwm));
441 return -EINVAL;
442 }
443
444 static inline int pwm_enable(struct pwm_device *pwm)
445 {
446 might_sleep_if(pwm_can_sleep(pwm));
447 return -EINVAL;
448 }
449
450 static inline void pwm_disable(struct pwm_device *pwm)
451 {
452 might_sleep_if(pwm_can_sleep(pwm));
453 }
454
> 455 static inline bool pwm_can_sleep(struct pwm_device *pwm)
456 {
457 return true;
458 }
459
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Sean Young" <sean@mess.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Vladimir Zapolskiy" <vz@mleia.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Daire McNamara" <daire.mcnamara@microchip.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Cc: oe-kbuild-all@lists.linux.dev, Sean Young <sean@mess.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context
Date: Sun, 1 Oct 2023 22:43:51 +0800 [thread overview]
Message-ID: <202310012229.ldJwkjOY-lkp@intel.com> (raw)
In-Reply-To: <1bd5241d584ceb4d6b731c4dc3203fb9686ee1d1.1696156485.git.sean@mess.org>
Hi Sean,
kernel test robot noticed the following build errors:
[auto build test ERROR on thierry-reding-pwm/for-next]
[also build test ERROR on shawnguo/for-next atorgue-stm32/stm32-next media-tree/master linus/master v6.6-rc3 next-20230929]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Sean-Young/media-pwm-ir-tx-trigger-edges-from-hrtimer-interrupt-context/20231001-194056
base: https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git for-next
patch link: https://lore.kernel.org/r/1bd5241d584ceb4d6b731c4dc3203fb9686ee1d1.1696156485.git.sean%40mess.org
patch subject: [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context
config: arm-randconfig-002-20231001 (https://download.01.org/0day-ci/archive/20231001/202310012229.ldJwkjOY-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231001/202310012229.ldJwkjOY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310012229.ldJwkjOY-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/cpumask.h:10,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/spinlock.h:63,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/slab.h:16,
from include/linux/resource_ext.h:11,
from include/linux/acpi.h:13,
from include/linux/i2c.h:13,
from drivers/input/misc/da7280.c:12:
include/linux/pwm.h: In function 'pwm_apply_state':
>> include/linux/pwm.h:428:24: error: implicit declaration of function 'pwm_can_sleep'; did you mean 'cant_sleep'? [-Werror=implicit-function-declaration]
428 | might_sleep_if(pwm_can_sleep(pwm));
| ^~~~~~~~~~~~~
include/linux/kernel.h:194:39: note: in definition of macro 'might_sleep_if'
194 | #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
| ^~~~
In file included from drivers/input/misc/da7280.c:16:
include/linux/pwm.h: At top level:
>> include/linux/pwm.h:455:20: error: conflicting types for 'pwm_can_sleep'; have 'bool(struct pwm_device *)' {aka '_Bool(struct pwm_device *)'}
455 | static inline bool pwm_can_sleep(struct pwm_device *pwm)
| ^~~~~~~~~~~~~
include/linux/pwm.h:428:24: note: previous implicit declaration of 'pwm_can_sleep' with type 'int()'
428 | might_sleep_if(pwm_can_sleep(pwm));
| ^~~~~~~~~~~~~
include/linux/kernel.h:194:39: note: in definition of macro 'might_sleep_if'
194 | #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
| ^~~~
cc1: some warnings being treated as errors
vim +428 include/linux/pwm.h
419
420 struct pwm_device *devm_pwm_get(struct device *dev, const char *con_id);
421 struct pwm_device *devm_fwnode_pwm_get(struct device *dev,
422 struct fwnode_handle *fwnode,
423 const char *con_id);
424 #else
425 static inline int pwm_apply_state(struct pwm_device *pwm,
426 const struct pwm_state *state)
427 {
> 428 might_sleep_if(pwm_can_sleep(pwm));
429 return -ENOTSUPP;
430 }
431
432 static inline int pwm_adjust_config(struct pwm_device *pwm)
433 {
434 return -ENOTSUPP;
435 }
436
437 static inline int pwm_config(struct pwm_device *pwm, int duty_ns,
438 int period_ns)
439 {
440 might_sleep_if(pwm_can_sleep(pwm));
441 return -EINVAL;
442 }
443
444 static inline int pwm_enable(struct pwm_device *pwm)
445 {
446 might_sleep_if(pwm_can_sleep(pwm));
447 return -EINVAL;
448 }
449
450 static inline void pwm_disable(struct pwm_device *pwm)
451 {
452 might_sleep_if(pwm_can_sleep(pwm));
453 }
454
> 455 static inline bool pwm_can_sleep(struct pwm_device *pwm)
456 {
457 return true;
458 }
459
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Sean Young" <sean@mess.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Vladimir Zapolskiy" <vz@mleia.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Daire McNamara" <daire.mcnamara@microchip.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Cc: oe-kbuild-all@lists.linux.dev, Sean Young <sean@mess.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context
Date: Sun, 1 Oct 2023 22:43:51 +0800 [thread overview]
Message-ID: <202310012229.ldJwkjOY-lkp@intel.com> (raw)
In-Reply-To: <1bd5241d584ceb4d6b731c4dc3203fb9686ee1d1.1696156485.git.sean@mess.org>
Hi Sean,
kernel test robot noticed the following build errors:
[auto build test ERROR on thierry-reding-pwm/for-next]
[also build test ERROR on shawnguo/for-next atorgue-stm32/stm32-next media-tree/master linus/master v6.6-rc3 next-20230929]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Sean-Young/media-pwm-ir-tx-trigger-edges-from-hrtimer-interrupt-context/20231001-194056
base: https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git for-next
patch link: https://lore.kernel.org/r/1bd5241d584ceb4d6b731c4dc3203fb9686ee1d1.1696156485.git.sean%40mess.org
patch subject: [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context
config: arm-randconfig-002-20231001 (https://download.01.org/0day-ci/archive/20231001/202310012229.ldJwkjOY-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231001/202310012229.ldJwkjOY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310012229.ldJwkjOY-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/cpumask.h:10,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/spinlock.h:63,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/slab.h:16,
from include/linux/resource_ext.h:11,
from include/linux/acpi.h:13,
from include/linux/i2c.h:13,
from drivers/input/misc/da7280.c:12:
include/linux/pwm.h: In function 'pwm_apply_state':
>> include/linux/pwm.h:428:24: error: implicit declaration of function 'pwm_can_sleep'; did you mean 'cant_sleep'? [-Werror=implicit-function-declaration]
428 | might_sleep_if(pwm_can_sleep(pwm));
| ^~~~~~~~~~~~~
include/linux/kernel.h:194:39: note: in definition of macro 'might_sleep_if'
194 | #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
| ^~~~
In file included from drivers/input/misc/da7280.c:16:
include/linux/pwm.h: At top level:
>> include/linux/pwm.h:455:20: error: conflicting types for 'pwm_can_sleep'; have 'bool(struct pwm_device *)' {aka '_Bool(struct pwm_device *)'}
455 | static inline bool pwm_can_sleep(struct pwm_device *pwm)
| ^~~~~~~~~~~~~
include/linux/pwm.h:428:24: note: previous implicit declaration of 'pwm_can_sleep' with type 'int()'
428 | might_sleep_if(pwm_can_sleep(pwm));
| ^~~~~~~~~~~~~
include/linux/kernel.h:194:39: note: in definition of macro 'might_sleep_if'
194 | #define might_sleep_if(cond) do { if (cond) might_sleep(); } while (0)
| ^~~~
cc1: some warnings being treated as errors
vim +428 include/linux/pwm.h
419
420 struct pwm_device *devm_pwm_get(struct device *dev, const char *con_id);
421 struct pwm_device *devm_fwnode_pwm_get(struct device *dev,
422 struct fwnode_handle *fwnode,
423 const char *con_id);
424 #else
425 static inline int pwm_apply_state(struct pwm_device *pwm,
426 const struct pwm_state *state)
427 {
> 428 might_sleep_if(pwm_can_sleep(pwm));
429 return -ENOTSUPP;
430 }
431
432 static inline int pwm_adjust_config(struct pwm_device *pwm)
433 {
434 return -ENOTSUPP;
435 }
436
437 static inline int pwm_config(struct pwm_device *pwm, int duty_ns,
438 int period_ns)
439 {
440 might_sleep_if(pwm_can_sleep(pwm));
441 return -EINVAL;
442 }
443
444 static inline int pwm_enable(struct pwm_device *pwm)
445 {
446 might_sleep_if(pwm_can_sleep(pwm));
447 return -EINVAL;
448 }
449
450 static inline void pwm_disable(struct pwm_device *pwm)
451 {
452 might_sleep_if(pwm_can_sleep(pwm));
453 }
454
> 455 static inline bool pwm_can_sleep(struct pwm_device *pwm)
456 {
457 return true;
458 }
459
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-01 14:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 10:40 [PATCH 0/2] Improve pwm-ir-tx precision Sean Young
2023-10-01 10:40 ` [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context Sean Young
2023-10-01 10:40 ` Sean Young
2023-10-01 10:40 ` Sean Young
2023-10-01 14:43 ` kernel test robot [this message]
2023-10-01 14:43 ` kernel test robot
2023-10-01 14:43 ` kernel test robot
2023-10-01 16:07 ` kernel test robot
2023-10-01 16:07 ` kernel test robot
2023-10-01 16:07 ` kernel test robot
2023-10-01 17:21 ` Sean Young
2023-10-01 17:21 ` Sean Young
2023-10-01 17:21 ` Sean Young
2023-10-04 9:59 ` Uwe Kleine-König
2023-10-04 9:59 ` Uwe Kleine-König
2023-10-04 9:59 ` Uwe Kleine-König
2023-10-05 8:30 ` Sean Young
2023-10-05 8:30 ` Sean Young
2023-10-05 8:30 ` Sean Young
2023-10-05 9:17 ` Uwe Kleine-König
2023-10-05 9:17 ` Uwe Kleine-König
2023-10-05 9:17 ` Uwe Kleine-König
2023-10-06 10:27 ` Thierry Reding
2023-10-06 10:27 ` Thierry Reding
2023-10-06 10:27 ` Thierry Reding
2023-10-06 14:44 ` Uwe Kleine-König
2023-10-06 14:44 ` Uwe Kleine-König
2023-10-06 14:44 ` Uwe Kleine-König
2023-10-06 10:29 ` Thierry Reding
2023-10-06 10:29 ` Thierry Reding
2023-10-06 10:29 ` Thierry Reding
2023-10-01 10:40 ` [PATCH 2/2] media: pwm-ir-tx: trigger edges from hrtimer interrupt context Sean Young
2023-10-02 5:49 ` Ivaylo Dimitrov
2023-10-02 8:20 ` Sean Young
2023-10-02 8:59 ` Uwe Kleine-König
2023-10-02 9:52 ` Ivaylo Dimitrov
2023-10-04 7:43 ` Sean Young
2023-10-04 9:35 ` Uwe Kleine-König
2023-10-02 6:16 ` Ivaylo Dimitrov
2023-10-04 8:00 ` Sean Young
2023-10-04 12:54 ` Ivaylo Dimitrov
2023-10-04 14:42 ` Sean Young
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=202310012229.ldJwkjOY-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=festevam@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=s.hauer@pengutronix.de \
--cc=sean@mess.org \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vz@mleia.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 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.