<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.ie/group/linux.kernel</id>
  <title type="text">linux.kernel Google Group</title>
  <subtitle type="text">
  linux-kernel@vger.kernel.org (Moderated)
  </subtitle>
  <link href="/group/linux.kernel/feed/atom_v1_0_msgs.xml" rel="self" title="linux.kernel feed"/>
  <updated>2010-03-15T19:30:03Z</updated>
  <generator uri="http://groups.google.ie" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>David Miller</name>
  <email>da...@davemloft.net</email>
  </author>
  <updated>2010-03-15T19:30:03Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/a2f545e0e25d97b7/b4437f752e906c9a?show_docid=b4437f752e906c9a</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/a2f545e0e25d97b7/b4437f752e906c9a?show_docid=b4437f752e906c9a"/>
  <title type="text">Re: [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing</title>
  <summary type="html" xml:space="preserve">
  Ok, I really think we should link with libopcodes or similar so we can &lt;br&gt; handle the simple assembler annotation case without requiring the &lt;br&gt; kernel image being available. &lt;br&gt; That&#39;s what I was trying to achieve when I sent you the report
  </summary>
  </entry>
  <entry>
  <author>
  <name>Arnaldo Carvalho de Melo</name>
  <email>a...@infradead.org</email>
  </author>
  <updated>2010-03-15T19:30:03Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/a2f545e0e25d97b7/dc8185340cd536a3?show_docid=dc8185340cd536a3</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/a2f545e0e25d97b7/dc8185340cd536a3?show_docid=dc8185340cd536a3"/>
  <title type="text">Re: [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing</title>
  <summary type="html" xml:space="preserve">
  Em Mon, Mar 15, 2010 at 11:55:26AM -0700, David Miller escreveu: &lt;br&gt; Annotation is done by objdump -dS, that requires an executable file to &lt;br&gt; do ASM annotation, and one with DWARF info for source code annotation. &lt;br&gt; What we have with /proc/kallsyms is just the symtab. &lt;br&gt; - Arnaldo
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ville Syrjälä</name>
  <email>syrj...@sci.fi</email>
  </author>
  <updated>2010-03-15T19:30:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/0fe1e630b4ff63e1/27693149a4991e9b?show_docid=27693149a4991e9b</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/0fe1e630b4ff63e1/27693149a4991e9b?show_docid=27693149a4991e9b"/>
  <title type="text">Re: [PATCH] drm: Allow platform devices to register as DRM devices</title>
  <summary type="html" xml:space="preserve">
  I really dislike the fact that drm has bus specific junk all over the &lt;br&gt; generic code. Some ideas how to clean that up: &lt;br&gt; Add &#39;struct device *dev&#39; into drm_device so you don&#39;t have to go through &lt;br&gt; the pdev/platformdev to get it every time. Also use dev_name() instead &lt;br&gt; of pci_name() and whatever you used for the platform device case.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Felipe Balbi</name>
  <email>m...@felipebalbi.com</email>
  </author>
  <updated>2010-03-15T19:30:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/07b7378410b38461/6764d258bea5f696?show_docid=6764d258bea5f696</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/07b7378410b38461/6764d258bea5f696?show_docid=6764d258bea5f696"/>
  <title type="text">Re: [PATCH] USB: f_mass_storage: dynamic buffers for better alignment</title>
  <summary type="html" xml:space="preserve">
  I have no opinion anymore :-p &lt;br&gt; I can only think about the devices I&#39;ve been working on which would be a &lt;br&gt; pain to allocate so much memory and would suffer if you use vmalloc() &lt;br&gt; too, so both would be a no-no for me :-p &lt;br&gt; how about ? &lt;br&gt; for (i = FSG_NUM_BUFFER; i; i--, ++bh) { &lt;br&gt; bh-&amp;gt;buf = kmalloc(FSG_BUFLEN, GFP_KERNEL);
  </summary>
  </entry>
  <entry>
  <author>
  <name>Chris Mason</name>
  <email>chris.ma...@oracle.com</email>
  </author>
  <updated>2010-03-15T19:30:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/42573576ec3cb225/9284823e381877da?show_docid=9284823e381877da</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/42573576ec3cb225/9284823e381877da?show_docid=9284823e381877da"/>
  <title type="text">[GIT PULL] Btrfs updates</title>
  <summary type="html" xml:space="preserve">
  Hello everyone, &lt;br&gt; The master branch of the btrfs unstable tree has a collection of fixes &lt;br&gt; and features: &lt;br&gt; git://git.kernel.org/pub/scm/l inux/kernel/git/mason/btrfs-un stable.git master &lt;br&gt; If Linus decides this pull is too big/too late, we&#39;ll maintain a bug fix &lt;br&gt; only branch for .34 and keep this branch stable for people that want to
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michał Nazarewicz</name>
  <email>m.nazarew...@samsung.com</email>
  </author>
  <updated>2010-03-15T19:30:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/07b7378410b38461/def68449992f9a76?show_docid=def68449992f9a76</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/07b7378410b38461/def68449992f9a76?show_docid=def68449992f9a76"/>
  <title type="text">Re: [PATCH] USB: f_mass_storage: dynamic buffers for better alignment</title>
  <summary type="html" xml:space="preserve">
  I admit, I haven&#39;t thought about that. Some fields rearrangement &lt;br&gt; could help avoid some padding but yes, it can be done. &lt;br&gt; However, there is one more thing I&#39;ve had in mind. Each buffer &lt;br&gt; is 4 pages (16 KiB) and there are two such buffers in struct &lt;br&gt; fsg_common therefore the whole size of the structure is
  </summary>
  </entry>
  <entry>
  <author>
  <name>Pavel Machek</name>
  <email>pa...@ucw.cz</email>
  </author>
  <updated>2010-03-15T19:20:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/30b01465863713c4/3756b02d17b28015?show_docid=3756b02d17b28015</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/30b01465863713c4/3756b02d17b28015?show_docid=3756b02d17b28015"/>
  <title type="text">Re: [PATCH] staging: winbond: mac_structures.h Fixed indentation, whitespace etc</title>
  <summary type="html" xml:space="preserve">
  ...which only shows how little problems checkpatch detects. &lt;br&gt; Get rid of revision history; it does not make sense, is not english, &lt;br&gt; and just should not be there. &lt;br&gt; Consistent tabs vs spaces? &lt;br&gt; Same here. &lt;br&gt; I thought you was killing C++ comments? &lt;br&gt; Commented out code should be killed, not commented out in nicer way.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Tony Lindgren</name>
  <email>t...@atomide.com</email>
  </author>
  <updated>2010-03-15T19:20:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/135d2381f90120a4/e203c680e8f3b403?show_docid=e203c680e8f3b403</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/135d2381f90120a4/e203c680e8f3b403?show_docid=e203c680e8f3b403"/>
  <title type="text">[GIT PULL] omap fixes for 2.6.34-rc1</title>
  <summary type="html" xml:space="preserve">
  Hi Linus, &lt;br&gt; Please pull omap fixes from: &lt;br&gt; git://git.kernel.org/pub/scm/l inux/kernel/git/tmlind/linux-o map-2.6.git omap-fixes-for-linus &lt;br&gt; Regards, &lt;br&gt; Tony &lt;br&gt; The following changes since commit 57d54889cd00db2752994b389ba714 138652e60c: &lt;br&gt; Linus Torvalds (1): &lt;br&gt; Linux 2.6.34-rc1 &lt;br&gt; are available in the git repository at:
  </summary>
  </entry>
  <entry>
  <author>
  <name>David Miller</name>
  <email>da...@davemloft.net</email>
  </author>
  <updated>2010-03-15T19:10:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/6c7e58820441b0f0/e01c95f3b28ca3ea?show_docid=e01c95f3b28ca3ea</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/6c7e58820441b0f0/e01c95f3b28ca3ea?show_docid=e01c95f3b28ca3ea"/>
  <title type="text">Re: [PATCH] net/netfilter/ipvs/ip_vs_ftp.c: Remove use of NIPQUAD</title>
  <summary type="html" xml:space="preserve">
  Yes.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Samuel Ortiz</name>
  <email>sa...@linux.intel.com</email>
  </author>
  <updated>2010-03-15T19:10:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/7a5f3f3567fe68c3/d81205ba8ea5f13b?show_docid=d81205ba8ea5f13b</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/7a5f3f3567fe68c3/d81205ba8ea5f13b?show_docid=d81205ba8ea5f13b"/>
  <title type="text">Re: [PATCH 1/4 v2] x86: remove rdc321x_defs.h</title>
  <summary type="html" xml:space="preserve">
  Hi Ingo, &lt;br&gt; Thanks. &lt;br&gt; The MFD tree, yes. &lt;br&gt; Florian, I&#39;ll review those patches later this week, thanks. &lt;br&gt; Cheers, &lt;br&gt; Samuel.
  </summary>
  </entry>
  <entry>
  <author>
  <name>David Miller</name>
  <email>da...@davemloft.net</email>
  </author>
  <updated>2010-03-15T19:00:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/ca81ed5b4d573ad2/60fa324829b851b8?show_docid=60fa324829b851b8</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/ca81ed5b4d573ad2/60fa324829b851b8?show_docid=60fa324829b851b8"/>
  <title type="text">Re: [Regression] r8169: enable 64-bit DMA by default for PCI Express devices (v2)</title>
  <summary type="html" xml:space="preserve">
  RnJvbTogSsO2cm4gRW5nZWwgPGpvZX JuQGR1Ymxpbi5sb2dmcy5vcmc+DQpE YXRlOiBNb24sIDE1 &lt;br&gt; IE1hciAyMDEwIDE2OjEwOjQxICswMT AwDQoNCj4gRm9yZ290IHRvIENjOiBs a21sLg0KDQpBY3R1 &lt;br&gt; YWxseSwgd2hhdCB5b3UgcmVhbGx5IG 5lZWQgdG8gQ0M6IGlzIG5ldGRldiwg YWRkZWQuDQo+IE9u &lt;br&gt; IE1vbiwgMTUgTWFyY2ggMjAxMCAxNj owODowNiArMDEwMCwgSu+/vXJuIEVu Z2VsIHdyb3RlOg0K
  </summary>
  </entry>
  <entry>
  <author>
  <name>David Miller</name>
  <email>da...@davemloft.net</email>
  </author>
  <updated>2010-03-15T19:00:01Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/72554804fb8d2d94/856b63229d1d285a?show_docid=856b63229d1d285a</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/72554804fb8d2d94/856b63229d1d285a?show_docid=856b63229d1d285a"/>
  <title type="text">Re: 64-syscall args on 32-bit vs syscall()</title>
  <summary type="html" xml:space="preserve">
  There are many archs that still lack VDSO.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Linus Torvalds</name>
  <email>torva...@linux-foundation.org</email>
  </author>
  <updated>2010-03-15T19:00:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/66b7f0e9171678b7/457c3d1e9bd85cc9?show_docid=457c3d1e9bd85cc9</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/66b7f0e9171678b7/457c3d1e9bd85cc9?show_docid=457c3d1e9bd85cc9"/>
  <title type="text">Re: [PATCH] init dynamic bin_attribute structures</title>
  <summary type="html" xml:space="preserve">
  The firmware loader should be done differently: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://patchwork.kernel.org/patch/84814/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; and I suspect that Wolfram may have skipped the thermal one as having been &lt;br&gt; done by another patch (that I didn&#39;t merge, due to having questions about &lt;br&gt; the whole issue, but that I don&#39;t have any objections to) &lt;br&gt; But maybe there is also some limitation to the coccinelle rule too.
  </summary>
  </entry>
  <entry>
  <author>
  <name>David Miller</name>
  <email>da...@davemloft.net</email>
  </author>
  <updated>2010-03-15T19:00:02Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/a2f545e0e25d97b7/5c29853e218c970d?show_docid=5c29853e218c970d</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/a2f545e0e25d97b7/5c29853e218c970d?show_docid=5c29853e218c970d"/>
  <title type="text">Re: [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing</title>
  <summary type="html" xml:space="preserve">
  Arnaldo, if perf top can use the kallsyms to do it&#39;s normal task, why &lt;br&gt; can&#39;t it use that for symbol annotations too? Isn&#39;t there enough &lt;br&gt; information available?
  </summary>
  </entry>
  <entry>
  <author>
  <name>Anthony Liguori</name>
  <email>anth...@codemonkey.ws</email>
  </author>
  <updated>2010-03-15T18:50:01Z</updated>
  <id>http://groups.google.ie/group/linux.kernel/browse_thread/thread/a394e4b96262b225/2ee5bb0c72183d89?show_docid=2ee5bb0c72183d89</id>
  <link href="http://groups.google.ie/group/linux.kernel/browse_thread/thread/a394e4b96262b225/2ee5bb0c72183d89?show_docid=2ee5bb0c72183d89"/>
  <title type="text">Re: [PATCH][RF C/T/D] Unmapped page cache control - via boot parameter</title>
  <summary type="html" xml:space="preserve">
  Not really. In many cloud environments, there&#39;s a set of common images &lt;br&gt; that are instantiated on each node. Usually this is because you&#39;re &lt;br&gt; running a horizontally scalable application or because you&#39;re supporting &lt;br&gt; an ephemeral storage model. &lt;br&gt; In fact, with ephemeral storage, you typically want to use
  </summary>
  </entry>
</feed>
