All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gideon D'souza" <gidisrael@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild test robot <lkp@intel.com>,
	"kbuild-all@01.org" <kbuild-all@01.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH 2/2] m68k: replaced gcc specific macros with ones from compiler.h
Date: Fri, 20 Jan 2017 15:51:26 +0530	[thread overview]
Message-ID: <CAPNrq4wfe6Bp1SOjF3nP7=KV2EJtV7dgL5kzmtkYkUfw7wfg4w@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdXkQ6sSw=oQcxUBi0hbZ1_tjc9mx55HvJ1mLPwJoHyDZw@mail.gmail.com>

> 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@linux-m68k.org> wrote:
> On Thu, Jan 19, 2017 at 9:31 PM, kbuild test robot <lkp@intel.com> 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@linux-m68k.org
>
> 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

  parent reply	other threads:[~2017-01-20 10:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 13:35 [PATCH 2/2] m68k: replaced gcc specific macros with ones from compiler.h Gideon Israel Dsouza
2017-01-19 13:35 ` Gideon Israel Dsouza
2017-01-19 20:31 ` kbuild test robot
2017-01-20  7:44   ` Geert Uytterhoeven
2017-01-20  7:44   ` Geert Uytterhoeven
2017-01-20 10:21     ` Gideon D'souza
2017-01-20 10:21     ` Gideon D'souza [this message]
2017-01-20 10:34       ` Geert Uytterhoeven
2017-01-20 10:34       ` Geert Uytterhoeven
2017-01-20 11:24         ` Gideon D'souza
2017-01-20 11:24           ` Gideon D'souza
2017-01-19 20:31 ` kbuild test robot
2017-01-19 20:48 ` kbuild test robot
2017-01-19 20:48   ` kbuild test robot
2017-01-20  5:21   ` Gideon D'souza
2017-01-20  5:21   ` Gideon D'souza
2017-01-24 12:14 [PATCH 1/2] compiler-gcc.h: Added new macro for gcc attribute Gideon Israel Dsouza
2017-01-24 12:14 ` [PATCH 2/2] m68k: replaced gcc specific macros with ones from compiler.h Gideon Israel Dsouza
2017-01-25  1:04   ` Greg Ungerer
2017-01-25  1:04   ` Greg Ungerer
2017-01-25  6:54   ` kbuild test robot
2017-01-25  6:54     ` kbuild test robot
2017-01-27 16:39   ` Paul Gortmaker
2017-01-27 16:39     ` Paul Gortmaker
2017-01-27 17:18     ` Gideon D'souza
2017-01-27 17:18       ` Gideon D'souza
2017-01-24 12:14 ` Gideon Israel Dsouza
2017-01-27 18:14 Gideon Israel Dsouza
2017-01-27 18:15 ` [PATCH 2/2] m68k: replaced gcc specific macros with ones from compiler.h Gideon Israel Dsouza
2017-01-27 18:15 ` Gideon Israel Dsouza

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='CAPNrq4wfe6Bp1SOjF3nP7=KV2EJtV7dgL5kzmtkYkUfw7wfg4w@mail.gmail.com' \
    --to=gidisrael@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=lkp@intel.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.