Gideon: what exactly did you use to send this email series?
I used git format-patch and then send-email on my Fedora 24 system.
I did :
git format-patch HEAD^^ # this generated two patches for the two commits I made
git send-email --to ... ~/patches/0001- .... #sent first patch
git send-email --to ... ~/patches/0002- ....#sent second patch
Yes, I sent each patch individually. Should I have just passed the directory?
On Fri, Jan 20, 2017 at 1:14 PM, Geert Uytterhoeven
<geert@xxxxxxxxxxxxxx> wrote:
On Thu, Jan 19, 2017 at 9:31 PM, kbuild test robot <lkp@xxxxxxxxx> wrote:
Hi Gideon,
[auto build test ERROR on m68k/for-next]
[also build test ERROR on v4.10-rc4 next-20170119]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Gideon-Israel-Dsouza/compiler-gcc-h-Added-new-macro-for-gcc-attribute/20170120-032332
base: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-next
config: m68k-allmodconfig (attached as .config)
Hmm, although Gideon seems to have use git-send-email, there's no
"In-Reply-To" header in the email containing the second patch, hence
the kbuild test robot didn't consider the dependency on the first
patch...
Gideon: what exactly did you use to send this emai series?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
