From: Dan Robertson <danlrobertson89@gmail.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
felipe.balbi@linux.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts/gdb: fix linux constants
Date: Fri, 15 Feb 2019 20:30:07 +0000 [thread overview]
Message-ID: <20190215203006.GA593@nessie> (raw)
In-Reply-To: <07923abd-117d-2a33-2700-7db0840eacad@ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
Kieran,
> This commit was pipped to the post by a similar patch [0] from Felipe Balbi
No problem! I probably should watch the LKML closer.
Go with the patch from Felipe, but like you men there is definitely no need
for the `include linux/fs.h` now.
Thanks for the tip on the Fixes tag. As a kernel newbie tips like this are
appreciated.
Cheers,
Dan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-15 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190215191713.GA28287@nessie>
2019-02-15 20:24 ` [PATCH] scripts/gdb: fix linux constants Kieran Bingham
2019-02-15 20:30 ` Dan Robertson [this message]
2019-02-18 13:25 ` [PATCH 0/1] " Dan Robertson
2019-02-18 13:25 ` [PATCH 1/1] " Dan Robertson
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=20190215203006.GA593@nessie \
--to=danlrobertson89@gmail.com \
--cc=felipe.balbi@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=kieran.bingham@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox